CONFIGURE COLUMNS
Incognito mode
Keep selected column values available to page editors while readers see a simpler table.
Enabling Incognito automatically selects Atlassian Store and prevents choosing Page Content or Attachment while any Incognito column remains enabled. Confidential uses the same storage requirement.
After saving, Simple Tables checks page edit permission on the server. Readers without that permission receive only the permitted data, and the entire Incognito column is absent. The table waits for data and permission checks before appearing, without a covering layer.
Protect a column in Atlassian Store
Open the Simple Table macro settings and choose the columns that should remain available only to page editors.
- 1
Open Columns
Edit the Simple Table macro and open the Columns tab.
- 2
Expand a column
Open the column settings. The Incognito icon is beside the Header field in Column details.
- 3
Enable Incognito
Select the icon. Store as switches to Atlassian Store. If storage is unavailable, loading, disabled by the administrator or too small for this table, the control explains the reason.
- 4
Save and publish
Submit the settings and save or publish the page. Other storage choices become available after all Incognito columns and Confidential are turned off.
Requirement
An administrator must enable Atlassian Store. This requires a static table within the 5 MB storage limit. Live URL sources, joins and Simple Table with Body macros cannot activate Incognito. You can always turn an existing flag off.
What readers can access
Simple Tables checks page edit permission before sending protected values to a person.
Protected values
Readers do not receive the protected values in table data responses. Fullscreen, filters, grouping, pivot tables, downloads and Ask Rovo use the permitted data.
Dependent columns
Calculated columns that depend on Incognito values are also hidden, including indirect dependencies. Formulas whose dependencies cannot be established safely remain hidden. A second column reading the same field cannot expose it.
Joined tables
Joins cannot recover private source values. A join that requires a protected match column cannot resolve for a reader.
Copied pages
A copied page can display permitted values. Access to the private values requires edit permission on both the copied page and the original page. The first protected save creates an independent stored payload.
Permissions and sharing
Confidential remains a handling label. Incognito applies column access checks using Confluence permissions; neither feature adds an encryption layer. Editors can still copy, download or share information they can access.
An internal deal identifier
A Revenue Operations team shares a pipeline table with a wider audience.
- Before
- Internal deal IDs appear alongside the customer, stage and owner.
- After saving in Atlassian Store
- Deal ID is marked Incognito. Page editors retain that working context; readers receive the customer, stage and owner without the protected identifier or its column.
Existing tables and earlier copies
Existing Incognito tables in Page Content, Attachment or an older Atlassian Store payload keep their visual hiding until they are saved again in Atlassian Store with this version. This is not retroactive protection: earlier page versions, attachments, downloaded files and other copies remain unchanged. An ineligible source must have Incognito turned off before its settings can be saved.