Permissions

Templating.app uses a two-tier permission system for Issue Templates. On top of the standard Jira permissions, administrators can configure global permissions and template owners can set restrictions on individual templates.

Jira Permissions (Required)

Every action on Issue Templates requires standard Jira permissions in the template’s project:

• Browse Project - required to see templates for that project
• Create Issue - required to create, edit, apply, and delete templates

Jira administrators always bypass all permission checks.

Global Permissions

Jira administrators can configure instance-wide permissions in the Templating.app admin settings. These control which users and groups can perform Issue Template operations across the entire Jira instance.

Permission	Description
Browse Templates	Control who can view available issue templates
Create Templates	Control who can create new issue templates
Delete Templates	Control who can delete issue templates
Apply Templates	Control who can use templates to create issues

Permissions can be assigned to individual users and groups.

Tip

When a global permission is not configured, the action is allowed for everyone. Only when you actively assign users or groups to a permission does it become restrictive.

Setting up Global Permissions

1. Go to Jira Administration and open the Templating.app settings.

2. Navigate to the Issue Template Permissions section. You’ll see four permission areas: Browse, Create, Delete, and Apply. Each one shows a status badge (Active/Inactive).

3. For each permission you want to restrict, search and add groups or users using the picker fields. Selected entries appear as tags that can be removed with the X button.

4. For the Delete permission, you can optionally enable “Allow template owners to delete their own templates”. This toggle becomes available once at least one group or user is added to the Delete permission.

5. Click “Update permissions” to save your changes.

Allow Owners to Delete Their Own Templates

When the Delete Templates permission is restricted, you can enable an additional option that allows template owners to delete their own templates, even if they don’t have the general delete permission.

Template-Level Restrictions

Template owners can add restrictions to individual templates. This provides an additional layer of control on top of global permissions.

Restriction	Description
Browse	Restrict who can see this specific template
Edit	Restrict who can modify this specific template
Apply	Restrict who can use this specific template to create issues

Template-level restrictions work together with global permissions. A user must pass both the global permission check and the template-level restriction to perform an action.

Setting up Template-Level Restrictions

1. Open an Issue Template and go to the Restrictions tab.

2. You’ll see three restriction areas: Browse, Edit, and Apply. An info banner explains that restrictions further limit access beyond global permissions.

3. Add groups or users to restrict access for each area. When no users or groups are specified, the restriction is inactive and does not limit access.

4. Click Save to apply the restrictions.

Template Ownership

Each template has an owner, which is automatically set to the user who created the template. The owner is displayed in the template view and is relevant for the “Allow owners to delete their own templates” option.

Permission Overview

Here’s a summary of which permissions apply at which level:

Action	Jira Permission	Global Permission	Template Restriction
View template	Browse Project + Create Issue	Browse Templates	Browse
Create template	Browse Project + Create Issue	Create Templates	-
Edit template	Browse Project + Create Issue	-	Edit
Delete template	Browse Project + Create Issue	Delete Templates	-
Apply template	Browse Project + Create Issue	Apply Templates	Apply

Note

Restricting template application does not prevent users from creating issues manually in Jira. It only controls access to the template itself.