Scopes and roles

A mailbox scope is tool@mbx_…, grp:name@mbx_…, or *@mbx_…. Groups are expanded when a grant is written, so adding a tool to a group in a future release does not silently broaden an existing grant. Effective authority is the intersection of a live mailbox grant and token scopes. An empty token scope list does not narrow the grant.

Group	Members
grp:read	get_identity, read_inbox, monitor_inbox
grp:intent	wants_to_move, wants_to_copy, wants_to_expunge, wants_to_send_draft
grp:direct	move, copy, trash, spam, archive
grp:draft	start_draft, edit_draft, patch_draft, reply_to_thread, discard_draft
grp:approve	approval_list, approval_status, monitor_approval, cancel_approval, approval_commit

set_flags and send_draft are not in a group. get_identity is callable by every active token even though it appears in grp:read for understandable role listings.

Mailbox roles

Role	Expansion
Reader	grp:read, plus approval status and monitoring
Operator	Reader, grp:intent, grp:draft, approval listing and cancellation
Approver	Reader, approval listing, decision/commit, and cancellation
Owner	* for that mailbox

The five direct filing scopes, send_draft, and approval_commit are gated for agents. Granting them requires explicit administrator confirmation; they are not part of a normal operator grant.

Organization capabilities use org:* names and are distinct from mailbox scopes. Organization admins receive organization-wide management authority; ordinary members receive the narrower member defaults. Inspect get_identity instead of reconstructing the effective result client-side.