Hub roles
Hub roles decide who administers vastframe itself: who sees the admin console, who manages projects across the organization, and who can create projects at all. They are separate from app access, which decides who can use an app, and from project permissions, which decide who can change one project.
The roles
| Role | Can | Scope |
|---|---|---|
| Org Admin | Everything: policies, integrations, roles, sign-in, people, every project | Whole organization |
| Delegated Admin | See and manage projects whose owner is in their scope: the org tree, cost, audit events, kill switch, archive, transfer | One department, or one manager's reporting subtree |
| Auditor | Read everything, including the audit log and every project page. Changes nothing. | Whole organization |
| Builder | Create projects | n/a |
| Approver | Review integration access requests (routing uses the approvers set on each integration) | Per integration |
Roles are assigned to people or to directory groups. Group membership is resolved transitively.
Org Admin
Members of the built-in admin group are Org Admins automatically. On a self-hosted installation this group is IT Admins unless the installation sets another name (TC_ADMIN_GROUP). Anyone can also be made an Org Admin with a role assignment.
Delegated Admin
A Delegated Admin needs a scope when you assign the role:
- A department: every project whose owner's directory
departmentmatches. - Someone's reporting subtree: every project owned by that manager or anyone below them.
A typical use is Finance's IT liaison, scoped to the Finance department. Delegated Admins see Admin › Org, Projects, Cost and Audit log, filtered to their scope. Org-wide pages such as Integrations, Policies and Roles are hidden from them.
Auditor
Auditors open every admin page and every project page read-only. The console shows a read-only banner and disables actions; the API refuses every change with 403 (READ_ONLY on project routes, FORBIDDEN on admin routes, both saying "Auditors have read-only access"). Auditors may run read-only SQL in the Database Studio and download files.
Builder
By default everyone can create projects. An Org Admin can clear Everyone can create projects on Admin › Roles; after that only people or groups with the Builder role can.
Approver
Integration approvers are set per integration in Admin › Integrations and are routed requests for that integration. Anyone listed there counts as an Approver. You can also assign the Approver role on Admin › Roles, but today that assignment doesn't route any requests to the person: only the approvers listed on an integration (and Org Admins) can decide its requests. See Access requests.
Assign a role
See Manage roles for the steps.
On every installation today, role assignments are stored in the Hub and managed on Admin › Roles. Reading Hub roles from Microsoft Entra app roles on the vastframe app registration is planned for Azure installations.
Admin changes are labelled
When an admin acts on a project they don't own, every audit row records the role they acted as, for example "Adele Vance (Org Admin)". The project page shows a banner: "You're viewing Ben Carter's app as Org Admin. Changes are audited."