When an advisor finishes working with you, remove their access from each place you shared files: direct invitations, groups, folders and shared links. Keep the files available to the people continuing the project. Check the changes before marking the handover complete, and deal separately with copies the advisor already downloaded.
The advisor's last call is on Friday. Your colleague still needs the budget on Monday, and the project folder includes work from both of them. You want to close one person's access without turning the next working day into a search for missing files.
Agree what finishes and when
Choose a date and time for access to end. Confirm which files the continuing team needs, where the current versions are and who will answer any remaining questions.
For a planned departure, have that person open the files before the cutoff. If the advisor holds the only editable copy, arrange the agreed handover first. The client file handover guide can help you collect the working context as well as the documents.
If access needs to stop because of a security incident, follow your incident process promptly. Routine handover arrangements can follow.
Look for every way the person can open the files
Start with the email addresses the advisor used. They may have accepted an invitation with a different address from the one in your recent messages.
For each project, check direct access, group membership, access inherited from a parent folder or site, and links that anyone holding them can use. Check pending invitations too, so an unused invitation does not leave a way back in.
Microsoft's OneDrive and SharePoint sharing instructions, for example, treat direct access and sharing links separately, and explain that inherited access may need to be changed at the parent folder or site.
Make one row for each route you find. A small consultancy might start with this:
| Where access comes from | Change to make | Check afterward |
|---|---|---|
| Direct invitation to the project room | Remove the departing advisor | Their room membership is gone; the continuing colleague still opens it |
| A project group that includes the advisor | Remove that person from the group | Other group members keep the files they need |
| A proposal link that anyone holding it can open | Give continuing reviewers a restricted link, then remove the old link | The old link fails and the new link works for an approved reviewer |
| An invitation sent to a second email address | Cancel the unused invitation | It no longer appears as an active invitation |
These are possible routes, so use only the rows that apply to your tools. If you cannot see where access comes from, ask the workspace administrator before treating it as removed.
Use the free access removal worksheet to record the person, each route, the change and the result.
Change the person's access without dismantling the project
Remove the individual membership where that is how access was granted. Removing an entire group or deleting its shared folder can interrupt everyone else.
A broadly shared link needs separate attention. Removing a named person will not stop them using a link available to anyone who has it. Microsoft describes this distinction in its external sharing overview. Where your service allows it, move the continuing reviewers to access tied to their own accounts, check that it works, then close the old link.
Check other systems the advisor used as well. A document room does not control access to a separate design tool, cloud drive or client portal. If the advisor managed a connection or shared credential, ask the administrator responsible for that system to review it.
You may choose to keep a narrow window for one unfinished task. Write down the task, the files needed and when access will be reviewed again. Read-only access still lets someone read the material, so keep it only while there is a reason.
Check both the departure and the continuing work
First, review the saved permissions after each change. Confirm the person's direct membership, group access and outstanding invitations have been dealt with.
Then check what someone can actually open. If the departing advisor is available, ask them to try an old link while signed in to their own account. They should tell you the result without sharing their password. Use any administrator access-check tools your service provides to help inspect the remaining routes.
Opening the link while signed out only tests anonymous access. It does not show what that person's signed-in account can still reach.
For a repeatable practice run, use harmless sample documents and a separate test account you control. Give it the same access routes, remove them and try the old links. Record that as a process test; it does not replace checking the real person's memberships.
Finally, ask a continuing colleague to open a file they need for their next task. Record any check you could not complete and who will follow it up. A failed check is useful information to fix before Monday.
Handle downloaded copies separately
Changing access to the shared source does not recall ordinary files already saved on someone's device or sent as email attachments. Agree how those copies will be returned, retained or deleted under your existing arrangements. A closed link cannot prove that a local copy was deleted.
The download permissions guide explains how to make those decisions before sharing the next pack.
Keep a short completion note with the cutoff time, changes made, checks passed and outstanding actions. That gives the next project lead something more useful than an email saying "all sorted."
Try the process with a small project room
In Aurora, an administrator with permission to manage a room can remove a participant and revoke an unused room invitation. Keep the project's files in the library for the people who still need them. Review the person's other rooms and any organization or library access separately; removal from one room is specific to that room.
You can practice with sample documents during the 30-day Starter free trial, with unlimited libraries, two rooms, three internal users, 25 external users and 10 GB. No card is required and nothing is charged automatically. Give a test participant access to one room, remove that membership, and check that a continuing participant can still open their files.
Try Aurora with a sample project. Start with the free worksheet if you are reviewing an existing setup today.
Departing advisor access worksheet
Free to use and adapt. Keep your completed worksheet in your own project files.
Download Worksheet (.md)Use one copy for one departing person. Keep it with the project's internal records. The completed rows below show a possible process; replace them with your own tools and checks.
Before the cutoff
- Project:
- Departing person and all invited email addresses:
- Person making the changes:
- Access ends on (date, time and timezone):
- Person continuing the work:
- Current files and editable sources checked:
- Remaining task, if any:
- Separate services to review:
Worked example
A consultancy advisor finishes on Friday at 17:00 local time. The project coordinator continues on Monday.
| Route | Action | Departure check | Continuing work check |
|---|---|---|---|
| Direct room membership | Remove the advisor | Saved member list no longer includes the advisor | Coordinator opens the current budget |
| Project group | Remove the advisor from the group | Review other memberships for that address | Other group members retain access |
| Anyone-with-link proposal | Move remaining reviewers to restricted access and remove the old link | Old link fails; check for other active links | Approved reviewer opens the replacement link |
| Pending invite to another address | Cancel the invitation | Confirm it is no longer active | No change needed for other reviewers |
These rows show possible actions and expected checks. Record your actual results in the table below.
Your access list
Add a row for every direct, group, inherited or link-based route. A person can have several routes to the same file.
| Tool and file, room or folder | Email or group involved | Route | Change and person doing it | Time saved | Departure check and result | Continuing work check and result |
|---|---|---|---|---|---|---|
Use "checked", "needs a change" or "not yet checked" with a short explanation. A signed-out browser checks anonymous access only. A sample-account exercise checks the process; record the real person's permissions separately. Never request their password.
Copies and unfinished work
- Ordinary downloaded or emailed copies known to exist:
- Agreed handling of those copies and person following up:
- Confirmation received, if any, and date:
- What remains unknown:
- Temporary access still needed for a specific task:
- Files included and next review date:
- Separate tools, connections or credentials referred to their administrator:
Do not record a local copy as deleted solely because its original link stopped working.
Completion note
- Changes completed at:
- Continuing colleague and file they opened:
- Checks still missing:
- Person and date for each follow-up:
- Project lead who received this note:
Related guide: /guides/remove-departing-advisor-access
