DISPLAY
Confidential label
Mark a static table as confidential and save its rows in Atlassian Store. Turning on Confidential automatically changes Store as to Atlassian Store and displays a notice above the table. If your administrator has not enabled Atlassian Store, you cannot activate Confidential: the disabled toggle shows a message asking you to contact your administrator to enable it.
Put the signal where readers need it
Enable the label in Display settings, then pair it with your organization’s permissions and sharing guidance.
- 1
Check the storage policy
A Confluence administrator enables Atlassian Store in Apps → Simple Tables → Settings. Use a static table with no more than 5 MB of serialized data.
- 2
Open Display settings
Edit the macro and open Display in the table setup.
- 3
Open the Context group
Turn on Confidential in the Context group. This selects Atlassian Store and locks the storage choice while enabled. If unavailable, ask your administrator to enable Atlassian Store; the source must be static and fit the 5 MB limit.
- 4
Save the macro
Save or publish the page. Readers see a red confidential-content notice above the table.
- 5
Apply the page’s handling policy
Use the label with the appropriate sharing guidance and permissions for the page, space, and organization.
Tip
If Confidential is disabled, read the explanation beside the toggle. Ask an administrator to enable Atlassian Store in Apps → Simple Tables → Settings. The table must use a static source and fit the 5 MB limit. The option also waits for storage settings and data to finish loading. You can still turn off an existing confidential label.
Example: mark a sensitive planning view
A planning team shares upcoming initiatives, budget ranges, and internal notes with its authorized members.
- Scope access first
- Use Confluence permissions so only the intended members can open the planning page. The confidential label does not replace that access control.
- Mark the table clearly
- Enable Confidential when the table contains sensitive initiatives, budget ranges, or internal notes. The full-width notice appears before the rows and establishes context before anyone starts working.
- Make the handling policy clear
- Pair the notice with your organization’s sharing and handling guidance. Authorized readers understand that the content needs care while the table remains fully usable.
- Result
- Permissions decide who may see the page; the label reminds those people how to handle its contents. The label itself adds no encryption layer and does not hide or redact data.
A handling signal, not access control
Confidential combines a visible handling label with Atlassian Store for the source rows. The label adds no separate access restriction or encryption layer. Confluence permissions still control the audience, and enabled table downloads remain available. Changing storage does not erase earlier page content, attachments, history or exported copies.