Permissions for Solution groups/sections
Vasken Bakalian
Assuming this request https://smartsuite.canny.io/feature-requests/p/organizing-solutions-into-folders will be developed and we will have Solution grouping in any sort or form, it would be very useful to set permissions to the whole group.
Will elaborate more by an example:
I have my paid plan where I have my freelace/agency setup & systems like CRM, projects, Finances ..etc
Also I have another set of solutions for content, where I create Template like solutions to record looms.
I also have another group for Client solutions, these could be for demo/aftersales purposes, or just developing them temporarily until I move the solution to the client workspace.
Additional groups/sections might be for testing, experiments, learning, teaching ... etc
And I'll have colleagues who will join my workspace only for the internal management group or the client demo group and don't have to see or touch the content or experiments or any of the noise left.
I know I can set each solution one by one, but since each group may have 10 or even up to 20 solutions, it would be very useful to set permissions on the group level
Currently I am using colors, sometimes numbers (to sort the solutions)
Jon Darbyshire
Thank you for posting, Vasken Bakalian! I have a few more questions for you:
- Can you provide more details on the types of permissions you would like to set at the group level? For example, are there specific actions you would like to restrict or allow?
- How would you like the permission settings to behave when a solution is moved from one group to another?
- Could you elaborate on the roles of the colleagues who will join your workspace? What specific access or restrictions should each role have?
Vasken Bakalian
Jon Darbyshire
- I'm thinking of a similar setup as the solution level permissions itself.
With a same effect of applying the same permissions to each and every solution but doing it once for all.
- The new group permissions apply immediately.
before #3, the overriding of permissions come here.
I think solution level permissions overriding group permissions will solve this, even when solutions are moved.
- I'll usually need either Solution Creators and/or General Access members.
From my perspective, the group level permissions could be more high level since I either need a member to see or not see the whole section/group.
Since for anything additional we might need, we can always add & override on the solution level, but in most cases, I don't want the Ops person to see the noise of my experiments, tests and solutions for content creation.