Skip to main content
Open console

Teams and people

Who a project belongs to, and what each role in a team can do.

6 min read

Everything in the console belongs to a team: projects, machines, disks, integrations and access tokens. You see what your teams own and nothing else. SSH keys are the exception: they belong to you, in every team you are in.

Every console address carries the team: /{team}/projects/…, where {team} is a short id the team was given when it was made.

If you belong to a single team, the console fills it in and the field is not shown. It becomes a choice once you belong to more than one.

Roles

Each role can do everything the roles below it can, plus its own.

Role Can
Viewer See projects, environments, machines and their state. Changes nothing
Developer Everything above, plus work on the sites: deploy, open a shell, edit variables, take and restore backups, and add staging or development environments where the subscription has room
Admin Everything above, plus run the team: start projects and change their terms, resize and remove machines, move and add services on the Resources tab, delete environments, reset a database, switch the maintenance page on, change secret variables, manage integrations, notifications, people, invitations, the audit log and the project groups
Owner Everything above, plus the money: billing, invoices, cancelling, deleting a project, and making another owner. A team always keeps at least one

Developer is the role you give an outside developer: it works on the sites and decides nothing for the team. Anything that spends money, removes something or changes who can do what is Admin and above.

Production needs an Admin to deploy it, redeploy it or go back a release, and to open a shell in it, export its database, download a backup or copy it into another environment: each of those reads its data or its secrets. A Developer there still restarts it, takes backups, edits ordinary variables and reads its logs. Anything that reshapes or overwrites it, a restore included, needs the Owner. Its domains follow the same rules.

On staging and development, protected or not, a Developer does all of this. Protection only decides whether an environment is kept when its branch is deleted.

Adding somebody

Invite them by email address from the team's People page. They get a link, and they join with the role you chose.

Withdraw an invitation from the same page. A person you remove loses access immediately, including anything they had open.

Only some projects

An invitation covers every project the team owns. When you invite somebody you can instead name the projects they should reach: they can do everything a full member could, inside those projects and nowhere else.

  • The role still decides what somebody may do; this only decides where.
  • An Owner cannot be narrowed.
  • What belongs to the team is untouched: the team itself, its keys and its billing.

How people are counted

The first person on a project is included. Past that, a project is in one of three bands: up to 3, up to 10 and up to 30 people. What each costs is on the price list.

Inviting somebody inside a band changes nothing on the invoice; the price moves when the project moves to the next band. Past thirty, talk to us.

A project counts the people who can reach it. Somebody invited to one project counts on that project and no other. Somebody who works across the team counts on every project.

Integrations

Services your team already pays for, connected once and used by any project: a log collector, storage for your backups, somewhere to send notifications, and an APM account (Monitoring says what APM covers). They are under your team's settings, and Admins and Owners manage them.

Each one carries what that service needs to identify the account (a Datadog site, an Axiom dataset, a Loki endpoint) and its token. Tokens are encrypted and never shown again; you can replace one, but not read it back.

Integrations covers what can be connected and what each one is used for.

Single sign-on

A team can put its identity provider in front of the team: Microsoft Entra ID, Okta, Google Workspace, Keycloak, anything that speaks OpenID Connect or SAML 2.0. It is on top of the Vallic sign-in, not instead of it. Everybody still signs in to Vallic with their own password and authenticator. Google or GitHub can stand in for the password, never for the authenticator. The team's members at the email domains you list also sign in at your provider every few hours.

  • Somebody your provider disables loses the team when their session there ends, at most the hours you set (1 to 720, 12 to begin with).
  • Only the domains you list are asked. Members at any other domain keep their own sign-in.
  • One sign-in covers the browser, vallic and their SSH key for the team. Until they have signed in at your provider, the team's pages send them there, the API answers sso_required with the address to sign in at, and their key is not on the team's machines.
  • An access token is issued only after signing in there, and then works for its lifetime.
  • The address your provider signs in must be the account's own. Nobody is created or linked: people are still invited as before.
  • You require it of your own domain only once you have signed in through it. Save it with the requirement off, sign in from the card, then require it: a provider set up wrong would otherwise shut the team to everybody at the domain. If it stops working later, an Admin outside the domains, or support, can turn it off.

It is a subscription of the team's own, €49 a month whatever the team runs. The Owner takes it out under Single sign-on on the team's settings page. If it ends, the provider stays as it is and still required where it was. It can then be removed but not changed.

An Admin or an Owner sets it up on the same page: the protocol, the provider's details, the domains, and how long a sign-in there counts. The page shows what to register at your provider: the redirect URI for OpenID Connect, the entity ID and reply (ACS) URL for SAML.

Confirming it is you

Some changes ask for your password again when you last confirmed it more than five minutes ago, even though you are signed in:

  • issuing an access token, or adding an SSH key
  • inviting somebody, or changing what a member may do
  • showing a backup key, or making a secret variable readable
  • deleting an environment or a backup
  • cancelling a project or a subscription
  • setting up, changing or removing single sign-on
  • removing a connected Google or GitHub sign-in, under Security on your account
  • restoring a backup over production

The console takes you to the confirmation and back to what you were doing; vallic opens the browser for it. A personal access token cannot confirm, so a pipeline cannot do any of these.

Signing in with Google or GitHub is not a password confirmation. These changes still ask for your password. If you never set one, choose Forgot your password? on the sign-in page.

Audit log

Every change that costs money or alters access is recorded: machines bought and destroyed, disks grown, people added and removed, roles changed. It answers when something changed and who changed it. Admins can read it from the team page.

Next

Need a hand?

Open a ticket from Support in the console. We answer on the ticket.

Open the console How support works