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.
| Scope | Why Shell needs it | Used by (commands) |
|---|---|---|
read:confluence-space.summary / read:space:confluence | List spaces and navigate the site tree | ls, cd, tab completion at / |
write:confluence-space | Create folders that become pages/structures where space writes apply | mkdir / space-adjacent writes as already shipped |
search:confluence | CQL-backed discovery | find (-name, -mtime, -label, -prune, …), folder listings, attach find, du |
read:page:confluence | Read page metadata and bodies | ls, ls -l, cat, tree, less, pipes |
read:content-details:confluence | Richer page detail where needed | detailed listing / history-related reads |
write:page:confluence / write:confluence-content | Create/update/move/copy pages, labels, archive | touch, mv, cp / cp -r, chmod, label add / label rm, archive |
delete:page:confluence | Move pages to trash / remove | rm / del (one or many pages; and moves that Confluence models as delete+create where applicable) |
read:attachment:confluence | List page attachments | attach ls, attach find, du |
write:attachment:confluence / delete:attachment:confluence | Rename / trash attachments | attach 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.