Quin
opened 3 years ago
-
Allowing specific role to manage different secrets will complicate things a lot and currently there is no plan to support that.
As to helps/tips, please check latest version and let me know which permission needs to be elaborated.
-
Hi
I meant for there to be a role that only allows to manage all job secrets, so my employees can add/edit/remove them from any project and not have full access to the whole project.
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee |
Not assigned
|
Issue Votes (0)
Watchers (4)
Hi
I was wondering if there was an option to allow other Roles (say "Code Writer") to create Job Secrets. Currently, the only way I can figure this out is to allow a user full Project Management permissions, which isn't ideal.
As an aside, it'll be helpful is the hits/tips underneath the labels were more descriptive, rather than just "[something] administrative permission inside a project, including batch operations over multiple code comments." For instance, and example of what [it] does would be helpful for people to understand.