Submission Access: Controlling Who Can View Completed Reports

Ayesha
Ayesha
This article explains how to manage submission access settings in Xenia. You will learn how to control who can view checklist submissions and reports across different organizational levels.

1. Submission Access Control

1. What Submission Access Controls

Submission Access is a completely separate setting from Template Access. While Template Access controls who can complete a checklist, Submission Access controls who can view the completed data afterward — the submission records, responses, and photos.

These are two different questions:

  • "Who can fill out this form?" → Template Access / Can Submit
  • "Who can see the historical data from this form?" → Submission Access

A cashier might submit a temperature log every shift, but you don't want them browsing 30 days of historical data. A store manager needs to see everything from their store. An HR director needs everything from every location. Submission Access is where you set all of this.

Found in: Operations → Templates → [Template Name] → Settings → Access → Submission Access section 

2. The Three Visibility Tiers

Each role gets its own tier — you can have different tiers for different roles on the same template.

Tier 1 — View Own Submissions Only The user sees only what they personally submitted. Nothing from anyone else, even at the same location. Use for: Frontline employees, basic store-level users who don't need visibility into other people's submissions.

Tier 2 — View Own + Submissions at Their Locations The user sees their own submissions plus all submissions where the location tagged on the submission matches one of their member locations. Use for: Store managers who need to see everything from their store. District managers who need everything from their district's locations. The scope is automatically determined by the user's location membership — add a store to their membership and they automatically see that store's submissions. Critical requirement: The template must include a "Select Location" step for this tier to work. Without it, submissions aren't tagged to a specific location and the filtering has nothing to match against.

Tier 3 — View All Submissions The user sees every submission for this template across the entire workspace, regardless of location. Use for: HR Managers reviewing records across all locations, QA/Compliance roles, Admin/Owner accounts.  

3. Tier 1 — View Own Submissions Only

Tier 1 — View Own Submissions Only The user sees only what they personally submitted. Nothing from anyone else, even at the same location. Use for: Frontline employees, basic store-level users who don't need visibility into other people's submissions.

Explain Tier 1 Visibility

4. Tier 2 — View Own + Submissions at Their Locations

Tier 2 — View Own + Submissions at Their Locations The user sees their own submissions plus all submissions where the location tagged on the submission matches one of their member locations. Use for: Store managers who need to see everything from their store. District managers who need everything from their district's locations. The scope is automatically determined by the user's location membership — add a store to their membership and they automatically see that store's submissions. Critical requirement: The template must include a "Select Location" step for this tier to work. Without it, submissions aren't tagged to a specific location and the filtering has nothing to match against.

Explain Tier 2 Location Access

5. Tier 3 — View All Submissions

Tier 3 — View All Submissions The user sees every submission for this template across the entire workspace, regardless of location. Use for: HR Managers reviewing records across all locations, QA/Compliance roles, Admin/Owner accounts.

Explain Tier 3 Organization Access

6. Important: The Location Step Requirement for Tier 2

Tier 2 filters submissions based on their tagged location — the location the employee selected when they submitted the form. Without a Location step in the template, submissions have no location tag and the filter has nothing to work with. The manager would effectively only see their own submissions (behaving like Tier 1), even with Tier 2 configured.

If Tier 2 isn't working as expected, this is almost always the reason. Check the template for a Location step.

Check Template Location Step

7. Practical Configuration by Template Type

Practical Configuration by Template Type

TemplateFrontlineStore ManagerDistrict ManagerHR / Admin
Daily Opening ChecklistTier 1Tier 2Tier 2Tier 3
Temperature LogTier 1Tier 2Tier 2Tier 3
Performance Notice— (not in Can Submit)Tier 1Tier 2Tier 3
Incident ReportTier 1Tier 2Tier 2Tier 3
Food Safety Audit— (not in Can Submit)Tier 2Tier 3
This article explained how to configure submission access tiers and template permissions in Xenia to control who can view checklist submissions at various organizational levels. For more information, see related articles on template management and user roles.


Need Help?
Reach out to our support team at Support@xenia.team 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.