What is the challenge? |
Some features or initiatives are sensitive, so we would like to be able to set record level permission restrictions |
What is the impact? |
Anyone who might come across work that isn't being widely publicised in the org |
Describe your idea |
We'd like to be able to set permissions against specific records, to make them visible to a specific user set, without having to do this at the workspace level. We want to keep the workspace available, but restrict particular records. |
Thank you for your idea. As noted, permissions are currently set at the workspace level. For the use case mentioned here, we would recommend keeping a separate workspace for projects or records that need not be visible for others within the workspace. Since it is possible to move records between workspaces, you could start in a more restricted workspace and then move the record once it reaches a point for more general knowledge.
Given the option listed above and historical permissions-related feedback, we are unlikely to implement this idea at this time. We hope you can understand.