Skip to main content

Global and Site-Specific Checklists

Understand how global and site-specific checklists differ in visibility, editing permissions, and usage across locations.

Updated over 2 months ago

WashStacks supports two types of ad hoc checklists: global and site-specific. The main difference is how they are shared across locations and who can edit them.

Site-Specific Checklists

Site-specific checklists are assigned to a single location. Only users with access to that location can view or edit them.

These are ideal when processes vary by store or when each location needs its own version of a checklist.

Today, all checklists are site-specific except for Ad Hoc checklists, which can optionally be made global.

Global Checklists

Global checklists are available to all locations. They are designed for company-wide use when the same checklist should apply everywhere.

To prevent accidental changes that affect multiple sites, be careful about who you assign to manage them.

Ad Hoc checklists are currently the only type of checklist that is global.

Use global checklists when you want one shared version that can be triggered manually across your entire organization. Common examples include:

  • Corporate audits

  • Safety reviews

  • Employee onboarding checklists

Editing Global Checklists

To create, edit, or delete a global checklist, a user's role must:

  • Have view permission for regular checklists

  • Have the additional appropriate Global Checklist permissions assigned

Users who do not have access to all locations can still see and complete global checklists, but they cannot edit them.

Things to Know

  • Global checklists apply to all locations. They cannot be restricted to a subset of sites.

  • Only Ad Hoc checklists can be made global.

  • Roles must have the Run Ad Hoc Checklists permission enabled in order to run an Ad Hoc checklist.

Did this answer your question?