Short guides to the things operators do every day.
GuidesShort walkthroughs of the work that comes after setup: answering a customer who cannot sign in, handing a teammate part of the panel without handing over everything, and deciding which emails Rekey sends on your behalf. Each one is a minute or less, and written out in full beside the video. For setting up your first Application, watch the walkthrough.
Help a customer from the panel
Someone writes in and cannot sign in. Find them by email, read their account, and fix it without asking them for a password or running a query by hand.
Find the person
Every Application keeps its own list of end users. Search it by email address.
Read the account
One page carries the whole account, split into tabs: overview, subscriptions, devices, credits, security, and data.
Support actions
Clear an account lockout, resend verification, send a password reset, reset devices, or sign them out everywhere. Each one is recorded in the activity trail with your operator id.
Subscriptions and devices
What they pay for and when it renews, then the devices their sessions are bound to. Releasing a device ends that session.
Security history
Every security event on the account, including sign-ins that failed, so you can tell a lockout from a forgotten password.
Give a teammate less than everything
A support contractor needs to read end users and nothing else. Operator permissions restrict a workspace member area by area, and the panel stops rendering what they cannot use.
Invite as a member
Scopes apply to the MEMBER role. Owners and admins are not restricted by them.
Restrict area by area
End users, billing, sign-in configuration, developer, organizations, activity and overview each take none, read, or read and write.
Save
The panel does not grey out what a member cannot reach. It does not build those tabs at all, and the API refuses the calls behind them.
Decide which emails Rekey sends
Rekey sends verification, reset and magic-link email for you. Turn the whole set off for one Application, or go one email at a time, and read the log of what went out.
One switch for all of it
Turning email off is per Application, so a test Application can go quiet while production keeps sending.
Or one email at a time
Welcome and the dunning reminder each have their own switch. Verification, magic link and password reset have one too, until a live sign-in method depends on the email, and then the row says so rather than offering a control. Two are never switchable here: workspace invitations and the operator unapplied-payment notice go out through a path this Application does not gate.
The send log
Every send is recorded, so you can show a customer what was sent to them and when.
The same pattern elsewhere
The MCP server for an Application is one page and one switch, in the same place.
Where to go next
Everything on screen is sample data. The names and addresses belong to nobody.
If you would rather read than watch, the same ground is covered step by step on the blog, and the documentation has the API behind each one.