> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mymeddical.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Revoking and restoring access

> Stop a staff member or a parent signing in straight away, and let them back in later.

## Overview

Use **Revoke access** when someone should no longer be able to use your organisation's account: a carer or teacher who has left, or a parent where there is a safety or custody concern.

* Only a **Super Admin** can revoke or restore access.
* You do it from the web portal. The mobile app does not have this control yet.
* The person is **not told**. No email or notification is sent.
* Everything they recorded stays in your records.

***

<Note>
  This works the same for schools, daycares and sports clubs. Wherever this page says "child" or "parent", read "student" or "athlete" and "guardian" for your organisation. Staff and Guardians are on plans that include staff management.
</Note>

## Revoke someone's access

1. In the left sidebar, click **Staff** for a staff member (teacher, carer, coach or other), or **Guardians** for a parent.
2. Find the person.
3. On the person's row, choose **Revoke access**. On a staff row this is in the **⋯** menu. On a guardian row it is the red icon at the end of the row.
4. Type a reason. It is kept in your records and is **not** shown to the person.
5. Confirm.

The person is signed out everywhere and cannot sign in again, whether they use a password, an emailed code or a sign-in link. Their row shows a red **Access revoked** label.

<Note>
  If the person already had the app open, they are signed out the next time it contacts the server. If a message says an open session "may continue for up to 24 hours", their sign-in is still blocked.
</Note>

***

## What happens to a revoked parent

A revoked parent stays on each child's record, so you keep their name and contact details. But they:

* no longer receive emails about the child (end-of-day report, payment reminders, camp notices, health plan and form emails, photo notifications);
* lose access to all of their children's information and photos at your centre;
* cannot be chosen at check-out as the person collecting the child.

Revoking applies to the person's whole account at **your** centre only. If the same email address is used at another centre, nothing changes there.

***

## Every child needs a guardian

A child can never be left without a guardian. If the person you are revoking is the only guardian (who isn't already revoked) for any child still at your centre, revoking is refused. The message names the children. Add another guardian to each of those children first, then revoke.

* The other guardian only needs to be on the child's record. They do not need to have signed up yet.
* Children who have left your centre do not count.

***

## Restore someone's access

1. Open **Staff** or **Guardians** and find the person.
2. Choose **Restore access** from the same menu or icon.
3. Confirm.

They can sign in again straight away. Anything they had open before the revoke stays closed, so they sign in fresh.

***

## Access ends on (staff)

When you add or edit a staff member, the optional **Access ends on** date is the **first day they no longer have access**. At 12:01am on that day, in your centre's local time, their access is revoked in the same way.

For example, if a carer's last shift is Friday, set **Access ends on** to Saturday.

If you restore someone whose date has already passed, the date is cleared so they are not revoked again.

***

## Things to know

* You cannot revoke yourself, and you cannot revoke the last active Super Admin. Make someone else a Super Admin first.
* If you use a school-system connection, revoked people are not added back by the next sync.
* You cannot send an invitation or login details to a revoked person. Restore their access first.
* An old invitation or password-reset link will not work for a revoked person.
* Revoke access replaces the old **Deactivate** button on the staff list.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.