Absolutely agree. I envisage, on a project level, being able to assign view/edit permissions, and on a task level, if a user has not been granted project access, they may only view the tasks they’ve been assigned to or @-mentioned in.
Add permission to project
reports,
design-manager,
marketplace-solutions-directory,
sales-activity-feed,
academy,
ads,
conversations-inbox,
help-resources,
help-resources-community,
workflows,
user-management-permissions,
social,
sales-documents,
account-settings,
object,
products-line-items,
tasks,
chatflows,
marketing-email,
content,
partner-tools
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Private Projects | 28 | 13429 | April 22, 2024 | |
| Making Projects That Are Only Visible to Chosen Team Members | 1 | 1303 | February 7, 2023 | |
| User permissions - Edit v Delete | 0 | 20 | July 15, 2026 | |
| Permissions Based on Task Assignment | 0 | 213 | February 24, 2025 | |
| Tasks, Need Create Permission, edit, and delete permissions. | 1 | 420 | May 28, 2026 |