Skip to content

Admin panel

The Admin panel is where access is granted. Every account that can sign in to RSP Lab is listed here, with the role it holds in each application. Administrators grant and revoke that access, and handle the rare account problems: disabling sign-in, ending sessions, merging duplicates, deleting an account.

Addressadmin.rsplab.click
Accessa grant on the admin project — read to look, admin to change
Sign-inRSP Lab account
The Admin panel sign-in page.
Sign-in. Access is refused until an administrator grants it; absence of a grant is denial.

Quick path: give someone access

  1. Open Users and find them — filter by name or email.
  2. Select them. Their details and Access open on the right.
  3. In the grant editor, pick the project from the list and choose a role, then grant it.
  4. They get the new access the next time they sign in.

Someone who has no account yet: choose Invite user, and their access can be granted straight away — before they have ever signed in.

ApplicationProject
SM-DP+ consolesmdpp
eIM consoleeim
OTA consoleota
SM-DP consolesmdp
SM-SR consolesmsr
Entitlement consoleentitlement
ASN.1 Editorasn1editor
Attach Flow Inspectoropen5gs
eSIM simulatorsimulator
Applet Labappletlab
This paneladmin
Engineering documentationdocs

* means every project. Use it sparingly: a role on * applies to applications that do not exist yet.

Users and clients

The Users table: identifier, name, email, sign-in method, access chips and state, with one user's details open.
One row per principal. A grant is one role on one project, and the star row is every project at once.

Users are people. Clients are machines — scripts and services that sign in on their own. Both tables show each account’s identifier, name, email, how it signs in, one chip per grant, and whether it is enabled.

On a phone the panel reflows: the sections become a row across the top, and the details of whoever you select open underneath the list instead of beside it.

The Clients table.
The OAuth clients registered with the estate identity issuer.

What an administrator can do

ActionWhat it does
Grant / RevokeAdd, change or remove one role on one project
Disable / Enable sign-inStop an account signing in, without deleting it
Revoke all sessionsSign the account out everywhere, now
Invite userCreate an email-and-password account. They are emailed a temporary password, valid three days.
Set passwordSet one directly: temporary (they must change it at the next sign-in) or permanent. At least 12 characters, including a lowercase letter.
Reset passwordEmail a reset code (email-and-password accounts only). On an account that has never signed in, the invitation is sent again instead.
Delete this userRemove the account and all its access. Asks you to type to confirm.
Rotate secretIssue a client a new secret. The old one stops working.

You cannot delete the account you are signed in as.

Same person, two accounts

Signing in with Google one day and an email and password the next creates two accounts. When the panel sees a password account sharing an email with a Google account, it offers Same person, two accounts.

Merging copies the Google account’s grants onto the password account — keeping the higher role wherever both have one — and then deletes the Google account.

Troubleshooting

You seeWhyWhat to do
No access to this panelYour account holds no grant on adminAnother administrator must grant it
Buttons refuse with a role errorYou hold read on adminAsk for admin
Password actions are unavailableThe account signs in with GoogleGoogle manages that password
An invited person never got the emailMail from the sign-in service is often filteredAsk them to check spam, or use Set password and tell them directly
Someone still has access after a revokeTheir session is still openRevoke all sessions