Custom Permissions
By default, any Jira user who has access to an issue can interact with checklists (also known as tasklists) using the Tick app. This default behavior is designed to simplify the user experience upon installation.
However, for teams that require more granular access control, Tick supports Custom View Permissions and Custom Manage Permissions for both checklists and templates. These options offer greater flexibility over who can view or manage checklist-related content.
Tick Permission Options
We offer two ways to apply permissions, giving you flexibility and control:
-
Basic (View):
- Specifies who can see a feature—whether it’s a checklist or a template—based on Jira roles.
- If a user can view it, they can perform all actions on it; if they cannot see it, they cannot perform any actions.
- Simple and quick to set up, ideal for teams that need minimal configuration.
-
Advanced (Manage):
- Provides enterprise-grade, detailed control, allowing you to define specific permissions for each user and feature.
- By default, users do not have any access until explicit permissions are granted.
- If both Basic (View) and Advanced (Manage) permissions are configured, only Advanced (Manage) permissions will be applied.
Permissions can be applied to two modules Checklist and Template, see the table below for a detailed breakdown of permissions for each module.
The tables below summarize the custom permissions available and their specific functions.
Checklist Permissions (Task and Tasklist)
| Add Tasks (Tick) | Edit Tasks (Tick) | Remove Tasks (Tick) | Toggle Tasks (Tick) | View Tasks (Tick) | |
|---|---|---|---|---|---|
| Create task | ✓ | ✗ | ✗ | ✗ | ✗ |
| Create tasklist (checklist) | ✓ | ✗ | ✗ | ✗ | ✗ |
| Edit task title | ✗ | ✓ | ✗ | ✗ | ✗ |
| Edit tasklist (checklist) title | ✗ | ✓ | ✗ | ✗ | ✗ |
| Assign task | ✗ | ✓ | ✗ | ✗ | ✗ |
| Edit due date | ✗ | ✓ | ✗ | ✗ | ✗ |
| Make task optional | ✗ | ✓ | ✗ | ✗ | ✗ |
| Change order | ✗ | ✓ | ✗ | ✗ | ✗ |
| Remove task | ✗ | ✗ | ✓ | ✗ | ✗ |
| Remove tasklist (checklist) | ✗ | ✗ | ✓ | ✗ | ✗ |
| Check or uncheck task | ✗ | ✗ | ✗ | ✓ | ✗ |
| Change status of task | ✗ | ✗ | ✗ | ✓ | ✗ |
| Convert to subtask | ✗ | ✗ | ✗ | ✓ | ✗ |
| View task on issue page | ✗ | ✗ | ✗ | ✗ | ✓ |
| View tasklists (checklists) on issue page | ✗ | ✗ | ✗ | ✗ | ✓ |
Template Permissions
| Manage Templates (Tick) | View Templates (Tick) | |
|---|---|---|
| Create templates | ✓ | ✗ |
| Edit templates | ✓ | ✗ |
| Remove templates | ✓ | ✗ |
| View templates | ✗ | ✓ |
| Apply templates | ✗ | ✓ |
Enabling Custom Permissions
By default, custom permissions are disabled, so anyone who can see an issue can also use Tick features. To enable more advanced control, follow the steps below.
Open Tick Permissions
Go to Jira → Manage Apps, and in the sidebar, click Permissions under the Tick app section.
Enable View Permissions
By default, View Permissions and Manage Permissions are disabled to simplify onboarding. To control who can view checklists and tasks, enable the View Permissions and Manage Permissions checkboxes.
Now, the way you decide who gets to just look, and who gets to work with the checklists and templates in Tick – that's through what we call View Permissions and Manage Permissions. These work their own way, depending on whether your project is Team Managed or Company Managed.
For clarity, we have divided the explanation of view and manage permissions onto separate pages to provide more detailed information and visual examples. Please follow the link below that corresponds to your project type to continue with the setup.