ClickUp Permissions Matrix
Purpose
Single-page reference for who can do what in the Symphony Core ClickUp workspace. Resolves "can I delete this?", "can a Guest see that?", "should this contractor be a Member or a Guest?" without grepping across the workspace setup SOP, vendor onboarding SOP, and tag taxonomy. Powers the Admin guide, the QA Reviewer guide, and the new-joiner onboarding walkthrough.
Scope
- In scope: ClickUp's four built-in role tiers (Owner / Admin / Member / Guest) and how SC assigns them. Cross-cutting capabilities at workspace / space / folder / list / task / time-entry levels.
- Out of scope: GHL, Drive, GitHub, Slack permissions — see the per-platform docs in
05-platform/platforms-config/.
1. Role waterfall
Higher tiers inherit everything the lower tiers can do, plus their tier's additional capabilities. Demoting a role removes the additional capabilities; the user keeps the lower-tier ones.
2. SC role assignment policy
| Tier | Who in SC holds this | When to grant |
|---|---|---|
| Owner | Workspace Owner (the principals of Symphony Core LLC). Limit: 1-2 humans, ever. | At workspace creation. Transferring ownership is a deliberate succession event, not an ops convenience. |
| Admin | Account Manager(s). Currently 0-1 humans depending on staffing. | When a Member needs to manage spaces, status templates, or workspace-level tags. Default: keep the count small (≤3 total Admins including Owner). |
| Member | SC internal team (FT + retained contractors). | When the person needs visibility across multiple client folders or any access to SC Operations space. |
| Guest | External project-partner vendor teams, scoped to a single folder. See Project Partner Team Onboarding SOP §5. | When the person needs to act on a single client engagement (or single internal folder) only — never on the broader workspace. |
Default for any new joiner: lowest tier that lets them do the job. Promotion is cheap; demotion is awkward (other team members notice).
3. Capability matrix
✅ allowed · ❌ blocked · ⚠️ allowed but governed by canon (see footnote)
Workspace level
| Capability | Owner | Admin | Member | Guest |
|---|---|---|---|---|
| Edit billing / change plan tier | ✅ | ❌ | ❌ | ❌ |
| Transfer workspace ownership | ✅ | ❌ | ❌ | ❌ |
| Add/remove Members and Admins | ✅ | ✅ | ❌ | ❌ |
| Add/remove Guests | ✅ | ✅ | ✅¹ | ❌ |
| Toggle ClickApps (Multiple Assignees, Time Tracking, etc.) | ✅ | ✅⚠️ | ❌ | ❌ |
Edit status templates (incl. sc-status-01) | ✅ | ✅⚠️ | ❌ | ❌ |
| Edit space-level tag taxonomy | ✅ | ✅⚠️ | ❌ | ❌ |
| Edit workspace integrations (GitHub, Slack) | ✅ | ✅ | ❌ | ❌ |
¹ Members can add Guests only to folders they have permissions on. Practically rare in SC (Admins typically provision Guests).
⚠️ Admin actions on shared workspace surfaces are governed by clickup-structure-sync (structural changes) and tag-taxonomy §Governance rules (tag changes) — paired-update discipline applies.
Space level
| Capability | Owner | Admin | Member | Guest |
|---|---|---|---|---|
| Create / delete a space | ✅ | ✅⚠️ | ❌ | ❌ |
| Edit space settings (statuses, custom fields, default views) | ✅ | ✅⚠️ | ❌ | ❌ |
| View any space | ✅ | ✅ | ✅² | ❌ |
| Create folders within a space | ✅ | ✅ | ✅² | ❌ |
² Members see only spaces they've been granted access to. SC convention: all FT/retained Members have access to both Client Delivery and SC Operations spaces.
⚠️ Structural changes (add/remove/rename space, folder, list) pair with SOP §6 + memory + ticket-close per clickup-structure-sync.
Folder level
| Capability | Owner | Admin | Member | Guest |
|---|---|---|---|---|
| Create / rename / delete folder | ✅ | ✅⚠️ | ✅² | ❌ |
| Edit folder default views | ✅ | ✅ | ✅² | ❌ |
| Grant Guest access to a folder | ✅ | ✅ | ✅²,³ | ❌ |
| Read folder contents | ✅ | ✅ | ✅² | ✅³ |
³ Guest folder access is the standard scoping pattern. A Guest sees the folder + its lists + its tasks; nothing else in the workspace. Per Project Partner Team Onboarding SOP §5, grant Guest access to one folder only.
List level
| Capability | Owner | Admin | Member | Guest |
|---|---|---|---|---|
| Create / rename / delete list | ✅ | ✅⚠️ | ✅² | ❌ |
| Edit list-level views | ✅ | ✅ | ✅² | ❌ |
| Edit custom-field options on the list | ✅ | ✅ | ❌ | ❌ |
Task level
| Capability | Owner | Admin | Member | Guest |
|---|---|---|---|---|
| Create a task in a list you can see | ✅ | ✅ | ✅ | ✅ |
| Edit any task | ✅ | ✅ | ✅ | ✅ (within their folder) |
| Delete a task | ✅ | ✅ | ✅⚠️⁴ | ✅⚠️⁴ |
| Archive a task (right-click → Archive) | ✅ | ✅ | ✅ | ✅ |
| Set custom-field values on the task | ✅ | ✅ | ✅ | ✅ |
| Add tags to a task (from the approved set) | ✅ | ✅ | ✅ | ✅ |
| Assign a tag that doesn't exist yet | ✅⚠️ | ✅⚠️ | ❌ | ❌ |
| Add the only assignee | ✅ | ✅ | ✅ | ✅ |
| Add comments | ✅ | ✅ | ✅ | ✅ |
⁴ Don't delete completed work. Use cancelled status if a task shouldn't run, or native archive for cold storage (see Workspace Setup SOP §5.6). Deletion is irreversible and breaks any downstream links / time entries.
Time-tracking level
| Capability | Owner | Admin | Member | Guest |
|---|---|---|---|---|
| Log time on any task you can see | ✅ | ✅ | ✅⁵ | ✅⁶ |
| Edit your own time entries | ✅ | ✅ | ✅ | ✅ (until locked) |
| Edit someone else's time entries | ✅ | ✅ | ❌ | ❌ |
| Approve a submitted week | ✅ | ✅⁷ | ❌ | ❌ |
| Unlock an approved week | ✅ | ✅⁷ | ❌ | ❌ |
⁵ FT SC team members typically don't track time in ClickUp; they're on retainer. Time-tracking is required for the vendor flow.
⁶ Guests need the Can track time permission explicitly granted at the workspace level — not a default. See Project Partner Team Onboarding SOP §5.
⁷ The designated Approver (per ClickUp Timesheet Approval SOP §3). This is a role assignment, not an inherent Admin capability — multiple Admins can exist while only one is the Approver.
4. Common questions
Q: I want to give a contractor access to one client's work only.
A: Guest role, scoped to that client's folder. They'll see the folder + its active-work and reference lists + every task in them; nothing else in the workspace. Per Project Partner Team Onboarding SOP §5.
Q: I want a contractor to log time across multiple clients. A: That's a Member, not a Guest. Guests are scoped to one folder. Members see all spaces they've been granted access to. Cost trade-off: Members consume a paid seat; Guests are free up to 10 per Member seat (on Business plan).
Q: Can a Member edit the sc-status-01 status template?
A: No — that's Admin-only. Members can only act within the status set; they can't change the set itself. Same for custom-field options at the list/space level and the tag taxonomy.
Q: Can a Guest see tasks in another folder I happen to mention in a comment? A: No. Cross-folder task links rendered in their UI show as inaccessible. They see the link but can't open it.
Q: My Guest can't see the time tracker.
A: The Can track time permission is off by default for Guests. Workspace Settings → Members → that Guest → toggle Can track time ON. (Per Project Partner Team Onboarding SOP §5.)
Q: Can a Guest see other Guests in the workspace? A: No. Guests see only the folder they're scoped to and members of that folder. They can't enumerate the workspace user list.
Q: I want to delete a stale task.
A: Don't — set status to cancelled instead (still visible in the cancelled-status filter; auditable). True deletion is for spam/accidental-creation only, and even then prefer archive.
Q: Who can disable the Multiple Assignees ClickApp?
A: Owner or Admin. Why we keep it disabled: single-assignee-per-ticket working rule.
5. Lifecycle: adding and removing role-holders
Adding a new Member or Guest: see SC Task Management Workspace Setup SOP §9 (User Lifecycle) for the step-by-step procedure (invite, role assignment, space/folder grants, permissions toggle, smoke-test).
Demoting / removing a role-holder: same SOP §9. Order matters — revoke external integrations (Slack, GitHub) first, then ClickUp seat, so the person can't act on the workspace mid-revocation.
Vacation / temporary handoff: no UI mechanism — done by reassigning their open tickets to a delegate per the Role Handoff sub-section in ClickUp Ways of Working §Roles.
6. References
- SC Task Management Workspace Setup SOP §4.3 Members & roles — authoritative source for the assignment policy.
- Project Partner Team Onboarding SOP §5 Platform access provisioning — Guest seat provisioning detail.
- ClickUp Ways of Working §Roles — the 4-role per-ticket model (Creator / Assignee / QA Reviewer / ClickUp Admin) — orthogonal to this doc's workspace-tier model. Don't conflate: this doc is about ClickUp's built-in seat tiers; the playbook §Roles is about who-does-what on a per-ticket basis.
- ClickUp Timesheet Approval SOP — the Approver capability (footnote ⁷ above).
- SC ClickUp Tag Taxonomy §Governance rules — tag-add permissions detail.
clickup-structure-syncworking rule — structural-change discipline.
Revision History
| Date | Version | Change | Author |
|---|---|---|---|
| 2026-06-14 | 1.0 | Initial release. Single-page reference for the 4 ClickUp seat tiers (Owner/Admin/Member/Guest) with capability matrix across workspace/space/folder/list/task/time-tracking levels, SC role-assignment policy, common questions, and lifecycle pointers. | Symphony Core Systems Team |