Invite team members and manage roles in your workspace
Invite teammates to your Voroa workspace by email and give each one a role: Admin, Developer, Contributor, Viewer or Billing. See what every role can do.
To add a team member on Voroa, open Settings → Team Members, enter your teammate’s email, pick a role, and select Send invite. Your teammate accepts the email invitation, signs in with that same email address, and lands in your workspace with the access their role allows. Invitations expire after 7 days.
Each member signs in with their own account, so nobody shares a password, and you can change or remove anyone’s access at any time.
The short version:
- Open Settings → Team Members in your workspace.
- Enter the teammate’s email address.
- Choose a role: Admin, Developer, Contributor, Viewer or Billing.
- Select Send invite, or copy the invite link and send it yourself.
- Your teammate accepts within 7 days, signing in with the invited email address.
Team members are available on paid workspace plans. On the Free plan a workspace has a single member: you. How many members a workspace can have depends on its plan; see pricing for the seats on each plan.
Which role should I give?
| If your teammate needs to… | Give them |
|---|---|
| Run everything, including members and billing | Admin |
| Build, configure and deploy services and databases | Developer |
| Deploy, restart and read logs, but not change configuration or see secrets | Contributor |
| Only see what is running, for example a manager or a client | Viewer |
| Handle invoices and payments, for example an accountant | Billing |
Start with the smallest role that lets someone do their job. You can raise it later in one step.
Member roles
Each member of a workspace has one of the following roles:
| Role | Description |
|---|---|
| Admin | Full access to the workspace’s resources and settings, including member management and billing. The workspace’s creator is automatically an Admin. |
| Developer | Full access to the workspace’s services, databases, and integrations — but not members, billing, or workspace settings. |
| Contributor | Can trigger deploys and restarts and view logs and metrics. Cannot create or configure services, and cannot see environment variables or database connection details. |
| Viewer | Read-only. Can see services, deploy status, and metrics. Cannot view logs, environment variables, or connection details, and cannot change anything. |
| Billing | Manages billing and payment settings only. Can see the workspace and its members, but not logs, metrics, or service configuration. |
The person who created the workspace is its owner. The owner is always an Admin, cannot be removed, and cannot leave the workspace.
The same tables below are available in-product under Roles & permissions (select Show) on the Team Members page — so there is never any guesswork about what a teammate will be able to access before you invite them.
Role permissions
Yes = permitted. — = not permitted.
Workspace administration
| Permission | Admin | Developer | Contributor | Viewer | Billing |
|---|---|---|---|---|---|
| View workspace members | Yes | Yes | Yes | Yes | Yes |
| Invite, remove, and change members | Yes | — | — | — | — |
| Manage workspace settings | Yes | — | — | — | — |
| Manage billing and payment settings | Yes | — | — | — | Yes |
| Leave the workspace (non-owners) | Yes | Yes | Yes | Yes | Yes |
Projects and environments
| Permission | Admin | Developer | Contributor | Viewer | Billing |
|---|---|---|---|---|---|
| Manage projects and environments | Yes | Yes | — | — | — |
Services and datastores
| Permission | Admin | Developer | Contributor | Viewer | Billing |
|---|---|---|---|---|---|
| View services and deploy status | Yes | Yes | Yes | Yes | Yes |
| Create services | Yes | Yes | — | — | — |
| Modify service configuration | Yes | Yes | — | — | — |
| Trigger deploys, restarts, and rollbacks | Yes | Yes | Yes | — | — |
| Delete services | Yes | Yes | — | — | — |
| Manage environment variables and secret files | Yes | Yes | — | — | — |
| Manage custom domains | Yes | Yes | — | — | — |
| Configure databases and view connection details | Yes | Yes | — | — | — |
Observability
| Permission | Admin | Developer | Contributor | Viewer | Billing |
|---|---|---|---|---|---|
| View service and build logs | Yes | Yes | Yes | — | — |
| View metrics | Yes | Yes | Yes | Yes | — |
Integrations
| Permission | Admin | Developer | Contributor | Viewer | Billing |
|---|---|---|---|---|---|
| Manage the GitHub connection | Yes | Yes | — | — | — |
Invite a teammate
- Open Settings → Team Members.
- Enter your teammate’s email address, choose a role, and select Send invite.
- Your teammate receives an invitation email with an Accept invitation link. You also get a shareable link you can copy and send yourself — both do the same thing.
Your teammate signs in — or creates a Voroa account — with the same email address the invite was sent to, and lands directly in your workspace. Invitations expire after 7 days.
A few guardrails to be aware of:
- If you hit your plan’s member limit, upgrade the workspace plan to add more teammates.
- You can only invite someone at a role up to your own — a member with member-management rights can never mint a role above their own.
- Re-inviting the same address re-sends the invitation with a fresh link (the old link stops working). Re-sends are capped per day to prevent abuse.
Pending invitations
Invitations that have not been accepted yet are listed under Pending invitations, with the invited role and when the invite expires. From there you can:
- Resend — issues a fresh link and sends the invitation email again.
- Revoke — cancels the invitation immediately. The link stops working.
Change a role or remove a member
Admins can change any member’s role from the dropdown next to their name, or remove them with Remove. The member is notified by email when their role changes or their access is removed. Removal takes effect immediately; their own Voroa account is not affected, and you can invite them again at any time.
You cannot change your own role or remove yourself this way — ask another Admin.
Leave a workspace
If you are a member (not the owner) of a workspace, you can leave it from Settings → Team Members → Leave workspace. You lose access to the workspace and its services; an Admin can invite you back later.
Frequently asked questions
How many team members can a workspace have?
It depends on your workspace plan. The Free plan allows one member, the owner. Paid plans allow more; see pricing for the seats on each plan. If you reach the limit, upgrade the plan to invite more people.
Can a team member see my environment variables and secrets?
Only Admins and Developers can manage environment variables, secret files and database connection details. Contributors, Viewers and Billing members cannot see them. Saved environment variable and secret file values cannot be read back by anyone, Admins included; Voroa shows only their names. Admins and Developers can reveal a managed database’s password, and every reveal is logged.
Can I give an accountant access to invoices only?
Yes. Invite them with the Billing role. They can manage billing and payment settings and download invoices, but they cannot see logs, metrics or service configuration.
What happens when I remove a team member?
They lose access to the workspace immediately and receive an email telling them so. Their own Voroa account is not deleted, and you can invite them again at any time.
Can I transfer workspace ownership?
No. The owner is always the person who created the workspace. The owner cannot be removed and cannot leave the workspace. To share full control, give another person the Admin role.
Why does my teammate see “This invitation was sent to a different email address”?
They signed in with a different email address from the one you invited, or they have not verified that address yet. Ask them to sign in with the invited address and verify it, or send a new invitation to the address they use.