Your group

The platform is organized around one rule: each customer gets one top-level group. Everything belonging to your organization is inside it, and nothing crosses between customers.

The tree

code.vector.cloud/
│
└── <your-organization>/          ← your top-level group
    │
    ├── teams/                    ← who works here
    │   ├── <department-a>/
    │   └── <department-b>/
    │
    ├── registries/               ← packages and container images
    │   ├── docker/
    │   ├── pip/
    │   ├── choco/
    │   └── …
    │
    ├── <project-1>/              ← your projects
    └── <project-2>/

Vector's own group has the same shape, as do groups created for workshops and for individual collaboration projects.

Not every group has every part

Registry types are enabled individually, and groups created before the convention settled do not all have a teams folder.

The teams folder

teams/ is where people are managed, with one subgroup per department or working group on your side.

You are not a member of a project directly:

  1. You are a member of a team group, for example <your-organization>/teams/embedded-tools.
  2. That team group is invited to the projects it should work on.
  3. Your access to a project follows from your team membership.

A project's access list therefore does not have to be edited whenever somebody joins or leaves. It is also why a project you cannot see is usually a team-membership question: how to ask.

Team membership is managed by Vector

Adding someone to a team group, or removing them, is done by Vector. Send these requests to your Vector contact or support@vector.com.

The registries folder

registries/ holds the package and container registries available to your group, one project per package type.

Registries

Isolation and visibility

  • Customers are separated by top-level group. You cannot see another customer's group, and their runners cannot reach yours.
  • Groups start with zero access. Nothing is visible until access is granted explicitly.
  • Everything is private. Public visibility is disabled across the whole instance, so a project cannot be published to the internet by accident.

Roles

Role Who has it Can
Guest / Reporter Read-only participants View, comment
Developer You, normally Branches, merge requests, pipelines, publish packages
Maintainer Vector employees CI/CD variables, protected branch settings
Owner Authorized Vector employees only Group and project administration

Naming

New projects and subgroups are created by Vector, so ask your Vector contact and propose a name.