Documentation
Organizations, departments and roles
How access is scoped, and what each role may do.
Organizations
An organization is the tenant. Every workflow, agent, knowledge base and connection belongs to exactly one, and nothing crosses between them. That boundary is enforced in the database itself, not only in application code.
Departments
Inside an organization, work is scoped to departments. A department owns its workflows, its knowledge bases and the connections it has been granted. People see what their departments have.
- Every organization has a permanent default department called Everyone.
- Every user joins Everyone, and nobody can leave it.
- A department that still holds workflows, agents or connection grants cannot be deleted.
Departments are called teams in some places in the interface. They are the same thing.
Roles
| Role | May do |
|---|---|
| Member | Work in the departments they belong to: run workflows, inspect runs, approve where they are a recipient. |
| Organization admin | Everything a member may do, plus departments, membership, connections, knowledge bases, spend limits and the audit log. |
| Platform admin | Provisions organizations and their first admin. Has no implicit access to any organization's data; an organization must be named explicitly. |
Sign-in
People sign in through your identity provider. Your provider tells us who somebody is; it never tells us what they may do. Roles and department membership are held in PromptOne and are checked on every request, so removing somebody takes effect on their next action rather than when a token expires.