Autonnel v1.7.0

Permissions

Assign features to roles, assign roles to users, control who sees what in the admin.


The permission system lets you control what each user can see and do in the admin UI. You assign features to roles, then assign roles to users. Each user sees only the menu items their roles include.

Features

Every top-level menu and sub-menu is gated by a feature ID, and the page behind it checks the same feature, so a menu item is shown exactly when its page opens. Examples:

Feature IDCovers
overviewOverview dashboard and its live activity feed
pagesPages menu and every page action (create, edit, delete)
pages.createShows the create and duplicate actions in the Pages list
pages.deleteShows the delete action in the Pages list
funnelsFunnels menu and every funnel action
marketingMarketing menu, including connecting ad accounts with OAuth from the Connect ad platform dialog
ordersOrders menu
orders.refundIssuing refunds
orders.emailsOrders → Emails
paymentPayment menu (view payment providers)
settings.paymentCreating, editing and deleting payment accounts and binding them to domains; without it the account pages and each domain’s Payment tab are read-only
transactionsPayment → Transactions
api-keysSettings → API Keys
settingsSettings pages added by plugins (for example Voluum). It does not open any core settings page.
settings.usersSettings → Users: inviting users and managing invitations
settings.logsSettings → Logs and the system status box at the bottom of the sidebar
settings.localization, settings.storage, settings.llm, settings.ai-conversion-analysis, settings.ads, settings.email, settings.ecommerce, settings.recallThe settings page of the same name (settings.email is Email Templates)
settings.maintenanceThe Maintenance tab of each domain
settings.google-maps, settings.browser-renderingSettings → Integrations, each showing only its own panel
settings.couponCoupon management
settings.notificationsNotification channel config
settings.domainsDomains & brands: binding domains and each domain’s store name, logo, favicon, email sender, custom code and search indexing. Roles that held the removed Branding or Custom Code permissions get this one when you run npx autonnel pages:backfill-domains.
permissionsRoles and Permissions tab

Permissions are per feature, not per record: there is no “only content I created” rule. A role with funnels can edit and delete every funnel. pages.create and pages.delete only hide buttons in the Pages list; the API itself checks pages.

The feature catalog is defined in source code and is not editable from the admin UI. Plugins can add their own features (for example a plugin page with a read and an edit permission). They appear in the role editor as a separate group named after the plugin, only Admin has them until you grant them to a role, and they disappear from the editor when the plugin is removed.

Built-in role

Admin is created on first run. It always has every feature, including ones added by later versions, and it cannot be edited or deleted. Every other role is a custom role.

Creating a custom role

  1. Go to Settings → Roles and Permissions.
  2. Click New role.
  3. Enter a name. Names are unique per installation.
  4. Check the features to include. The matrix groups features by section (Pages, Funnels, Orders, Settings, etc.).
  5. Save. The role is immediately available to assign to users, and changes to an existing role apply to its members on their next request.

Inviting users

Go to Settings → Users and send an invitation to an email address (open self-registration is disabled). The invite link opens the registration page, which behaves differently depending on whether the email already has an account:

  • New email — the invitee chooses a username and password; the account is created and joins with the invited roles.
  • Email with an existing account — the invitee must enter that account’s current password. The invitation then adds the existing account to this workspace with the invited roles; an invitation never changes the account’s password. A wrong password fails without consuming the invitation, so it can be retried.

On Autonnel Cloud this is how one person joins multiple organizations with a single account: accept each organization’s invitation with the same email and password, then sign in on each organization’s <org>-console domain.

Assigning roles to users

Go to Settings → Users, find the user, and use the role selector. The change takes effect immediately for new requests.

A user with multiple roles has the union of all their roles’ features.

The admin sidebar reads the current user’s effective features on each page load and hides any top-level or sub-level menu items the user lacks access to. Opening a page directly without access redirects to the first menu item the user can open (Overview for most roles); a user whose roles grant no menu at all sees a “no access” page. API endpoints return 403.

Plugins that add menu items declare which feature gates them; plugin settings pages without their own feature use settings.

Controlling access to the Roles and Permissions tab

The Roles and Permissions tab is visible to users whose roles include the permissions feature (which includes Admin), and to users whose ID is listed in the PERMISSIONS_ADMIN_USER_IDS runtime configuration value.

PERMISSIONS_ADMIN_USER_IDS is a comma-separated list of user IDs. Configure it in Settings → Roles and Permissions or in your deployment’s runtime configuration.

Caveats

  • The built-in Admin role cannot be modified or deleted. Create a custom role if you need a variation.
  • Deleting a role with active users is blocked. Reassign all users first, then delete.
  • Multiple roles. A user with multiple roles has the union of all assigned roles’ features. There is no way to subtract a feature from a specific role without removing that role.
  • API Keys — API keys inherit the permissions of the user who created them.
  • Users — invite and manage user accounts under Settings → Users in the admin.