Members and roles
Roles, what each role can do, invites, and the handle every member needs to start reviews.
Every member of a workspace has a role. The role decides what that member can do.
The four roles
- Owner. Full control of the workspace, including billing. A workspace always keeps at least one owner, so you cannot remove or demote the last owner.
- Admin. Manages members, repositories, and team settings. An admin can edit and remove admins, members, and viewers, but cannot change an owner.
- Member. Works day to day and can start reviews on connected repositories.
- Viewer. Read-only. A viewer reads reviews and repositories but cannot start a review.
Viewers are free
Vetoo bills per seat, and a viewer is not a seat. A viewer costs nothing and does not count against your plan's seat limit. You can therefore give read-only access to as many people as you need.
In exchange, a viewer cannot start a review. Vetoo also skips auto-review on a request that a viewer authored. Anyone who needs a review of their own code needs the Member role or above, and a seat.
Invite someone
An owner or admin invites a member by email from the Members page. The inviter sets the role at that time: Admin, Member, or Viewer. An invite cannot grant Owner. To make someone an owner, change their role after they join. Pending invites appear on the same page, and you can revoke one before the person accepts it.
Nobody, not even an owner, can change their own role. Ask another owner or admin to change it.
An invited member adds a seat and bills a full period for that seat, not a prorated amount. If you remove the member later, Vetoo issues no refund. The seat stays yours until the period ends, and the lower count bills from your next renewal. See Plans and credits for the full seat rules. An invited viewer never adds to the bill.
If an invite returns a seat-limit message, your plan has no free seat. Move to a tier with more seats, or free a seat. If read-only access is enough, invite the person as a viewer instead.
Handles start reviews
Vetoo matches a request to a member by their GitHub or GitLab handle. Until someone sets that handle on a member profile, Vetoo does not review that member's requests. Anyone can set their own handle, and an admin can set it for anyone else from the Members page. Check the handle first when a review does not run, because this step is easy to overlook.