Template Permissions¶
Reviewing check template permissions
Check templates belong to the whole organization rather than to a datastore, so working with a template is governed by the user role. The checks a template creates live on datastores, so creating them also needs a team permission on each target datastore. For the full reference of user roles, see User Roles.
User Roles¶
| Action | Member | Manager | Admin |
|---|---|---|---|
| View templates in the Library and open a template's page | |||
| Read a template's Timeline, comment, and reply | |||
| Create a template, from the Library or from a check | |||
| Edit a template, its description, or its tags | |||
| Bulk edit templates | |||
| Add one or several checks from a template | |||
| Archive a template | |||
| Export templates to an enrichment datastore | |||
| Delete another user's comment on a template |
Team Permissions for the Checks¶
Creating a check from a template also needs a team permission on the datastore that will hold the check, the same as creating any check:
| Action | Minimum team permission on the target datastore |
|---|---|
| Add a single check as Draft | Drafter |
| Add a single check as Active | Author |
| Add multiple checks (always created as Draft) | Drafter |
Once created, each check follows the permissions of its own datastore. See the Permissions page of its rule type, linked from Getting Started with Checks.
Key Details¶
- Editing a template with linked checks. An edit that reaches the linked checks, such as new tags, or any change on a locked template, also needs access to every datastore that holds one of them. Without it, the edit stops with
Cannot update this template: it has linked checks in datastores you do not have access to. Admins are not limited by this. - Modules. Creating a template, or a check from one, requires the module for the template's rule type. Existing templates and their checks stay editable. See Feature Availability.
- API. The same rules apply through the API. See the Templates API page.
See Also¶
-
How Templates Work
What a template defines, how checks are created from it, and what Locked and Unlocked change.
-
Filter Permutations
How
each()in a template's filter creates one check per value, and how adding or removing values changes them. -
Template Overview
Every part of a template's Overview: Summary, Description, Definition, and Timeline, plus the page's tabs and actions.
-
Template Checks
Every check created from the template, across datastores, and how to review the drafts it creates.
-
Template Anomalies
The anomalies found by every check created from the template, and how to triage them from the template's page.
-
Template Examples
Scenarios that show when a template pays off, and whether to lock it.
-
Template Best Practices
How to name, lock, and maintain templates so their checks stay trustworthy.