Roles & permissions

Brev has two independent role systems: an organization role applied to every member (Owner / Admin / Member / Observer / Guest) and a team role applied per team (Admin / Member). Most permission decisions are evaluated against the org role; team admin is a localised escalation that lets non-admin members run their team's goals.

Organisation roles #

Owner

Same rights as Admin. Each organization has exactly one Owner, usually whoever created it. Only the Owner can hand the role to someone else, by transferring ownership on Settings → Members, which makes them an Admin.

Admin

Runs the workspace: can edit or delete any goal regardless of ownership, manage cadences, teams and members, change product and AI settings, and open Billing and usage analytics. Cannot make someone else Owner. This is the role you grant to anyone running the workspace day-to-day.

Member

The default for new invitees. Can create goals they own (individual, or for teams they're on), edit and delete goals they own or are Team Admin over, add check-ins, create private custom views, and invite people as Members. Cannot create company-owned goals, manage cadences, teams or members, or change anyone's role.

Observer

Read-only for goals, actions and meetings. Sees the workspace (subject to per-goal visibility), reads cadences and opens views, but cannot create, edit or check in on goals, even ones they own or that are shared with them, and cannot edit actions or manage meetings. Use for executives or auditors who need to see progress without participating. Observer is chosen when inviting someone; an existing member cannot be switched to Observer.

Guest

Sees only what is explicitly shared with them (a goal, a view, a meeting or an artifact), and only to read. Cannot create, edit or check in on anything, cannot invite anyone, sees only themselves in the member list, and gets no weekly digest. Use for contractors or partners who should follow specific work without seeing the rest of the workspace. Only Owners and Admins can make someone a Guest, when inviting them or by changing an existing member's role.

Team roles #

Team Admin

Can edit and delete every goal that names this team (or one of its subteams) in its team list, and goals owned by anyone on the team, even if the Team Admin isn't a listed owner. Can also create goals for those teams and name their members as owners. The team's lead (by default whoever creates the team) is made Team Admin automatically; Org Admins add more in the team's membership editor.

Team Member

Counts as 'on the team' for goal creation: can create team-owned goals for this team, and edit or delete goals they personally own. No special powers over other members' goals.

What each role can do #

The table below lists every CRUD-shaped action exposed in the UI. Org-A = Org Admin or Owner. Team-A = Team Admin of the team that owns the object.

Goals · create (individual)

Owner / Admin, with anyone as owner. A Member can make themselves the owner, or, as a Team Admin, a member of that team or its subteams. Observers blocked.

Goals · create (team-owned)

Owner / Admin, for any teams. A Member only for teams they're on or are Team Admin over (including subteams): every team picked must qualify, and the picker lists only those teams.

Goals · create (company-owned)

Owner / Admin only. Members see Company greyed out in the owner picker, with a tooltip explaining why.

Goals · edit / delete

Owner / Admin / a listed owner / Team Admin of the goal's team / Team Admin of a team that any listed owner is on. Team Admin includes the team's lead and admins of a parent team. Observers and unrelated members blocked.

Actions · edit / delete

Owner / Admin / the action's assignee / Team Admin of a team the assignee is on (or of a parent of that team). Unassigned actions: Owner / Admin only. The host of a meeting an action came from, or the owner of its series (for a private meeting, only its host), can also edit it, assigned or not, but not delete it or change someone else's pending suggestion (they can keep or dismiss it). Observers blocked. Creating an action and assigning it to someone else hands it over. Keeping or dismissing a suggestion is separate: its assignee can, anyone who can see an unassigned one can, and so can the host of the meeting it came from (organizer or series owner; for a private meeting, only its host). Owners and Admins get no extra keep-or-dismiss right.

Tags · create

Owner / Admin / Member. Observers and Guests cannot. Renaming and deleting a tag: Owner / Admin only.

Check-ins · add / edit / delete

Adding: same as goal edit, plus anyone the goal is explicitly shared with via the People / Teams dropdowns (not Observers). Sharing a goal grants check-in rights but not edit-the-goal rights. Editing or deleting an existing check-in: its author or an Owner / Admin.

Cadences · create / edit / delete

Org Owner / Admin only. Members and Observers participate by being added to events.

Cadence events · edit

Owner / Admin, the event's organizer, the cadence owner, participants, and people the host added as editors. Viewer shares and Observers cannot edit. A private event can be edited only by its host and by Owners / Admins who attended. See Cadence event for what's editable on a single event. Notes/agenda are co-edited inside the artifact surface.

Event artifacts · create / edit / rename / delete

Available to everyone (no feature permission). Access is by event participation: event organizers and participants can create, edit, rename, and delete the artifacts on events they're part of, as can anyone the host has added to the event as an editor; read-only viewers can read artifacts but not modify them. An artifact's owner can always edit, rename, and delete it on its own page, and in the Artifact tab of any event they can open, and can share it with people or teams as editors, who can then edit, rename, delete, and share it too, except while a meeting it's on is locked. Anyone who can edit an artifact, including organizers, participants and editors of a meeting it's on, can change who it's shared with. People it's shared with as Viewers can read it and its comments but can't comment, unless they can through a team, a meeting, or org-wide access. See Artifacts on events.

Artifact templates · save / manage

Available to everyone (no feature permission). Anyone who can open an artifact (as its owner, a meeting participant, or through a share with them, their team, or the organization) can save it as a personal template; org admins can create org-wide templates; linking a template to a cadence is limited to that cadence's members, its owner, and org admins. The system default-template library is managed by Brev. See Artifacts on events.

Teams · create

Any active org member, by typing a new team name into the team picker of a goal. Settings → Teams and the sidebar's Add new team button are for Owners / Admins only. The team's lead (by default the creator) becomes Team Admin.

Teams · edit / delete

Org Owner / Admin only. Team Admins can't rename or delete a team. That prevents accidental loss of a team's goals.

Team membership · add / remove / change role

Org Owner / Admin only, from Settings → Teams or a member's Manage member dialog on Settings → Members. Being Team Admin doesn't add this right.

Members · invite

Any active org member can invite people as Members, from Invite team in the main sidebar. Owners / Admins can also invite from Settings → Members and choose Admin, Member, Observer or Guest. Guests cannot invite anyone. No invitation makes someone Owner.

Guest · what they can see

Only the goals, views, meetings and artifacts shared with them directly, read-only. Nothing else in the workspace appears for them, and the member list shows only themselves. Making someone a Guest is for Owners / Admins only.

Members · change role

Owner / Admin, between Org Member, Org Admin and Org Guest. Only the Owner can make someone Owner, which transfers ownership and makes the previous Owner an Admin. Nobody can change their own role, and Admins can't change the Owner's.

Members · deactivate / reactivate

Org Owner / Admin only (row ⋯ menu, the Status pill, or bulk actions on Settings → Members).

Custom views · create / edit / delete

Any active member can create one; only its creator edits or deletes it. A view is private to its creator unless they share it with specific people or teams (read-only for them). Admins don't see another user's custom views. Only Org Owner / Admin can make a view org-wide.

Team views · exist

Auto-created when a team is created. No separate CRUD; they live as long as the team does.

Agents · create / rename / toggle / delete

Any active member. Each scheduled agent and Operator conversation is visible to, and managed by, only the person who created it.

Agents · run Operator

Org Owner, Admin and Member. Observers and Guests can't run Operator anywhere (the app, Slack, Teams, the Brev Recorder apps for iOS and Mac, or the CLI), and nothing runs it for them: their scheduled agents, Operator jobs and AI check-in drafts for goals they own are declined too. A role change applies to the next run.

Product / AI settings

Org Owner / Admin only. This includes feature toggles, terminology, time periods and fiscal-year start, and check-in defaults. Everyone can open the Meeting agent page and set their own auto-join; its Appearance and meeting-type sections are admin-only.

Billing · view + manage

Org Owner / Admin only, in the app and through the CLI and MCP tools (credit grants, invoices, AI usage and model usage). Billing holds the subscription, AI credit balance and grants, invoices and payment method; Plans compares plans. There is no separate AI usage page for members, though everyone still sees the low-credit banner and whether AI is paused.

Usage analytics (Alignments, Check-ins, Integrations)

Org Owner / Admin only, and only where your workspace has usage analytics turned on. Includes the goal-discussion ranked list, the per-member check-in cadence table, and the integration-usage table.

Edge cases worth knowing #

• Sharing widens check-in, not edit. A Member shared on a goal via the People dropdown can submit check-ins, but cannot rename or delete the goal. Same applies to team-share. It grants check-in rights to everyone on the shared team without making them owners. Observers can't check in even when shared.
• Team Admin > goal Owner for editing. If a Team Admin's team appears in the goal's team list, they can edit and delete the goal even if they aren't listed as an owner. This is intentional. It's how managers maintain their team's goals when an IC owner is out.
• Cadences are admin-only on purpose. Brev treats cadences as part of the operating system of the org (when status meetings happen, who's expected to attend). Membership in a cadence event is separate and looser; participating doesn't grant editing the cadence itself.
• Custom views are personal data. Even Admins cannot see another user's custom views or filter chips unless the creator shares the view with them. To share a slice of goals across the whole org, an Admin can make a view org-wide, or use a team view.
• Anyone can invite, as a Member. Any Member can send an invitation, and it joins the invitee as a Member. Choosing Admin, Observer or Guest, or pre-assigning a team, is for Owners / Admins. Nobody is invited as Owner: ownership only moves by transfer.

Changing someone's role #

1. 1
   Go to Settings → Members

   Open Members (Owners and Admins only). The table lists every org member with their Org Role and Status.
2. 2
   Click the member's Org Role pill

   The pill in the Org Role column opens a list of roles: Org Member, Org Admin and Org Guest, plus Org Owner when you are the Owner. Your own row's pill is greyed out, and so is the Owner's row unless you are the Owner. Observer can only be chosen when inviting someone, not here.
3. 3
   Pick the new role

   Member, Admin and Guest apply straight away, with no confirmation. The member gets the new role's access on their next page load; they don't need to sign out and back in.
4. 4
   Transferring ownership

   Picking Org Owner opens Transfer Organization Ownership, which lists what changes: they get full control, you lose owner privileges and become an Admin, and only they can transfer ownership again. Click Transfer Ownership to confirm, or Cancel.

Usage profiles #

Every Owner, Admin and Member draws on the workspace's shared AI credits under a usage profile. Everyone starts on Standard. Owners and Admins can move a member to Power or Restricted in the Usage profile column on Settings → Members, and the change applies from that member's next request. Observers and Guests can't run the agent, so no profile applies to them. Being an Admin doesn't give you a bigger profile.

• Monthly allowance. Each profile includes a number of credits a month. When a member passes theirs, every Owner and Admin gets one inbox notification for that member that month. The member keeps working as long as the workspace has credits.
• Requests at once. While the workspace runs on AI credits, each profile limits how many agent requests a member can have running at the same time: Restricted the fewest, Power the most. Past the limit, Brev asks the member to wait for one to finish and send again.
• Months reset on the 1st. Allowances count from the first of each calendar month (UTC).