Confluence permissions the app asks for

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

Read-only: content, page and blog post, content summaries and permissions, space summaries, user and group, content properties, search, and app storage. No write, delete, email or impersonation permission. Permissions are app-managed, so a new permission comes with pending admin approval rather than blocking installs.

#Where you do it

Task

Where

Insert the macro

Confluence editor → /Smartsheet

Choose how readers see the sheet, then Apply

Macro settings → How readers see the sheet → Interactive table / Read-only sheet / Editable sheet → Apply

Approve the app's pending Confluence permissions

Atlassian Admin Hub

#Settings that affect this

Setting

Where

What it does

Global settings → Smartsheet

Confluence settings → Apps → Smartsheet

There are no Smartsheet-specific admin settings. The page shows only the Introduction / getting-started section and help links. Every other section is switched off for this app: Capabilities (suite only), Features (nothi

Get started page ("👋")

Confluence settings → Apps

A second global-settings entry that opens the get-started page.

Smartsheet space page

A space's page list → "Smartsheet" ("Browse and embed your Smartsheet views")

Three tabs. Introduction carries the help links. Space sheets scans Confluence pages for Smartsheet macros and needs no Smartsheet connection; each card carries a "used on N pages" badge and a right-click menu to copy th

#Worth knowing

  • "Read-only sheet" and "Editable sheet" make the sheet reachable by anyone with the link, outside Confluence. The app always publishes to everyone rather than inheriting your organisation's default, and there is no option to publish organisation-only from inside the macro (an existing organisation-scoped link is shown as such and reused unchanged).

  • Seeing or changing sharing needs Confluence edit permission on the page, not just view, because the panel shows live publish links.

  • The legacy token import depends on reading a reserved Confluence app property. If that read fails it falls back to a server-side site map that must be populated, otherwise previously connected users appear disconnected after the upgrade.

Better with company.