Getting started

1. Enable the module

Go to /admin/modules, find Help Tutorials, toggle ON. The help icon (lifesaver / question mark, depending on your theme) starts appearing on every admin page that has a tutorial entry for the page's page_key.

There are no config_schema fields — the module is on/off only.

2. Confirm the seed loaded

The first request to GET /admin/help-tutorials/{pageKey} against a tenant that lacks tutorials triggers an automatic seed. You can also force it manually:

POST /admin/help-tutorials/seed
{ "language": "es" }

The seeder uses INSERT ... ON CONFLICT DO NOTHING, so re-running is safe — it only fills gaps. After a fresh tenant is provisioned, hitting any tutorial-aware admin page once auto-seeds the default set. The defaults are written in English; seeding for another language stores the same English content under that language code until you translate it.

3. Grant the privilege

Reading tutorials requires no privilege beyond an authenticated admin session — every operator can open the help panel. Editing them requires manage_help OR manage_settings (Wave 11). Open /admin/users/usergroups → pick the group → toggle the privilege ON.

The split exists so you can let your support / docs team author tutorials without giving them keys to settings.

4. Verify

Open /admin/orders. You should see a help icon in the page header. Clicking it opens the tutorial side panel. If it doesn't appear:

• Module disabled — re-check the toggle.
• Tutorial missing for page_key=orders — run the seed.
• Browser cached the old admin layout — hard reload.

Languages

Each tutorial row is keyed (page_key, language). The runtime resolves to the user's i18n locale. If the requested locale doesn't have a row, it falls back to en, then to "no tutorial". Keep an en row for every page so the fallback always has content.