Models are page attachments
Revelation stores model content, views and presentation settings in a JSON attachment on the Confluence page. Confluence attachment version history applies. Catalogue synchronisation also uses page content and a page property to track its state.
Readers and editors
Loading a model checks page-view access. Saving and updating page tables require page-edit access. The inline Edit button is hidden when edit access is unavailable, and backend checks also enforce access. Ask the page owner for the access you need before editing or using Rovo to update the model.
Why the app requests access
The app reads and writes attachments for models. It reads page content and updates page content for catalogue tables. It uses Rovo action access for the agents. Check your installation's permission screen for the declared scopes and any changes.
Rovo processing is a separate choice
The app's model storage is in Confluence. Optional Rovo assistance also uses Atlassian's AI processing, which can involve third-party model providers according to your organisation's configuration. See Atlassian's AI Trust Center for current processing details and controls.
What to include in a model
Labels and custom fields are content you author. Use your organisation's normal rules for recording personal or sensitive information. Include only the model information needed for the task when seeking support.
Collaboration
Coordinate significant edits with other authors. Version checks help detect stale updates, but do not provide an exclusive lock for every save. Keep useful versions and backups for recovery.