Roles & permissions
Last updated 30 September 2026
Yaumiyya has no separate "manager" or "reviewer" account types. What you can do depends on your relationship to a meeting (owner or sharee), your place on a plan (owner or member), whether you are an approver or assignee, whether you have paid access, and the admin flag.
| Role | How you get it | Can | Cannot | Verified |
|---|---|---|---|---|
| Meeting owner | You created the meeting | Everything on the meeting: edit transcript, rename speakers, create/update/approve minutes, approve and assign actions, translate, share, export, delete | Delete while a bot is in the call or processing is running | UI (all tested flows used the owner) |
| Sharee (team member a meeting is shared with) | Owner shares via Share with your team | Read transcript, minutes and actions; Ask AI about it (charged to their own pool); export | Change anything; translate; retry; create minutes ("Only the meeting's owner can have them made"); see the recording or its cost | Code (lib/meeting-access.ts, migration 0066) |
| Plan owner | Pays for a plan with seats | Invite people (links), set per-member monthly credit limits, remove members, buy credits | n/a | UI (invite/withdraw); rest code |
| Plan member | Accepted an invitation | Spend the owner's credits; see own usage and limit; Leave this plan | Buy credits (the Plan page shows a read-only pooled view); see the owner's meetings unless shared | Code (components/team-panel.tsx, pooled-upgrade.tsx) |
| Assignee | Owner assigns an action to you | Change its status and notes; acknowledge (Got it / Needs clarification) | Assign it to others (owner only) | Code (migrations 0067, 0102); self-assignment UI |
| Approver | Chosen in "Who approves these minutes?" (1–10 people on the plan) | Approve, or Return with a note (required, ≤ 500 characters) | Edit minutes while in review | Code (lib/minutes/approval.ts); self-approval UI |
| Admin | profiles.is_admin | /admin: slips, users, credits, contracts, spend, vendors; grant/remove admin | Read other people's meetings (deliberately returns 404) | Code only. Role identified in application implementation, but UI workflow could not be safely verified during this documentation run. |
Plan-based entitlements#
| Entitlement | Trial / never paid | Paid access (approved slip, active plan or contract) | Verified |
|---|---|---|---|
| Longest meeting | 30 minutes | Recordings 1 h, uploads 2 h | Landing page text (UI); code lib/entitlement.ts |
| Join online (bot) | Locked: "Buy credits to unlock" | Unlocked | Unlocked form UI; locked panel code |
| Editors (seats) | 1 | Personal 1 · Team 3 · Business 10 · Council 4h 3 · Council 8h 5 · Government 20 | UI (Team "3 editors"); rest code |
| Approval by others | No | Multi-seat plans | Code |
| Free AI actions / month | Trial: 3 Ask, 1 draft, 5 edits (once) | Personal 2/1/5 · Team 5/2/20 · Business 12/4/40 | UI (Settings, Team plan) |
| Library quota | 5 docs · 25 MB · 100 pages | e.g. Team 200 docs, 3,000 pages / month | Team UI; rest code |
Hard monthly caps for everyone: 60 questions, 30 drafts, 150 edits (Settings text, UI).
Leftover "Pro" wording#
The code still contains "Pro feature" gates (analytics, PDF export, task list) in lib/plans.ts. They are all switched on for every account, so they never block anyone today. (VERIFIED THROUGH CODE)