Skip to main content

Users and permissions

Superadmins manage accounts under System > Users.

Roles

  • Author accounts create and manage content in their own author space. Site policy can require moderation before publication.
  • Admin accounts are superadmins. They manage system settings, users, root content, all author content, themes, plugins, and operational tools exposed in the admin interface.

Composer mode does not grant permission. Simple, Focused, and Full only change which controls are visible.

Creating an account

Set a Username/Author, role, e-mail address, optional display name, password, and the two account-state controls.

The Username/Author value uses lowercase letters, numbers, and underscores. It is both the login username and public author path and is fixed after account creation through the ordinary user editor.

New accounts receive the current site default Composer mode. Their publishing and appearance defaults can then be changed through the profile areas.

Account state

Account enabled controls authentication. Disabling it prevents sign-in and invalidates existing sessions. It does not automatically remove already published content.

Public content enabled controls the author space. Disabling it hides the author’s public content and suspends its secret link. It does not need to disable the login account.

The controls can be combined. A locked account with public content enabled is useful for an archive or a section maintained by a superadmin.

Password changes

Changing an account password invalidates prior authenticated sessions. Authors can change their own password in Profile. E-mail password resets require SMTP and the matching role policy under System > Security.

The CLI user:set-password preserves an existing account’s role when the optional role argument is omitted. Passwords passed on the command line may be visible in process listings and shell history.

Deleting a user

User deletion revokes the author secret link and moves owned content into orphan storage rather than silently deleting it. Review System > Orphans and decide whether to recover, reassign, export, or remove that content.

Keep at least one working superadmin account.