Users and roles

Every user has one of four roles. The roles are listed here in ascending order of privilege, and each role includes every permission of the roles below it.

Roles

1. User — an end user. A user runs searches, converses with agents, and manages a personal profile and preferences.
2. Developer — creates, validates and publishes agents; views and edits the agent configuration (allowlist, compile rules, runtime limits, search settings, profiles); reads the agent reports; sees all published agents.
3. Administrator — everything a developer can do, plus users and their roles, authentication, agent servers, connection pools, secrets and encryption, the license, and the user usage reports.
4. Account owner — everything an administrator can do, plus billing and account-level settings.

A program that calls the API on its own behalf is a service account: a user with a key instead of a password, and with its own role, any except owner.

Permissions

Adding users

An administrator adds users by email address, up to 25 at a time. Each new user receives an email saying they were added, then clicks New user / Forgot password on the sign-in dialog, enters that email address, receives a one-time code, and chooses a password. No password or code travels in the added-user email. If the account restricts email addresses to a domain, only addresses in that domain can be added. A user's role can be changed only by someone else.

Removing users

A deleted user cannot sign in and cannot be restored. The user's name stays on everything the user published. Administrators cannot delete themselves.

Freezing

An administrator can freeze the account. A freeze stops every change to agents and configuration: drafts, publishing, profiles and settings. Searches and agent runs continue. The freeze records who applied it, and only that administrator or another administrator can lift the freeze. A freeze suits a release or an investigation.