> A 15-minute weekly review of RestoreCord sub-users, permissions, sessions, 2FA and webhook URLs, so old staff access never becomes your next takeover.

Source: https://restorecord.today/weekly-access-review

# The weekly staff access review for Discord owners

Most server takeovers don't break in through the door. They walk in with keys someone was given months ago and never handed back.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)

Short answer

Once a week, open the Sub-Users tab of each server in RestoreCord, trim every teammate to the permissions their job needs, remove anyone who has left, check your own active sessions and 2FA, and rotate any log webhook URL that may have leaked.

## Why access gets a weekly slot, not a daily one

Your daily check watches what changes overnight. Access changes slowly: a moderator steps back, a helper is promoted for an event and keeps the role, an old laptop stays logged in. None of it is urgent on any single day, which is exactly why it piles up. Fifteen minutes every Sunday keeps the list short enough to read properly.

## Start with RestoreCord sub-users

Sub-users let teammates work on a server from their own RestoreCord account, so nobody ever needs your login. You'll find them under **Dashboard → Servers → Manage → Sub-Users**, available from Premium. Each row shows the person and the permissions they hold, and its menu offers Edit or Remove.

### Manage Sub-Users

Share server access with other users.

Add Sub-User

MOmod-team

View MembersPull Members

OPops-admin

Manage SettingsManage SnapshotsManage Firewall

Read every row against this table and ask, for each permission, whether this person used it in the last month:

| Permission              | What it allows                                                            | Who usually needs it                                  |
| ----------------------- | ------------------------------------------------------------------------- | ----------------------------------------------------- |
| **Manage Settings**     | Everything in server settings except managing sub-users                   | Co-owners and your most senior admin                  |
| **View Members**        | Username, avatar, country and verification date                           | Moderators who review new joins                       |
| **View Member Details** | IP, email, location and device (implies View Members)                     | Only the people handling ban evasion                  |
| **Pull Members**        | Starting migrations and recovery pulls                                    | Whoever runs recovery                                 |
| **Create Backups**      | Creating and viewing backups, not restoring or deleting                   | Anyone trusted to take a snapshot before a big change |
| **Manage Backups**      | Viewing, editing, deleting and restoring backups (implies Create Backups) | Owners only, in most servers                          |
| **Manage Firewall**     | Firewall rules and passwords                                              | Security-minded admins                                |

View Member Details exposes personal data, and Manage Backups can restore a snapshot over your live server. If you hesitate before ticking either, leave it unticked.

## Removing someone cleanly

When a teammate leaves, remove them the same day. Removal cuts their access to that server immediately and doesn't touch their RestoreCord account or any other server they help with, so it's a quiet, low-drama step. If they're only stepping back, edit their row down to View Members instead.

## Then look at your own account

Your owner account is the master key, so it gets the same scrutiny:

* Open **Active Sessions** and log out any device, browser or location you don't recognise.
* Confirm **Two-Factor Authentication** is still enabled, so a leaked password alone can't get in.
* If your Discord server requires 2FA for moderator actions, the bot owner's Discord account needs 2FA too, or the bot can't assign roles.

## Members who revoked access

People sometimes remove your bot's authorization from their Discord settings. RestoreCord's **Server Authorization Check** finds members who are no longer authorized and removes their verified role, and from Premium you can schedule **OAuth Authorization Checks** to run hourly, daily, weekly or monthly. A weekly schedule fits this review nicely.

## Finish with webhook hygiene

Your log channel's webhook URL is a secret. If it was ever pasted into a ticket, a screenshot or a public channel, delete that webhook in Discord, create a new one and update it in RestoreCord's Security tab. While you're in Discord, check that the log channel is still staff-only.

The review pairs with the [daily checklist](https://restorecord.today/daily-checklist) and the [monthly restore drill](https://restorecord.today/restore-drill). New to the log channel? Start with [setting it up](https://restorecord.today/morning-log-channel), or return to [RestoreCord Daily](https://restorecord.today/).

## This week's access review

Six items, about fifteen minutes. Work through them in order.

List everyone with dashboard access

Open the Sub-Users tab on each server and read every row: who it is and which permission chips they hold.

Trim permissions to the job

A moderator who only reviews members needs View Members, not View Member Details or Manage Backups.

Remove people who left the team

Removing a sub-user ends their access to that server immediately. Do it the day they step down.

Check your own active sessions

Review the devices logged in to your RestoreCord account and log out any you don't recognise.

Confirm 2FA is still on

Two-factor authentication on your RestoreCord account means a leaked password alone can't get in.

Rotate an exposed webhook URL

If a log webhook URL was ever pasted somewhere public, delete it in Discord and set a new one.

## Staff access questions

### 

### 

### 

## Hand out access without handing out your password

Invite teammates as RestoreCord sub-users and give each one only what their role needs.

[Invite my team](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
