Manage roles
Admin › Roles is where Org Admins assign Hub roles and set two organization-wide policies: who can create projects, and when unused projects are archived.
Assign a role
- Open Admin › Roles.
- Under Add an assignment, pick a Role.
- In User email or group name, enter a person's email or a group's name (for example
Finance). - For Delegated Admin, choose a Scope:
- A department: pick the department.
- Someone's reporting subtree: enter the manager's email as Subtree root (manager email).
- Select Add assignment.
The Role assignments table lists every assignment with what it's assigned to and its scope. Members of the built-in admin group appear as Org Admins without an assignment. Remove an assignment with the remove button on its row.
| Role | Can |
|---|---|
| Org Admin | Everything: policies, roles, all projects |
| Delegated Admin | See and manage projects in one department or manager subtree |
| Auditor | Read-only everything, including the audit log |
| Builder | Create projects (when not everyone can) |
| Approver | Review integration requests. Requests are routed to the approvers set per integration in Admin › Integrations; an Approver assignment here doesn't route requests on its own yet. |
Assignments and removals are audited (rbac.assign, rbac.unassign).
Who can create projects
Under Policies, Everyone can create projects is on by default. Turn it off to limit project creation to people or groups with the Builder role. Org Admins can always create projects.
Stale projects
Also under Policies:
| Setting | Default |
|---|---|
| Nudge the owner after | 60 days without opens |
| Archive this long after the nudge | 30 days |
Each value is a whole number of days between 1 and 3650. Select Save. See Project lifecycle.
Within a project
Owner, developer and viewer rights are per project, and who can open an app is its Access setting. See Project permissions and Who can open an app.