Roles and permissions
This page tells you what you can do on Tara, whom to ask for permissions, how seats are counted, and who can see your metrics.
Permissions belong to an organization
Each person has exactly one role in each organization they belong to, and the same account can have different roles in different organizations. Under an organization are projects. A project is one product or repo, and it has its own tasks, metrics, and Guardrails.
Four roles
| Permission | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| See tasks, acceptance results, and dashboards of a project | Yes | Yes | Yes | Yes |
| Approve tasks on the Bandum website | Yes | Yes | Yes | Yes |
| Use Phillip, run agents, install resources | Yes | Yes | Yes | |
Publish personal resources (your own store, <your-handle>/<name>) | Yes | Yes | Yes | Yes |
| Publish or contribute resources to the organization (no review; see the publish policy below) | Yes | Yes | Yes (default policy) | |
| Create projects | Yes | Yes | Yes | |
| Make an organization resource public, set the publish policy, set organization Guardrails | Yes | Yes | ||
| Invite and remove members, change roles (except Owner) | Yes | Yes | ||
| Configure sign-in (GitHub App, SSO, domains) | Yes | Yes | ||
| Billing, change plan, delete or transfer the organization, appoint Owners | Yes |
Sensitive actions such as changing roles and yanking a version of an organization resource need an Owner or Admin. Changing roles needs a Portal sign-in session, and a personal token, which is for everyday work, can't do it.
Who can publish to the organization
The organization setting Who can publish to this organization (Portal: Settings, then General) has two values. Members and admins is the default: Owners, Admins, and Members publish. Admins only limits publishing to Owners and Admins. Viewers never publish to the organization, whatever the setting. Everybody, Viewers included, can still publish to their own personal store. Changes to the setting are written to the audit log.
Seats
Owners, Admins, and Members take a seat, because they use AI. Viewers are free, and they are meant for BAs, POs, and PMs who work only in the browser. The Free plan has 7 seats, and the Team plan has no seat limit (see Pricing). When the seats are full, Tara refuses new invitations and role changes that would need a seat, with the seat_limit error. Ask an Owner to free a seat, as described in Troubleshooting.
Project admin
A project can have its own Project admin. A Project admin sets the project's Guardrails, adds and removes project members, and edits the project's settings. The person who creates a project becomes its Project admin. Owners and Admins of the organization have Project admin rights on every project.
Platform staff
Platform staff is not a customer role. It is a flag on PhillipCLI's own accounts, used to review the official store (aiforge/<name>, in the Portal under Settings, then Platform), set the platform floor for Guardrails, and operate the service. If you work for a customer, you never need it.
Grant and revoke roles
An Owner or Admin changes roles in the Portal under Settings, then Members, or with commands. Every role change is written to the audit log.
ph org members # members and roles
ph org members set-role <login> admin # change a role
ph org members remove <login> # remove a memberA role takes effect from the next request. Only an Owner can grant or revoke Owner, and the last Owner can't be demoted. To invite people, see Create or join an organization.
Who does what with resources
Nobody reviews your organization's resources by hand. A version that passes the automated scanner is released at once, signed, and visible to every member. A person can publish to their personal store and then contribute a copy to the organization. Only the official store (aiforge/<name>) has a review step, done by platform staff. For personal resources, the owner publishes and yanks them. Anyone who signs in can report a suspicious resource with ph tara report.
Who can see which metrics?
| Metric | Who can see it |
|---|---|
| Your AI usage and quota | You, and Owners and Admins for quota purposes |
| Metrics aggregated by project (Flow, AI, project health) | Everyone in the organization, Viewers included, in the Projects section |
| Per-person metrics, by repo, by model | Only that person, and Owners and Admins |
| Guardrails events with identity | Owners and Admins |
| Tara's audit log | Owners and Admins of the organization |
Data is isolated between organizations. People in one organization never see another organization's data, and the database enforces this. For details, see Who can see what.
Custom roles
Custom roles, for example a "Reviewer" who can approve resources but can't manage members, are planned for the Enterprise plan. There is no date yet.
Don't confuse this with a resource's roles
The roles field in a resource's metadata.forge is something different. It lists the job roles the resource suits, such as PO, BA, Dev, and Test. This field serves only search and suggestions, and grants no permissions.