Skip to content

Organisations and Locations

Jonot uses a two-level hierarchy: organisations at the top and locations beneath them. Understanding this structure is essential for configuring your account correctly.

An organisation (org) is the top-level entity in Jonot. It represents your business as a whole — for example, "Acme Healthcare" or "City Council Services". Every location, queue, device, staff member, and billing record belongs to an organisation.

Key facts about organisations:

  • Created during the signup wizard at https://join.jonot.io.
  • Identified by a slug (e.g. acme-healthcare) that appears in every customer-facing URL. Slugs must be 3–40 characters, lowercase letters, numbers, and hyphens only.
  • An org can have one or many locations — locations are uncapped on every plan; see Billing and Plans for per-location pricing.
  • Billing is managed at the org level.

A location is a physical venue or branch within an organisation — for example, "Main Street Branch" or "Airport Terminal 2". Each location operates independently with its own:

  • Queues (one or more named waiting lists)
  • Devices (kiosks, displays, and desks paired to the location)
  • Staff team (location-managers assigned to this location)
  • Receipt branding (header and footer text printed on kiosk tickets)

Locations are identified by a slug scoped within the org. The full customer join URL is:

https://customer.jonot.io/{org-slug}/{location-slug}/{queue-slug}/

An org can have as many locations as it needs — see Billing and Plans for how additional locations are priced. Org-managers see and can manage all locations. Location-managers are scoped to one or more specific locations — they cannot see other locations or access org-level settings.

  • Full administrative access to the entire organisation
  • Can create, edit, and delete locations, queues, and devices
  • Can invite and remove staff at any location
  • Can invite other org-managers (co-admins) to share full administrative access
  • Can access and manage billing
  • Can change org-level settings (name, slug, industry) — including renaming the organisation without needing a Jonot super-admin
  • Access scoped to their assigned location only
  • Can create, edit, and delete queues and devices within that location
  • Cannot invite or remove staff, create locations, access other locations, or manage billing — these are org-manager actions

Roles are assigned when a staff member accepts an invite. See Manage Staff for the invite flow.