Space Permissions

The space permissions commands list access permissions configured for a Confluence space. Each permission entry describes which principal (user, group, or role) is granted a specific operation (read, create, delete, or administer).

These commands are especially useful when a bulk export or migration has to be understood in the context of ownership, access, and governance.

Permissions by key


acs2md space permissions by-key SPACE_KEY [flags]

Examples


# List all permissions for a space
acs2md space permissions by-key DOCS
 
# JSON output
acs2md space permissions by-key DOCS --format json
 
# Resolve account IDs to display names
acs2md space permissions by-key DOCS --resolve-users
 
# Save to file
acs2md space permissions by-key DOCS --format yaml --output perms.yaml
 
# Limit results
acs2md space permissions by-key DOCS --limit 50

Aliases

by-key can also be invoked as key or k.

Flags

Flag	Short	Default	Description
`--format`	`-f`	`table`	Output format: `table`, `json`, `yaml`
`--output`	`-o`	(stdout)	Output file path
`--limit`	`-l`	`25`	Number of results per page
`--cursor`	`-c`	(none)	Pagination cursor for the next page of results
`--resolve-users`		`false`	Resolve account IDs to display names (makes additional API calls)

When --resolve-users is active, a progress bar appears on stderr while resolving user names. The table output includes both a “Principal” column (display name) and a “Principal ID” column.

Permissions by ID


acs2md space permissions by-id SPACE_ID [flags]

Lists permissions for a space using its numeric ID instead of its key. Same flags as by-key.


acs2md space permissions by-id 65539 --resolve-users --format json

Command aliases

The permissions command can also be invoked as perms or perm.


# These are equivalent
acs2md space permissions by-key DOCS
acs2md space perms by-key DOCS
acs2md space perm by-key DOCS

Permission model

Each permission entry includes:

Field	Description
Principal	The user, group, or role the permission is granted to
Principal type	`user`, `group`, or `role`
Operation	The permitted action: `read`, `create`, `delete`, or `administer`

Use cases

Compliance and audit — generate a report of who has access to sensitive spaces.
Governance — verify that space permissions follow your organization’s access policies.
Migration planning — capture permission structures before migrating content to another platform.


# Export permissions for all spaces in a script
for key in $(acs2md space list --format json | jq -r '.[].key'); do
  acs2md space perms by-key "$key" \
    --resolve-users \
    --format json \
    --output "permissions/${key}.json"
done