19 Vote

Allow non-owner to edit secrets

  • Shared ServiceRocket
  • Sep 30 2020
  • Likely to implement
Hosting platform Cloud
  • Nov 30, 2021

    Admin response

    Hi everyone, thanks for all your comments and votes regarding this idea.

    We are currently researching about implementing this idea and we are thinking of doing so by adding another role in secrets, Editor role, on top of the currently available Viewers & Owners role. This is currently tracked at this separate idea, Advanced permission scheme for each Secrets Macro, where I have attached a mockup and a detailed explanation on how it will work. Please check it out and do let us know what you think of it by commenting.

    Monique, PM

  • Attach files
  • Steven Carlson commented
    18 Mar 03:12am

    I see that this ticket has been planned. Is there anyway I can get an idea of when this feature will be added. Please and Thank you!

  • Admin
    Shared ServiceRocket commented
    14 Dec, 2020 02:33am

    Thanks for the comment, Andrew. Please give us some time to look into this.

  • Andrew Chatfield commented
    10 Dec, 2020 03:06pm

    We used to use Security and Encryption on the Server version of Confluence where anyone with access to decrypt the field could also edit it.

    Any member of our team who has the ability to decrypt the information may need to change it so having this limited to one individual makes the plugin completely unusable at the moment.

  • +10