Permissions
This page explains what permissions are required to access various features in the Templify app. It also covers the custom global permission introduced by the app and how Jira administrators can manag
🛡️ Custom Global Permission: Use Issue Templates
Templify defines a global permission that controls access to app functionality:
Issue Templates - Use Issue Templates
What It Controls
This permission is required to:
View and use templates in the issue view (Issue Panel, Issue Action)
Trigger actions like Apply Template or Create from Template
Use the Issue Template field on the native Create Issue screen
See UI Modifications (e.g. field autofill with defaults)
all other features...
Default Setting
By default, this permission is granted only to
jira-administrators
How to Grant Access
Jira administrators can assign it by:
Going to Jira Settings → System → Global Permissions
Finding “Issue Templates - Use Issue Templates”
Adding user groups (e.g.
jira-software-users)
🔐 Feature Access Requirements
Understand which permissions are required to access each part of the Templify app and ensure proper visibility for your users.
Issue Panel (in issue view)
Create Issues in the current project
Use Issue Templates (global permission)
Issue Action → Apply Template
Create Issues in the current project
Use Issue Templates (global permission)
Create Issue → Default Values
Use Issue Templates (global permission)
Create Issue → Template Field Picker
Create Issues in the current project
Use Issue Templates (global permission)
Templify Admin Pages
Jira protected page
Templify Global Page
Use Issue Templates (global permission)
🔒 Security & Execution Context
All key operations performed by Templify — including issue creation, field updates, and template application — are executed in the context of the user who triggers the action via the Jira UI.
This means:
The app respects Jira’s native permission model
Any operation the user is not authorized to perform in Jira (e.g., editing a restricted field, creating issues in a project without access) will also fail or be blocked when executed through Templify
The app does not escalate privileges — it never acts on behalf of a system user or administrator in background
✅ Examples of enforced restrictions:
If a user cannot create issues in a project, they won’t be able to apply a template to that project
If a field is hidden or restricted by a Field Configuration Scheme or Field Security, it will not be editable via a template
If a user lacks access to edit sub-tasks, templates containing sub-task structures will not be applied successfully
This ensures that all actions remain secure, auditable, and consistent with how Jira permissions are enforced elsewhere in the system.
🔄 Roadmap Insight
We're working on introducing granular permission controls in an upcoming release to give teams more flexibility and security.
This will allow administrators to:
Restrict access to specific features – for example, allow usage of default values but prevent managing templates
Differentiate between roles – such as users who can apply templates versus those who can create or edit them
Scope permissions more precisely across teams and projects
Stay tuned for updates in our changelog as this feature evolves.
Last updated