Checklist.coffeeSuite.coffee
Set-up and organisation

Organise locations and the Checklist team

Classify where controls happen and assign service roles without duplicating Suite identities.

1 min readUpdated Aug 23, 2026

Create stable operational locations and give shared Suite identities only the Checklist access they need.

Before you start

  • List the sites or areas that must be compared.
  • Confirm which existing Suite users participate.
Checklist location management with code, activity, status and service team access.
Stable locations and scoped roles keep operational history comparable without duplicating identities.

Use stable locations

Create a location for each site or operational area that must remain comparable in queues and reports. Inactive locations remain in historical checklists.

Respect plan capacity

The plan counts active locations. A reduction suspends excess locations reversibly and preserves their templates, schedules and history.

Reuse shared identities

Add existing Suite accounts and choose a Checklist role. Owners and members configure; operational users perform assigned work; clients keep read-only access. Adding a person here does not grant access to other services.

Step by step

  1. Open Locations.
  2. Create each site with a stable name and code.
  3. Deactivate obsolete locations instead of repurposing them.
  4. Open Team and add an existing Suite account.
  5. Assign the least privileged Checklist role.

Final check

  • Active locations fit plan capacity.
  • Names do not duplicate the same area.
  • Adding a member did not grant another service.
Tip: Keep inactive locations for historical accuracy; existing checklists still reference them.