Custom snippet permissions
Description
Our primary need here is that snippets are accessible outside the namespace they are created in.
Proposals:
- Allow snippets behave like projects in terms of permissions and allow them to be shared to groups or other users.
Context:
- We have set private as our default visibility level for projects, snippets and groups.
- We have set private as the only available visibility level for non-admin users.
- We have a central group in which users can share projects to so others can have access to those projects (this is primary for projects created/forked into user namespaces).
So far, this has worked for us as it provides privacy for all users and groups, while allowing for sharing of access easily and quickly to users with various permissions.
As of late, some users have been creating snippets, but have been unable to share them if they create them in their own namespace. Only when they create the snippet in a specific project that is then shared to the central group will others be able to see the snippet. The downside to this is that if a snippet has nothing to do with a project, the user then has to create a whole new repo to share that one snippet; furthermore, if they want to share a single snippet to a specific user, they need to create another repo just to do that as well.