Roles & access

Once your app has a login, not everyone needs the same powers. Roles let you sort people into groups and give each group the right level of access — so an admin can manage everything while a member only works with their own information.

The common roles

Most apps only need two or three:

Admin — full control. Sees everything, manages records across all people, and handles the app’s day-to-day. Usually that’s you and a trusted colleague.
Member — the everyday user. Signs in and works with their own information, but can’t see other people’s or change how the app runs.
Visitor — someone not signed in at all. Sees only the pages and actions you choose to make public.

You can name and shape roles to fit your app — “staff” and “customer,” “editor” and “reader,” whatever makes sense for you.

Gating pages and actions

Roles let you put a gate in front of a page or a button, so only the right people get through. Describe the rule you want in plain language:

“Only admins can open the reports page.”

“Members can add their own entries, but only admins can delete.”

“Hide the settings page from everyone except me.”

Exepad applies the rule everywhere it matters — a member simply won’t see the admin page, and a gated action won’t be available to someone without the right role.

Example scenarios

App	Admin can…	Member can…	Visitor can…
Team task tracker	See and manage everyone’s tasks	Manage their own tasks	— (sign-in required)
Client portal	See every client’s files	See only their own files	See the welcome page
Community blog	Publish and edit any post	Write their own posts	Read published posts

Who gets which role

By default, people who sign up are ordinary members, and you’re the admin. You decide who gets promoted — for example, giving a colleague admin access so they can help you run things. You manage that from your owner tools; see Managing users.

Next steps

Managing users — see who’s signed up and set their roles.
Viewing & editing your data — how roles shape what each person sees.