Elevated permissions for Discord staff. Only when needed.
umask gives staff the elevated role you choose after they authenticate, then removes it when their session ends. You remain in control of the role and its permissions.
How it works
Setup and authentication happen entirely in Discord.
-
Choose the roles
The server owner uses
/setupto select the permanent staff role and the elevated role. -
Issue a private code
The owner runs
/issue. Each staff member collects their phrase using/receiveand stores it securely. -
Authenticate when needed
Staff use
/authenticateto receive the elevated role for an allowed duration. It is removed on expiry or with/signout.
What umask needs
Just enough access to assign the role you've configured. No changes to its permissions.
- Manage Roles
- Allows umask to grant and remove your elevated role.
- A higher role position
- Place the umask bot role directly above the elevated role in Discord's role list.
umask doesn't need Administrator, access to message content, or the permissions contained in the elevated role.
A safeguard, not a guarantee.
umask reduces the time staff accounts hold elevated permissions. It cannot prevent misuse during an active session or guarantee immediate role removal during an outage. Read the limitations.