Permissions

AutoPage - Permissions

This page describes the permissions required to create and manage AutoPage rules, and how permissions affect rule execution.

---

Jira Permissions

Rule Creation and Management

To create, edit, or delete AutoPage rules, users need the following Jira permissions:

Permission	Required For
Browse Projects	Accessing the project and viewing issues that the rule applies to.
Edit Issues	Modifying issue properties (AutoPage stores link metadata on issues).
Administer Jira	Creating and managing global rules (rules that apply to all projects).

Note

Project-scoped rules can be created by project administrators. Global rules require Jira administrator permissions.

Rule Execution

When a rule is triggered, AutoPage checks whether the rule creator (not the user who triggered the event) has the required permissions. If the rule creator’s permissions have been revoked since the rule was created, the execution will fail and an error will be logged in the audit log.

---

Confluence Permissions

The AutoPage Confluence Helper App requires the following permissions to create and manage pages:

Permission	Required For
Create Pages	Creating new Confluence pages from templates.
Write Content	Updating existing pages when rules are re-triggered.
Read Content	Accessing template pages and existing linked pages.

Caution

If the rule specifies “Copy Permissions” in the action settings, the page-level permissions from the template page will be applied to the new page. Make sure the template page has the desired permission settings.

Template Page Access

Before executing a rule, AutoPage checks whether the rule creator has read access to the template page configured in the rule’s action. This check is performed at execution time — not at rule creation time.

If the template page has Confluence page restrictions applied (e.g. restricted to specific users or groups), the rule creator must be explicitly included. Otherwise, rule execution will fail with the following error in the audit log:

Rule owner <name> has no permissions for template page.

Caution

Page restrictions on the template page are a common cause of rule execution failures. If a template page is moved, restricted, or its permissions are changed after the rule was created, all rules referencing that template page will stop working for affected rule creators.

---

App Permissions

The AutoPage apps (Jira App and Confluence Helper App) request the following OAuth scopes during installation:

Jira App

• Read and write access to Jira issues and projects
• Access to Jira webhooks and event triggers
• Storage access for rule configuration and link metadata

Confluence Helper App

• Read and write access to Confluence pages and spaces
• Access to page properties and labels
• Storage access for connection configuration

---

Troubleshooting

If a rule execution fails with a permission error:

1. Check the Audit Log for the specific error message.
2. Verify that the rule creator still has the required Jira and Confluence permissions.
3. If necessary, recreate the rule with a user who has sufficient permissions.

Rule owner has no permissions for template page

Error message: Rule owner <name> has no permissions for template page.

This error means the rule creator does not have read access to the template page configured in the rule. Common causes:

• The template page has Confluence page restrictions that exclude the rule creator.
• The template page was moved to a space the rule creator cannot access.
• The rule creator’s Confluence account was deactivated or removed from a group that had access.

Resolution:

1. Open the template page in Confluence.
2. Check Page Restrictions (··· menu → Restrictions).
3. Either remove the restriction or explicitly add the rule creator (or their group).
4. Re-trigger the rule — no rule recreation is necessary once access is restored.