As we’ve hinted before, we are looking to deprecate Contributor Space access. Now that we have proper Database access and automatic sharing for assigned people and groups, there’s no need for the access level that tries to imitate both.
We’d like to make the transition as smooth as possible, and we need your help. If you’re currently using the Contributor access or have just transitioned from it, please answer a few questions about the desired access for each Database.
Here is an example. Dev Group has Contributor access to Project Management Space with three Databases: Objectives, Projects, and Tasks:
| What should they be able to do? | Answer |
|---|---|
| See and comment all Objectives | Yes |
| Edit Objectives they are assigned to | No |
| Create Objectives | No |
| ——— | |
| See and comment all Projects | Yes |
| Edit Projects they are assigned to | Yes |
| Edit Projects they are assigned to even if they lose Space access | Yes |
| Create Projects | No |
| ——— | |
| See and comment all Tasks | Yes |
| Edit Tasks they are assigned to | Yes |
| Edit Tasks they are assigned to even if they lose Space access | Yes |
| Create Tasks | Yes |
| Edit Tasks they create | Yes |
| Edit Tasks they’ve created even if they lose Space access | Yes |
Please pick the most critical Contributor use case in your workspace, copy-paste the table into your reply, and replace the Databases with yours.
Thank you!