Who can see what
This page explains who can read the metrics in the Portal and through ph ryoma, and how the system enforces those limits. Metrics exist to improve the process, not to score individuals.
Four principles
Only the person themselves, plus Owners and Admins who manage quotas, can see per-person usage. Everyone in an organization sees its projects as aggregated metrics. One organization can't see another organization's data. And the system doesn't rank people or projects; see Measurement.
Visibility table
| Metric | You | Member, Viewer | Owner, Admin |
|---|---|---|---|
| Your AI usage and quota | Yes | No | Yes |
| AI cost aggregated by project | Not applicable | The organization's projects | The organization's projects |
| Flow, AI, project health | Not applicable | The organization's projects | The organization's projects |
| Metrics by person, repo, issue, model | Yours only | No | No |
| Guardrails events with identity | Yours | No | No |
| The organization's audit log | No | No | Yes |
The roles are Owner, Admin, Member, and Viewer; see Roles and permissions. A Viewer is for BAs, POs, and PMs who work in the browser, and sees the same project metrics as a Member. A project admin sets the Guardrails and the members of one project; that role doesn't widen who can see metrics. Owners and Admins have project admin rights on every project.
Organizations are isolated
Every organization is a separate space: its members, projects, tasks, private resource store, locks, knowledge base, audit log, and metrics. Two layers enforce this, and the second stops anything that gets past the first.
- The application. Every query takes the organization from your sign-in session or token, never from a parameter you send. The organization in a URL such as
/v1/orgs/acme/...must match the one your token belongs to. - The database. Postgres Row-Level Security limits each transaction to the rows of one organization. Even a bug in the application can't return another organization's rows.
If you aren't a member of an organization, Tara answers 404 Not found for it, the same as for an organization that doesn't exist, so outsiders can't tell whether it exists. The same applies to a project outside your organization. Ryoma follows the same rule: it reads your organization and role from the Tara token every time and filters every query by the organization.
What other organizations can see of yours
Your organization's internal resources and everything else stay inside your organization. Your personal store (<your-handle>/<name>) is private to you: not even other members of your organization see it until you contribute a copy to the organization. Two things are shared. The official store (aiforge/<name>) is published by PhillipCLI platform staff and is visible to every organization. Public resources, whose owner chose to make them public, are labeled "Community", and other people install them only by the full name <owner>/<name>. A resource starts private (personal) or internal (organization) and becomes visible to everyone only when its owner makes it public. See Resources for the details.
The Projects section on the Portal
The Projects section shows delivery progress: the number of tasks by status, first-pass rate, rework rate, AI cost, the number of risk tasks, and the Flow and AI sections. Tara reads the data from Ryoma and filters by your current organization. You see the projects of the organization you have open, and the organization switcher at the top of the Portal changes it. A project can also be private: then only organization Owners and Admins and the project's members see it, and everyone else gets "not found". Private projects are on the Team and Enterprise plans; a project that is already private stays private if the organization moves back to Free.
Customer dashboards live on the Projects pages of the Portal, readable by every role of the organization.
The ph ryoma command
Anyone can run ph ryoma or ph ryoma usage to see their own data. The viewing commands ph ryoma projects, report, alerts, and estimate work on the projects of your current organization. The commands that change things, such as ph ryoma projects set, alerts set, and remove, are for Owners and Admins only. Calling a project you can't view returns an error.
View your own data
ph ryomaThe command prints converted cost and tokens, by project and by day, along with your position against your quota. When you run Claude Code through ph and have reached a threshold, Phillip also reminds you. Quotas only warn at 80% and 100%, and don't block work. To see another organization's data, switch with ph org switch <slug>.