Skip to content
Apolaris AI Docs

Privilege templates

pro

Save a set of privileges under a name and apply it to a user in one click — the default roles every organization starts with, and how to build your own.

A privilege template is a saved set of the permission tick-boxes from the user form, kept under a name such as Receptionist or Employee (basic). When you create or edit a user you pick a template, every privilege it contains is ticked for you, and you adjust for that person before saving. A template is a starting point, not a link: editing or deleting it later never changes the users it was applied to.

Templates make the tenth receptionist as quick to set up as the first, and keep people who share a job from drifting apart — without giving up the per-privilege model described in Users & privileges.

You reach them from Organization → Privilege templates in the sidebar, or from the Privilege templates button on the Users page.

Who can do this

The same people who manage users: a manager (is_manager) or a privilege admin (can_manage_privileges). The escalation guard applies to templates exactly as it does to users: a privilege admin cannot put a protected role flag (Manager — full access, Manage users & privileges, Send customer messages without confirming) into a template, and saving a template that already holds one leaves that flag untouched rather than removing it.

The default templates

Every organization starts with these templates, named in its default language. They are ordinary templates: rename them, edit them, delete the ones you never use.

Template Meant for What it grants
Employee (basic) Any staff member who only looks after themselves POS only: their own appointments, their own earnings, clocking in and time-off requests. Cannot charge or book.
Technician Staff who serve clients and charge at the till Employee (basic) plus booking and charging their own appointments, looking up and adding clients, submitting expenses, the AI assistant.
Receptionist The front desk Technician plus the whole-branch diary, editing clients, deleting bookings, the service list, the shared inbox and the time-off calendar.
Branch manager Runs one location without organization-wide admin Receptionist (with CRM access) plus staff records, attendance and schedules, approving time off, reports, analytics, expenses, stock, loyalty, cameras and approving what the AI proposes.
Office administrator The back office User accounts, staff records, schedules, attendance, time off, payroll and HR documents, expenses and reports — without being a manager.
Finance Bookkeeping Read-only on sales and payroll; manages expenses, billing and e-invoicing; exports reports and analytics.
Contact center agent Answers the shared inbox The inbox, clients, bookings and the whole-branch diary, the AI assistant.
Telephony admin Phone numbers and call flows The inbox, calls and recordings, voice settings, conversation flows, the knowledge base, reports.
Marketing Growth Customer journeys, broadcasts, the knowledge base, the public website, competitor intel, online-booking settings, reports and analytics.
Analyst Read-only numbers Reports and their export, analytics, the Data Explorer and billing; read-only on clients, sales and bookings.
Clinical practitioner A technician in a clinic Technician plus consents and the clinical history (read and write). Health data — grant deliberately.
Camera operator Watches the cameras Cameras and detection settings, branches and staff (read-only). No client or money access.

A template can include privileges that belong to a module that is off for your organization. They still apply — the picker shows those groups greyed with a Module off badge rather than hiding them, so a grant is never silently dropped.

Apply a template to a user

  1. Open Users and click Add User, or edit an existing user.
  2. In step 2 · Permissions, under Start from a template, click the template. Its privileges are ticked and everything else is cleared, so what you see is exactly that role; related privileges are ticked for you.
  3. Adjust for this person if needed — tick or untick anything.
  4. Set Branch access in step 3 and save. Branch access is per person and is never part of a template.

The card of the template that matches the current selection exactly is highlighted; change one tick-box and the highlight goes away, so the form always tells you whether a user still is that role. The Users page shows the same thing as a pill on each row.

Create your own template

  1. Open Privilege templates and click New template.
  2. Give it a name (unique within your organization), an icon and a one-line description — this is what a manager sees when picking it.
  3. In step 2, tick the privileges. You can start from another template, or from a default the organization no longer has.
  4. Click Save template. It appears on the user form immediately.

To derive a house role from a default, use Duplicate on the templates page: the copy opens for editing and the original stays as it was.

Edit, delete, restore

  • Editing a template changes only the template. Users who were set up from it keep exactly the privileges they have; re-apply the template to them if the change should reach them.
  • Deleting a template removes the shortcut, nothing else.
  • Restore default templates re-creates the defaults you deleted. A renamed or edited default still counts as present, so it is never duplicated. The button only appears while at least one default is missing.

Keep the list short and the names job-shaped — Front desk, Night shift, Clinic nurse. A template that needs a paragraph to explain is two templates.

See also: Users & privileges, Roles at a glance and the Privileges reference.