Skip to content

Account

An account is the top-level boundary in Prefactor, and it maps to your organisation.

Every agent, environment, admin user, and API token in Prefactor belongs to an account. When you sign in, you land inside one. Nothing crosses that boundary: activity, audit history, and configuration are all scoped to the account you are in. Projects, teams, and products all sit inside the same account.

Inside an account, you manage agents, the environments that separate your lifecycle stages, and the risk profiles that classify the data risk of your agents’ runs. You control who can access the account through its admin users and invites, and you create the API tokens that let your integrations authenticate with Prefactor. The account also holds the LLM providers: the language model connections, with their API keys, that hosted judges run on.

Each person who can sign in to the account, called an admin user, has one of two roles, and so does each API token. Full access can view and change everything in the account. Read only can view everything but can’t create, change, or delete anything. A read-only user can still complete their own profile after accepting an invite.

Roles exist so you can give people, and scripts, the access their job needs and no more. An auditor or a dashboard script can read every agent, run, and alert without being able to change a deployment or revoke a token.

The web app doesn’t hide controls from read-only users. They see the same buttons as everyone else, and Prefactor refuses the change with an error when they try to use one. The same check applies to requests made with a read-only API token. You choose a role when you invite someone or create a token, and you can change it later; nobody can change their own role.

Account settings opens from the user menu under your avatar.

  • Agent — agents belong to the account and are visible across all its environments.
  • Environment — environments live inside an account and separate lifecycle stages.
  • Risk profile — risk profiles are configured at the account level and assigned to individual agents.
  • API token — tokens authenticate integrations with Prefactor; both account-wide and deployment-scoped tokens belong to the account.
  • LLM provider — language model connections and API keys that hosted judges use.