Skip to content

Why these permissions

These are the existing Forge scopes already granted at install. This page explains why Shell needs each one. We are not adding or changing scopes.

ScopeWhy Shell needs itUsed by (commands)
read:confluence-space.summary / read:space:confluenceList spaces and navigate the site treels, cd, tab completion at /
write:confluence-spaceCreate folders that become pages/structures where space writes applymkdir / space-adjacent writes as already shipped
search:confluenceCQL-backed discoveryfind (-name, -mtime, -label, -prune, …), folder listings, attach find, du
read:page:confluenceRead page metadata and bodiesls, ls -l, cat, tree, less, pipes
read:content-details:confluenceRicher page detail where neededdetailed listing / history-related reads
write:page:confluence / write:confluence-contentCreate/update/move/copy pages, labels, archivetouch, mv, cp / cp -r, chmod, label add / label rm, archive
delete:page:confluenceMove pages to trash / removerm / del (one or many pages; and moves that Confluence models as delete+create where applicable)
read:attachment:confluenceList page attachmentsattach ls, attach find, du
write:attachment:confluence / delete:attachment:confluenceRename / trash attachmentsattach mv -y, attach rm -y

mv and cp take at most 100 sources (cp -r at most 200 pages) and can target another space; a cross-space mv needs -y. This is not a bulk multi-select migrator UI. Cloud 3.9.0 added cross-space mv / cp / cp -r without adding scopes. Cloud 3.8.0 added label, archive, cp -r, attach find, du, multi-target rm, and read-only folder support without adding scopes.

chmod lists or changes explicit page restrictions. Space-level permission admin is out of scope.