Skip to content
FibonacciAestheticsLog inTry it free

Practice Users and Access Revocation

6 min readUpdated on 20 November 2026

This guide explains how to invite a collaborator, what they can do, and most importantly how to revoke their access when they leave. It is aimed at practice administrators.

The last operation is the one that is always postponed but matters the most: a former collaborator who retains credentials can still access medical records, and no log will flag this as an anomaly because they are formally still authorized.

Prerequisites

  • Account with the admin studio role.
  • For invitations: email configured on the server. Without it, the invitee's account is created but they will not receive the message with the link to set their password, and the request will still appear successful. If an invitee says they haven’t received anything, this is the first thing to check.

Step 1: Inviting a Collaborator

In Settings, the Practice members section lists who has access. The Invite user button asks for first name, last name, email address, and role.

Every invitee receives mandatory two-factor authentication: they will be asked to set it up on their first login. It cannot be disabled, and the reason is that these accounts access health-related data.

The role decides what the person sees, and the drop-down writes it next to each option. The options come in two groups:

  • They see every patient of the practice: Practice administrator, Doctor who sees the whole practice, Doctor of one site (every patient, but in the diary only the appointments of their own site), Head nurse, Nursing staff, Front desk (patients and diary, without opening clinical records) and Cooperative front desk (patients and bookings, without clinical records).
  • They see only their own patients: "Doctor, own patients only" and its variant. The person finds only the patients they follow personally, not those added by the owner or by other colleagues.

As soon as you pick a role, a sentence appears under the drop-down saying what follows. For the "own patients only" roles it is a yellow warning: read it before sending. It is the difference between a colleague who can work straight away and one who cannot find the owner's patients.

Who can change the practice details

Only the owner and whoever has the «Practice administrator» role: name, address, VAT number, clinical rules and public page. Everyone else sees them like this:

  • a doctor sees them read-only, because they are the heading of the documents the doctor signs and must be able to check it. A notice at the top of the page says who can change them;
  • the front desk reads the practice name and contact details, which are needed for the calendar and invoices, but does not see the practice settings.

Whoever gets the «Practice administrator» role can also invite people and change roles. If Change role moves them to another role, they stop administering the practice from their next sign-in.

Step 2: Changing the Role of a Colleague Already Invited

If you chose the wrong role there is no need to remove and re-invite. In the person's row, the Change role button opens a window with the current role and the same drop-down as the invitation, with the same sentences about what follows.

  • It applies from the person's next sign-in. If they are signed in at that moment, they must reload the page or sign in again.
  • It stays in the audit log: who changed the role, for whom, and from which role to which.
  • Only the practice administrator can do it, and the button does not appear for your own account, for the owner, or for service identities.

Step 3: Revoking Access for Someone Who Leaves

In the same table, the Access column contains the Remove access button.

Before confirming, the window explains exactly what happens, and it’s worth reading:

  • Access is revoked immediately, including any active sessions: anyone working at that moment will be logged out on their next action.
  • Clinical data remains. Visits, consents, and signatures continue to be attributed to that physician. This is not a technical detail: a report cannot change authorship because the person who wrote it has changed practices.
  • This action cannot be reversed from the interface: to reinstate someone, they must be invited again.

The operation is recorded in the audit log: who performed it, on whom, and when.

Why There Is No "Temporary Suspension"

This is the question anyone asks when they can’t find the button. The answer is that in this system, the field that might seem useful ("inactive user") does not block access: it is descriptive. A "suspend" button built on that field would mislead the administrator into thinking access was revoked when it wasn’t, which is worse than not having the button at all.

If the absence is temporary and you still want to close access, the solution is to remove access and reinvite upon return.

Step 4: Cases Where the Button Does Not Appear

Instead of the button, you’ll see a dash, and hovering over it reveals the reason:

  • Your own account: No one can revoke their own access. If it were a mistake, no one would be left to fix it from the interface.
  • The last administrator: Removing them would lock the practice out of its own project.
  • Service identities (integrations and automations): These are disabled where they are configured, not from the colleagues screen.

The Change role button follows the same logic: it does not appear for your own account, for the owner, or for service identities.

Common Mistakes

  • Postponing revocation to "when there’s time." This is the only operation in this guide with a time window: the risk exists between departure and revocation.
  • Inviting a colleague as "Doctor, own patients only" and expecting them to see everything. They will see only the patients they follow personally. If they cannot find the owner's patients, the role is the wrong one, and Change role fixes it in a moment.
  • Assuming an invitation was successful without confirmation from the invitee. If email isn’t configured, the request succeeds but the message is never sent.

Frequently Asked Questions

I invited a colleague with the wrong role: do I have to remove and re-invite them? No. In their row, use Change role.

What happens to the records they were responsible for? They remain where they are. What changes is who can access them, not who they are attributed to.

Can I see who revoked whose access? Yes, in the audit log: the operation is tracked as a security event, distinct from a clinical deletion.

Can a revoked collaborator still use an open app? No. The active session stops working on the next action: revocation does not wait for the token to expire.