Governance Model
Roles & Permissions
Understand the 2asana collaborative framework and how project access is governed across different tiers of authority.
Tier 3
Admin
The project Owner is always an Admin.
Full infrastructure control. Authorized to manage membership, inject API keys, and decommission project nodes.
Tier 2
Editor
Authorized to manage strategic content.
Can define project Verticals, manage the Asset Registry, and configure the rules that guide AI analysis.
Tier 1
Member
The baseline observation tier.
Authorized to view all project data, morning briefs, and trigger on-demand synchronization workers.
Permissions Matrix
| Authorized Action | Member | Editor | Admin |
|---|---|---|---|
| View Project Data (Tasks, Members, etc.) | |||
| Edit Project Assets (Tools, Data Sources, etc.) | |||
| Edit Organization Structure (Departments, etc.) | |||
| Run On-Demand Sync & Analysis Jobs | |||
| Manage Project Rules & Status Updates | |||
| Edit Project Settings (e.g., Name, System Account) | |||
| Add or Remove Project Members | |||
| Delete ProjectOwner Authority Required |