Template Access: Controlling Who Can Submit or Edit
Last updated: October 19, 2026
This article explains how to manage access controls for checklists in Xenia. You will learn how to configure template-level permissions to control who can view and edit specific checklists.
Understand Template Access
1. What Template Access Controls
Every template in Xenia has its own access settings, independent of workspace role permissions. While role permissions determine whether a user can access the Templates module at all, template-level access controls determine whether they can see and interact with this specific checklist.
Template Access is found inside each template: Operations → Templates → [Template Name] → Settings → Access → Template Access section
There are two controls:
Can Edit: Who can open this template in the builder and make structural changes — add, edit, or delete steps, change settings, configure automations
Can Submit: Who can see this template on their device and complete a submission
These are configured per role or per specific user, and apply only to this checklist.
Navigate to Template
How to Configure Template Access
Go to Operations → Templates
Click into the template → click Settings tab
Navigate to the Access section
Under Template Access:
Can Edit → add or remove roles/users who can edit the template structure (typically Admin only)
Can Submit → add or remove roles who can see and complete this template
Save changes — changes take effect immediately

Select the "Edit" option.

Click the Settings button to access template configuration options.

Next, select "Access".

Select Can Edit Template Permission
Can Edit — Who Can Modify the Checklist
The "Can Edit" list determines which roles or specific users can open the template builder and make structural changes.
This is the template's own editing gate, separate from the "Manage Templates" role permission. Both must be true for a user to edit a template:
The role must have "Manage Templates" permission ON at the role level
The user or their role must be listed in this template's "Can Edit" section
Standard configuration: Restrict Can Edit to Admin only, or to a designated template owner. You do not want every manager who has Manage Templates permission being able to edit every checklist in the workspace.
The admin bypass: Admin and Owner roles with the "Access All — Unrestricted Access" permission can edit any template regardless of the Can Edit list. This is the safety net — if a template gets locked down, an admin can always get in and fix it.


Role Permission Requirement
This is the template's own editing gate, separate from the "Manage Templates" role permission. Both must be true for a user to edit a template:
The role must have "Manage Templates" permission ON at the role level
The user or their role must be listed in this template's "Can Edit" section

Select Can Only Submit Permission
Can Submit — Who Sees the Template
The "Can Submit" list determines which roles or specific users can see and complete this checklist.
Default behavior: By default, most templates are open to all users. This is fine for general-purpose checklists that everyone should use — a daily opening checklist, a cleaning log, a temperature log.
When to restrict: For sensitive or specialized templates, restrict Can Submit to specific roles:
Performance Notice forms → HR Manager and Admin only
Manager walkthrough audits → Managers and above, not frontline
Food safety audits → Auditors, QA Managers
Disciplinary records → HR only
The critical rule: If a user's role is not in the Can Submit list, they cannot see this template at all — it won't appear in their template list on any device. It is invisible to them, not just locked.
The visibility rule: Whoever can Submit AND whoever can Edit can see the template. Both groups have visibility. Only those in Can Submit can complete it. Only those in Can Edit can change the checklist structure.

Common Configuration Scenarios
Template Type | Can Submit | Can Edit |
Daily Opening Checklist | All store roles | Admin only |
Manager Walkthrough | Store Manager, District Manager | Admin only |
Performance Notice | HR Manager, Admin | Admin only |
Vendor Issue Report | All roles | Admin only |
Food Safety Audit | Auditor, QA Manager | Admin only |
Temperature Log | Cook, Kitchen Manager, Store Manager | Admin only |
This article explains how to configure template-level access controls in Xenia to manage checklist visibility and editing permissions. By using these settings, you can protect sensitive forms and ensure users only see checklists relevant to their roles. For more information, see related articles on role permissions and checklist management.
Need Help?
Reach out to our support team at Support@xenia.team