Module · 05

Administration

Roles in plain sentences, people as roles plus exceptions, and one register of everything your company does.

  • Roles
  • People
  • Activity
  • Mail
  • Backups
Roles · each area in a plain sentence

For administrators

  • Each role described area by area, in plain sentences
  • People as roles plus exceptions
  • Which statuses each role may set, picked by colour
  • Every booking field Shown or Required
  • The Activity register: who, what, when, before and after
  • Password length, expiry and idle sign-out for the whole company
  • Mail through NDMX or your own server
  • Nightly backups, with Look at a copy, Download and Replace everything
Roles · a plain sentence per areaActivity · who changed what, and when

Who uses it

  • AdministratorsSet up roles, people, fields, mail and backups.
  • Heads of departmentDecide what their teams may see and change.
  • IT managersCheck sign-ins, activity and backups.

What it does

01

Roles in plain sentences

A role is a named set of permissions, given to people so no one is set up by hand. A role's Permissions tab has one row per area, with a plain sentence of what the role can and cannot do there; open a row for its switches. Change a role and everyone holding it changes with it.

  • Copy role starts a new role from an existing one
  • Built-in roles cannot be deleted, only adjusted
Roles · each area in a plain sentence
02

People: roles plus exceptions

A person holds one or more roles. Their Access tab lists every permission as allowed or not, and names the role that grants it. One extra permission for one person is an exception on their own page, not a role made for one person.

  • Client access limits a person to named clients' bookings
  • Copy permissions gives a newcomer a colleague's roles in one step
  • The company always keeps at least one administrator
People · a person as roles plus exceptions
03

Which statuses a role may set

Inside a role's Bookings area, the company's statuses stand in their own colours, in two groups: work and billing. Click one to allow it. Clearing a status is a permission of its own.

  • Only the statuses a person may set are offered to them, on the desk and on the phone
Roles · the statuses a role may set, in their own colours
04

Booking screens: Shown or Required

For every field of the New Booking and New Report windows, choose whether it is shown and whether it is required, and see how many existing bookings leave it empty. A hidden field disappears from the window, the card, the list and the search. Required applies to new bookings only.

  • A company that books only for itself can hide every client field, invoice and rate card at once
Booking screens · every field Shown or Required
05

Activity: one register

Who changed what, when, and on which record, grouped by day. Open an entry to see each value before and after. The register covers everything the company does, including every booking's service and finance log. Entries are permanent.

  • Filter by bookings, finance, lists, people, company, layouts or sign-ins
  • A refused sign-in names its reason
Activity · who changed what, and when
06

Mail and Backups

Send the company's mail through NDMX, with nothing to set up, or through your own mail server, with Send a test, which reports the server's exact answer. Backups lists the nightly, manual and safety backups: Look at a copy opens a private, read-only copy of the company as it stood, and Download takes a copy protected by a passphrase only you know.

  • A saved mail password is never shown again
  • Restoring over the company first takes a safety backup, and every administrator is told
Backups · nightly, manual and safety, with Look and Download

See how your roles would look.

A walkthrough of roles, people, the Activity register, mail and backups, set up for your departments.

Request a demo