Your team

01Two roles, and yours

Your clinic has two roles: practitioner and assistant. Yours, the owner, is not a third role. You are a practitioner who reaches everything, without writing yourself a single exception.

A practitioner works on their own files and their own appointments: a colleague's do not open for them. They read the catalogue, the hours and the settings without being able to change them. An assistant works on the files and appointments of the practitioners you link them to: they book, move and cancel for them, but they export no file, delete nothing, and do not open the settings at all.

• Owner: everything, across the whole clinic.
• Practitioner: their files, their appointments, their hours. The catalogue and the settings read only, a colleague's files never.
• Assistant: the files of their practitioners, and nothing beyond.
• Deleting a clinical note belongs by default to neither the practitioner nor the assistant.

02An assistant with no practitioner opens no file

You link each assistant to the practitioners they work for. That link is not a display filter: it goes into the question put to the database. With no practitioner linked, the answer is zero rows.

The product says so in those words. The member permissions page writes: with no practitioner linked, this member reaches no file. And if that person opens the console, they read that sentence instead of an empty screen that would look like a breakdown.

• The agenda follows the same boundary and names it: the whole team for you, their linked practitioners for an assistant, themselves alone for a practitioner.
• Nobody widens their own link, not even the member who manages the team.
• The link is ticked and unticked practitioner by practitioner, whenever you want.

03One published exception, one member, one permission

The role sets the rule. An exception corrects it for one person, on one permission, in either direction.

The list of possible exceptions is closed: 24 permissions, the ones the console actually checks. A switch that commanded nothing would be worse than no switch, so it does not exist.

Three refusals are worth knowing, because they are the part that protects. An exception that only repeats the rule is refused. Granting the write without the read is refused. And nobody writes an exception on themselves, or on the owner.

• The role's own table sits beside it: allowed, not allowed, exception.
• Every exception published or withdrawn is recorded with its author and its date.
• A batch of exceptions goes through whole or not at all. Nothing commits halfway.

04Your hours, at two levels

The clinic's published hours are one thing. Each practitioner's week is another. They are two separate records, and that is deliberate.

The hours shown on your page and on your directory card are the clinic's, never the sum of the team's calendars. Bookable times, on the other hand, are read from the week of the practitioner concerned. So you can be away without closing the clinic, and close the clinic without erasing anyone's week.

The two levels hold together by one rule: a practitioner's week stays inside the published one. Narrow the clinic's week and the calendars that stuck out are brought back inside it, and the screen names the practitioner and the days. The practitioner concerned receives the notice, with the days that were brought back inside.

• An absence is entered for the whole clinic, or for one practitioner.
• Appointments falling inside a closure open for you to decide, and whoever has a noresia account is told. Someone registered at the desk has none: you make that call.
• The new hours are written only after the preview, and closing the screen without finishing does not save them. Each appointment you decide, though, executes the moment you decide it: rescheduled or cancelled, done, and it stays done.
• A booking that slips in during your preview is not lost: the save catches it and hands it to you to decide at once.
• A practitioner with no saved week is not bookable online, and the team list says so.

05Who performs which service

Each service carries its duration, which sets the length of the slot, and its price. You decide service by service whether that price shows publicly.

Then you say who does what. With no rows at all, a practitioner performs everything within their specialties: a clinic that does not want this detail has nothing to do. As soon as there are rows, they become the permitted list, and online booking stops offering that practitioner anywhere else.

• Services, add-ons and specialties are set practitioner by practitioner.
• The check runs twice: what the page offers, and what the booking accepts.
• A practitioner cannot be booked on a service whose specialty they do not carry.
• A price kept private shows on no public surface: no dash, no mention, and the amount itself never travels to the page.

06When the team changes

Your plan's seats are counted per role, practitioners on one side and assistants on the other, and a pending invitation already holds its own. So you see the real figure before you invite, not on the day someone accepts. Your own practitioner seat counts in that total.

A departure does not cost you your records. Deactivating removes access at once and takes the person out of online booking, and their future appointments open for you to decide, with their number. Nothing else comes undone: links and exceptions stay written, and reactivating restores access as it was, if a seat is free to take back.

Deleting looks at the record before it acts. A member who never received anyone is erased, and their email is freed for another clinic. A member with appointments, past or future, stays archived: files and revenue hold onto them, they can no longer sign in anywhere, and their email stays held.

• An invitation is good for seventy-two hours, and is resent or cancelled: the link already sent then stops working, and an expired invitation gives its seat back on its own.
• An email belongs to one team: the clinic holding it has to release it.
• A downgrade is refused while your seats exceed the new limit: deactivate a member or cancel an invitation first. At the deadline, nobody is deactivated for you.
• The owner account cannot be deactivated, deleted or transferred from the console.
• Deactivating a practitioner does not detach their assistants: the assistants keep access to that practitioner's files until you untick the link.