Getting help

Looking for access?

If you have no account, cannot see a project, or your sign-in has stopped working, go straight to Get access.

Your first point of contact is your Vector contact, the Vector employee who arranged your access. You can also write to support@vector.com.

A number of actions need permissions that customer users do not hold, by design. Going through Vector for those is the normal route, not an exception.

What to ask for

I want to… Notes
Create a project or group Say which group it belongs in, and propose a name. See naming
Get access to an existing project Usually resolved by adding your team group
Add or change a CI/CD variable or secret Needs the Maintainer role. See below
Get a package or tool made available Licensing may prevent redistribution
Get more, larger or different runners Say what your jobs need: CPU, memory, disk, OS
Reach an external host from a pipeline Firewall changes are manual and take days. See Network access
Extend a user's access before it expires Access is granted with an end date, and renewal can be requested
Reactivate a dormant account Accounts deactivate after 90 days of inactivity
Report a platform problem Include the project, pipeline and job URL

All of these go to your Vector contact.

Secrets

Secrets (tokens, credentials, API keys) must never be hardcoded. Not in .gitlab-ci.yml, not in a Dockerfile, not in a config file you commit. A committed credential stays in the repository history after it is removed, and has to be treated as compromised and rotated.

On the platform, they are stored in CI/CD variables:

  • Setting them needs the Maintainer role, so ask your Vector contact.
  • Reference them in your pipeline as $MY_SECRET_NAME.

Keep your own copies

The platform is backed up and replicated, but that is an operating measure for the platform and is not a substitute for your own copies. When your access ends, or when an environment with a fixed expiry date reaches it, the content stored in it is deleted. Take the copies you need before the date, not after.

How changes reach you

Planned platform changes are announced in the workspace before they take effect. Changes to your access, a deactivated account and deleted data are notified by email to your organization's Vector contact rather than to every user, so agree with them how those get passed on.

When you report a problem

Include this, and the problem can be diagnosed without a round of follow-up questions:

  • The project path and, where relevant, the pipeline and job URL.
  • What you expected to happen, and what happened instead.
  • The exact error message, copied rather than described.
  • Whether it worked before, and roughly when it stopped.
Platform sign-in Sign in to code.vector.cloud with your Vector ID
Vector ID sign-up Sign up for a Vector ID
GitLab documentation The upstream product documentation
GitLab CI/CD Pipeline syntax and reference
Vector support knowledge base Vector tools and licensing
Vector licensing Buying licenses for local development