Team access
Previewops automatically tracks everyone who logs into the dashboard and assigns them a role based on their GitHub org membership.
Roles
| Role | Access |
|---|---|
| Admin | Full control — manage credentials, tokens, billing, add-ons, and team members |
| Member | View the dashboard, credential and token lists, and add-on status; deploy, redeploy, and delete preview environments |
Role is resolved automatically at login via the GitHub Membership API. You cannot manually assign roles; they mirror your GitHub org roles.
Personal installs (where the installed org is the same as your personal GitHub account) are always given admin access.
People page
Admins can view and manage team members at Dashboard → People.
The page shows:
- Everyone who has ever logged into the dashboard
- Their role (admin / member)
- Last login time
- Block status
Block a user
Blocking prevents a user from logging in. Their existing session is terminated on their next request.
To block: click Block on the People page. To unblock: click Unblock.
Remove a user
Removing deletes the user from the list entirely. They can log back in unless also blocked.
Removing a user does not remove them from the GitHub org. Manage org membership on GitHub.
FAQ
Can a member trigger deploys via comments?
Yes. Members can deploy, redeploy, and delete previews from the dashboard. PR comment deploys (/deploy-previewops) are gated separately by GitHub repository permissions.
What happens if I remove someone from the GitHub org?
Their next login attempt will resolve their role as member (the fail-safe). If you want to prevent dashboard access entirely, block them on the People page first, then remove them from GitHub.
Can a member see credentials? They can see the list of stored credential provider keys, but not the credential values (those are never shown in the UI). Add/update/delete buttons are hidden for members.