Tilt Base gives each person a role for the whole organisation, and optionally a role in each team they're in. Roles are the same in every organisation. This page explains what each gives, how they combine, and what each person sees.
## Organisation roles
<table header-row="true">
<tr>
<td>Role</td>
<td>What they can do</td>
</tr>
<tr>
<td><span color="blue_bg">Admin</span></td>
<td>Everything. Build, publish and share every plugin, and approve requests, including their own, which is recorded as self-approved. Manage members, teams and organisation settings. Set up transcription, verified domains, SSO and directory sync. Read metrics, activity and the audit log.</td>
</tr>
<tr>
<td><span color="purple_bg">Contributor</span></td>
<td>Build, publish and share every plugin. Create teams. Read metrics and activity. Contributors can't approve requests unless nominated as approvers, and can't manage members or organisation settings, set up transcription or SSO, or read the audit log.</td>
</tr>
<tr>
<td><span color="gray_bg">Member</span></td>
<td>No role. Uses the published plugins they receive through their AI. Unless they hold a team role or approve plugins, they don't use the web app.</td>
</tr>
</table>
Only Admins manage members, organisation settings, transcription, and SSO and directory sync. A firm's IT person or managed service provider who sets up SSO needs Admin.
## Team roles
In a team, each person holds a team role, or none, which shows as Member.
<table header-row="true">
<tr>
<td>Team role</td>
<td>What they can do for that team</td>
</tr>
<tr>
<td><span color="blue_bg">Admin</span></td>
<td>Build, publish, share and approve the plugins the team owns, but never approve their own request. Add and remove people, give team roles and **Approver** ticks, require approval, rename and delete the team. Read the team's metrics, activity and audit log entries.</td>
</tr>
<tr>
<td><span color="purple_bg">Contributor</span></td>
<td>Build, publish and share the plugins the team owns. Read the team's metrics and activity.</td>
</tr>
<tr>
<td><span color="gray_bg">Member</span></td>
<td>Nothing to manage. Receives the plugins the team receives.</td>
</tr>
</table>
A team Admin isn't an organisation Admin: their role covers only that team.
### The Approver tick
An approver isn't a role. Approvers approve or decline requests to publish plugins in their scope, see those plugins read-only, and read their usage.
- The organisation's approvers are nominated in Settings › Organisation › General, and approve every plugin.
- A team's approvers have the **Approver** tick on the team's page, and approve the plugins the team owns.
Anyone can be an approver, with or without a role. See <mention-page url="https://app.notion.com/p/41b4815eed4f819b94baf97c828d62ce">Approval</mention-page>.
## How access adds up
A person holds at most one organisation role, at most one team role in each of their teams, and any approver nominations. They can do everything those give them together.
- A role for the whole organisation reaches every team. An organisation Contributor edits every team's plugins without being in the team.
- A team role reaches only that team's plugins and people. Someone who is a Member of the organisation and a Contributor in Litigation builds Litigation's plugins, and nothing else.
- Every role and approver nomination includes reading usage for its scope. Team roles and ticks read only their team's share.
## What a Member sees
Someone with no role and no approver nomination anywhere sees the "You're set up for Tilt Base" page whatever they open in the web app. It tells them their administrators manage the organisation's plugins, and to sign in when their AI asks to connect Tilt Base. Someone in more than one organisation can switch organisation there.
Members use plugins through their AI. See <mention-page url="https://app.notion.com/p/41b4815eed4f817fb4e3eaaa83d6218f">Ask your AI for work</mention-page>.
## What each person sees in the web app
### Sidebar
<table header-row="true">
<tr>
<td>Item</td>
<td>Who sees it</td>
</tr>
<tr>
<td>**Overview**</td>
<td>Everyone who uses the web app</td>
</tr>
<tr>
<td>**Plugins**</td>
<td>Anyone who can edit or approve plugins, for the organisation or a team</td>
</tr>
<tr>
<td>**Inbox**</td>
<td>Anyone who can approve plugins: organisation Admins, team Admins and approvers</td>
</tr>
<tr>
<td>**Library**</td>
<td>Anyone who can edit plugins: Admins, Contributors, and team Admins and Contributors</td>
</tr>
<tr>
<td>**Metrics**</td>
<td>Everyone who uses the web app</td>
</tr>
</table>
### Organisation settings
The account menu's **Organisation settings** opens the first of these you can use.
<table header-row="true">
<tr>
<td>Page</td>
<td>Who sees it</td>
</tr>
<tr>
<td>**General**</td>
<td>Organisation Admins</td>
</tr>
<tr>
<td>**Members**</td>
<td>Organisation Admins</td>
</tr>
<tr>
<td>**Teams**</td>
<td>Organisation Admins, Contributors and approvers see every team. Team Admins, Contributors and Approvers see their own teams.</td>
</tr>
<tr>
<td>**Transcription**</td>
<td>Organisation Admins</td>
</tr>
<tr>
<td>**SSO and directory**</td>
<td>Organisation Admins, once Tilt switches SSO on</td>
</tr>
<tr>
<td>**Activity**</td>
<td>Everyone who uses the web app. Team roles and ticks see their teams' deliveries.</td>
</tr>
<tr>
<td>**Audit log**</td>
<td>Organisation Admins, who read every entry, and team Admins, who read their team's</td>
</tr>
</table>
## Related
- <mention-page url="https://app.notion.com/p/41b4815eed4f81dc92c6cf6bdd40f80e">Members and invitations</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f817e9c85d2a5f5f1fa9f">Teams</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f819b94baf97c828d62ce">Approval</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f8141b20af00c49c519cd">Owners and receivers</mention-page>
- <mention-page url="https://app.notion.com/p/41b4815eed4f8106881cd767f9a68dba">Roles from your directory</mention-page>