Permissions

Response Templates themselves do not have any particular permissions. Instead, they have visibility scopes that determine where a template can be seen and used.

Of course, you don't just any user to be able to create or delete templates. To address this, the app ships with a default permissions, and further allows you to leverage the Jira permissions scheme.

Default Permissions

By default, Personal templates are protected and only accessible by the user that created it, while Global templates can only be managed by Jira Administrators, and Project Level templates can be managed by Jira Admins and Project admins. For a more succinct overview, take a look at the following table:

You can change the default permissions from the settings screens.

{{image of settings screen with permissions section}}

Alternatively, you can also change the app to utilize built-in Jira permissions schemes. In this case, change the permissions mode on the settings screen.

Once done, you can set permissions on a per-project level using the regular permissions schemes. This allows you to set who can add, edit, delete or even insert templates for any given project.

{{image of jira permissions with our settings}}

Important Note:

Jira doesn't support an addon like ours to provide default values for the Jira permissions. As such, you should set permissions before switching the permissions mode.

If a project doesn't have any values assigned to the permissions, then users simply won't be able to use any project level templates in that project.

Important Note:

Changing the permissions mode really only changes how Project Level templates are handled. Personal templates remain in the hands of individual users, and Global Templates will continue to be managed by Jira Administrators.