Skip to documentation
Browse documentation
How-to guideOrganizations and access

Manage a Code Voucher workspace

Keep repositories, private runs, teammates, and integrations inside one organization boundary, then grant each person only the access they need.

Choose the active workspace

After GitLab sign-in, create your first workspace or choose one from the workspace selector. A user can belong to several workspaces, but every repository, run, invitation, and provider connection remains scoped to the selected workspace.

Role permissions

RoleAccess
OwnerManage repositories, integrations, members, and roles. Only an owner can grant administrator access.
AdminManage repositories, integrations, members, and member/viewer roles. Cannot change owners or grant administrator access.
MemberView private runs. The current release does not grant members workspace or repository configuration access.
ViewerRead-only access to the workspace and its private runs.

Owner invitations are not supported in the current release. An owner cannot be modified through team management, and no one can change their own access there.

Invite a teammate

  1. 1

    Open workspace settings

    Select the intended workspace, then open Settings and find Team management.
  2. 2

    Enter the exact GitLab username

    Code Voucher resolves the username through the workspace GitLab service account and binds the invitation to GitLab's immutable user ID.
  3. 3

    Choose a role and create the invitation

    Owners may invite administrators, members, or viewers. Administrators may invite members or viewers.
  4. 4

    Copy the link once

    The invitation link is displayed only when it is created or rotated. Share it through an approved private channel.
  5. 5

    Accept with the invited GitLab account

    The recipient reviews the workspace and role, then signs in. A different GitLab account cannot accept the invitation.

Maintain access

  • Invitation links are single-use and expire after seven days by default
  • Rotate a lost invitation to invalidate its previous link
  • Revoke an invitation that should no longer be accepted
  • Change member and viewer roles when responsibilities change
  • Suspend access immediately, then reactivate it without issuing a new invitation
  • Review the active workspace before changing a team or provider connection