This page explains how permissions control access to features in the Templify app. Templify introduces two dedicated global permissions to clearly separate using templates from managing templates.
🛡️ Global Permissions Introduced by Templify
Templify defines two global permissions in Jira:
🔹 Issue Templates – Use Templates
This permission allows users to use existing Issue Templates, but not modify them.
What users with this permission can do:
Create issues from templates
Apply templates to existing issues
Use the Issue Template field on Create Issue screens
Trigger automation actions:
Create issue from template
Apply issue template
Benefit from UI Modifications (auto-filled fields, default values)
What users cannot do:
Create new templates
Edit or delete templates
Change template configuration or availability
Default grant: All users
🔹 Issue Templates – Manage Templates
This permission allows full administration of Issue Templates.
Use all features covered by Use Templates (this permission includes it)
Default grant: All users
🔐 Feature Access Requirements
Understand which permissions are required to access each part of the Templify app and ensure proper visibility for your users.
Module
Required permissions
Issue Panel (in issue view)
Create Issues in the current project
Manage Issue Templates (global permission)
Issue Action → Apply Template
Edit Issues in the current project
Use Issue Templates (global permission)
Create Issue → Default Values
Use Issue Templates (global permission)
Templify Admin Pages
Jira protected page
Templify Global Page
Manage 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.