Most apps need at least two types of users: admins (who can do everything) and regular users (who can do a subset). Overskill makes that easy.
Default roles
Out of the box, every new app has two roles:
- Member — someone you've let in, either because they bought a plan or because you gave them the role.
- Admin — can manage the app's users and has access to everything.
Signing up doesn't give someone a role automatically. You, the owner, manage the app from the Overskill editor; that isn't a role inside the app.
Where to find your app's users
On a computer, open the app in the editor and click Dashboard in the top bar, next to Preview. Then click Users in the Dashboard's left-hand menu. On a phone, tap the gear button in the editor's bottom bar (Dashboard and settings), then Users.
The list shows everyone who has signed up on that app. Someone appears there only after they've signed up on the app's own link, and that includes you: building the app doesn't give your sign-in inside the app a role. If a page is admin-only and you want to see it, sign up or sign in on the app, then set your own role here. Changing a role is free.
What your app knows about a signed-in person
Every signed-in person in your app has their own id, their email (if they signed in with one), their name if known, and their roles. Your app can also tell whether that person is the app's creator or a member of the app's workspace.
- Creator and workspace members: the app knows who they are, and they can use every feature. Only the creator can manage users.
- Roles: a person's roles are the ones you set in Users, your app's default roles, and any role a plan gives them. Someone with none counts as a regular user.
Admin
isn't automatic: the creator and workspace members get an admin role only if your app has a role called admin. If you want yourself or your team to see admin screens, ask the builder to check whether the person is the creator or a workspace member, rather than looking for an admin role.- Revoked access: when you revoke someone in Users, they're signed out within about a minute and can't sign back in.
In the editor, previewing as End user (the Preview as switch) uses a made-up test person, so its id and email won't match a real user.
Adding more roles
Most apps benefit from a third or fourth role. Tell the AI:
Add an
Editorrole. Editors can create and edit content but not delete it or invite new users.Add three roles: Admin (full access), Editor (create + edit), Reader (view-only).
Per-page permissions
Once roles exist, you can gate any page or button:
Only Admins can see the Settings page.
Editors can click the
Publishbutton, but Readers can't.Make the Users page Admin-only.
This hides pages and buttons. To make the data in a table admin-only too, see Making a data table private or admin-only.
Assigning roles to users
Three options:
- Manual assignment — in Dashboard → Users, pick a user and change their role
- Self-selection at sign-up — users pick their role when they create an account (good for marketplaces with sellers + buyers)
- Automatic by domain — users from
@yourcompany.comget Admin automatically (good for team tools)
Describe what you want and the AI sets it up.
Changing a user's role later
Open Dashboard → Users → click the user → change Role → save. Their access updates within seconds; they don't need to sign out.
Promoting users automatically from inside your app
Sometimes you want a user to move up a tier on their own — for example, someone redeems an access code, joins a group, or completes onboarding, and should instantly get the upgraded role with no manual step from you.
Your app can do this for you. Tell the AI:
When someone redeems a valid access code on the Claim page, automatically give them the
Member Plusrole.After a user finishes onboarding, promote them to
Verifiedso they get the higher limits.
The AI wires the promotion into your app directly. The user is upgraded the moment the action happens — if they're already signed in their access updates within seconds, and if they haven't signed in yet, the role is waiting for them the first time they log in. No more the owner has to notice and bump everyone manually.
What roles can't do
Roles control what users can SEE and DO inside your app. They don't change billing — only the owner can manage subscriptions and add seats.
What to read next
- How your app's users sign up — the broader auth setup
- Restricting access to paid users — gate by payment status
Invite beta testers before they sign up
You can invite a person by email to an app role before their first sign-in. Ask the builder to assign the intended existing role to that email. The role-invitation flow records the pending invitation; the person must use that email when joining. For someone already in the app, the role can be granted directly.
Use a dedicated tester role rather than giving testers admin access. Confirm the invitation or role grant, and test with both an invited account and an unrelated account.
Private access is not the same as disabling sign-up
An invitation grants a role; it does not by itself turn the platform sign-up page into an invite-only registration system. Have the app check the required role on every protected server operation. Requiring login alone does not prove someone was invited.
You can show a beta-plan button only to a role, but hiding a checkout link does not make the plan secret. A person may share the link. Do not rely on a hidden button for eligibility or billing rules.
Removing a tester role and revoking all access to the app are different actions. Choose the one that matches the outcome you want.