-
Notifications
You must be signed in to change notification settings - Fork 0
Collaboration
github-actions[bot] edited this page Aug 15, 2026
·
1 revision
Collaboration is designed for clear ownership and intentional sharing—not for broadcasting every personal task by default.
| Role | What it means |
|---|---|
| Owner | Controls the list, sharing, and collaboration boundary. |
| Editor | Can contribute to authorized shared work. |
| Viewer | Can see shared work without editing authority. |
The database enforces access with authorization predicates and Row Level Security. Interface controls explain permissions, but the database—not a button—is the security boundary.
- Share only the list relevant to the collaboration.
- Confirm the invited person’s account and intended role.
- Use activity and shared-work views to understand what changed.
- Revoke access when the collaboration ends.
Dependencies represent real prerequisites and can prevent premature completion. Attachments stay private to authorized collaborators; do not use them to share secrets.
Read Task dependencies and Task attachments for the complete model.