Saltar al contenido principal

Domain Editors

A Domain Editor is a per-domain role that unlocks the Editor tab in the Appilot extension. Editors can register and edit Controls, Forms, and Zones directly from the page, without needing the full Backoffice admin role.

The role exists because the people who maintain a customer's app surface (content owners, customer-success engineers, web admins) are often not the same people who manage the organisation's billing or members.

What an editor can do​

  • Open the in-context Editor tab on the extension for any domain they have been granted.
  • Pick elements on the page and register them as Controls (clickable affordances), Forms (auto-discovered fields), or Zones (named regions like sidebar or footer).
  • Edit the basic fields of existing controls/forms/zones: label, description, locator (for controls), view paths.

What an editor cannot do​

Anything that lives behind Backoffice's deep editor:

  • Control prerequisites (the prior steps, such as a hover or a click, that reveal a hidden control).
  • Form visibility rules, field defaults, required-field selection, multi-tab.
  • Submit / entry control linkage.
  • Member management, billing, organisation settings.

When an editor tries to send one of those fields, the API responds with a friendly toast pointing them at the right Backoffice page. The Editor's "Open in Backoffice for advanced settings →" link is always one click away.

AI description suggestions​

Each Register form (Controls, Forms, Zones) has a Suggest description (AI) button next to the description field. It calls a small org-paid LLM helper that drafts a one-or-two-sentence description from the element's semantic ID, label, page URL, and (when available) a short HTML excerpt. The user can edit the suggestion before saving.

The suggester is separate from runtime credits. End users' credits are never consumed when an admin generates a description. The cost is covered by the organisation as part of its plan.

A monthly cap protects against accidental runaway use. The default is 50 suggestions per user per month; org admins can raise or lower this from the organisation settings page (column organizations.editor_ai_monthly_cap). When the cap is reached the button surfaces an inline "monthly cap reached" message and the user falls back to writing the description manually.

How to grant editor access​

  1. Log in to Backoffice as an org admin.
  2. Open the app, then the domain you want to grant access on.
  3. From the domain sidebar, click Members.
  4. Toggle Editor on this domain next to the user you want to promote.

That's it. The next time the user opens the extension on a page under that domain, the Editor tab appears.

Org admins are implicit editors on every domain their organisation owns, no toggle required.

When to use this role​

Typical candidates:

  • Content owners maintaining a specific section of your app.
  • Customer-success engineers helping a customer fine-tune their setup.
  • Documentation team members who want to make sure the assistant can see the same elements they're writing about.

If a teammate needs access to billing, members, or deep configuration, give them the full admin role instead.

Revoking access​

From the same Members page, untoggle the user. The change takes effect immediately, the Editor tab disappears from their extension on the next page load.

  • Managing Zones, what zones are and when to register them.
  • Page Inspector, the user-facing diagnostics tab. Available to everyone, no role required.