Skip to end of banner
Go to start of banner

Managing access to Secrets

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Soon, an improved version with enhanced security of Security & Encryption for Confluence Cloud will be released. Please check out next steps for administrators at this page.

Overview

This page covers who can create, view, update, and delete secrets.

You need to ensure that users or groups have been granted Add/Delete Restrictions to allow for continued creation and editing of secrets

  • space admins are users that have been granted Add/Delete Restrictions permission in a space

  • non-space admins are users who have not been granted Add/Delete Restrictions permission in a space.

Creating a secret

To create a Secret macro, you must have the following requirements:

  • You have access to the space where you want to add the Secret macro.

  • You have Edit permission for the page where you want to add the Secret macro.

  • You have Add/Delete Restrictions permission in that space.

Updating a secret

To edit a Secret macro, you must be the owner of the secret, either as an individual “User Owner” or a member of a “Group Owner”. 

When a user edits a secret, the user will be made User Owner automatically, as long as the user is part of the group. By default, the secret creator is also the owner. 

The secret owner can add other users as owners. For details refer to creating and editing secrets documentation.  

Granting access to Confluence users to create secrets

For individual users

  • in Space permissions, in the Individual Users section

  • grant the user Add/Delete permission under Restrictions

Granting the permission allows the user to add/delete restrictions to other pages in that space.


For groups

  • in Space permissions, in the Groups section

  • grant a group Add/Delete permission under Restrictions

Granting the permission allows the members of the group to add/delete restrictions to other pages in that space.

App user permissions will retain legacy secret behaviour. Newly created secrets that utilize zero-knowledge architecture depend on individual user or group permissions.

FAQs and common scenarios

 I am the owner of a Secret and I want to transfer ownership to another user (e.g. I am leaving the company or I am being transferred to another team)

Currently, you cannot remove yourself as a secret owner. Instead, add another user as an owner, and request that user to remove your ownership.

We have introduced group-related access to assist with ownership transfers - see How to ensure that secrets-related access is not impacted by a change of owners? for more details.

  • No labels