# Test admin and member roles: what each person can see and do

> Permission bugs show a member a button they should not have, or hide one an admin needs. Test each role with its own stored account and check the screen for both.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/test-admin-and-member-roles/

## Roles break quietly

Role checks live in many places at once: the menu, the page, the button, the API. A change to one leaves the others behind. The result is a member who sees **Delete workspace** and gets an error when they click it, or an admin who cannot find billing because the menu item was hidden by mistake.

These are visible bugs, and they are the kind people notice in front of a customer.

## One account per role

Store one [sign-in account](https://testsy.dev/docs/sign-in-accounts/) per role in the project: "admin", "member", "viewer". Passwords are encrypted, never shown again and never sent to the AI; the tester types them into your sign-in form.

Then one test per role, written about what that person should and should not see:

```text
Sign in with the stored account "member".
Open Settings.
Check the Billing section is not shown and there is no
"Delete workspace" button.
Open the address https://app.example.com/settings/billing directly
and check the page says the member has no access.
```

```text
Sign in with the stored account "admin".
Open Settings and check the Billing section shows the current plan.
Invite this run's email address as a Viewer and check it is listed
as pending.
```

The second line of the member test is the important one: hiding a button is not the same as refusing access, and opening the address directly is how a curious member finds out.

## What the browser test proves

It proves what each role sees and what the pages allow. It does not prove your API refuses a member's request sent outside the app; that is a security test of the backend. Run both, separately. [What an AI tester cannot check for you](https://testsy.dev/blog/what-an-ai-tester-cannot-check-for-you/) draws the line.

## Keep them in one project

Put the role tests together and press **Run all** after any change to permissions. The project page groups tests by their last result, so a role that regressed stands out.

![The team page in Testsy: people, their roles and invitations waiting to be accepted.](https://testsy.dev/docs/img/team-light.webp)

That screenshot is Testsy's own team page, with viewer, member, admin and owner roles: the same shape of problem, and the same way to test it.

This post is part of [Release testing for product teams](https://testsy.dev/blog/release-testing-for-product-teams/).
