Invites and roles
Velixir is built around teams. Every project belongs to one team; every app, database, and cache belongs to one project. Billing is per-team. Sign-in is per-user; one user can belong to multiple teams and switch between them.
Inviting someone
From the dashboard sidebar click your team name → Team Settings → Invitations → Invite member. Enter their email + pick a role.
We email them an invite link. If they don't have a Velixir account yet, the link takes them through register → email verify → and then auto-accepts the invitation on their first sign-in.
Roles
| Role | What they can do |
|---|---|
| Owner | Everything. Manage billing, change roles, delete the team. There's always at least one Owner. |
| Admin | Manage everything except deleting the team or changing Owner roles. Can manage billing and invites. |
| Member | Read access to team resources by default. Per-project / per-app Write grants can be added for resources they actively own. |
Members with no explicit write grant get a friendly "you have read-only access" notice if they try to mutate anything — not a 404, not a generic 403. The same applies inside the dashboard: read-only members see all the data, just no mutate buttons.
Per-project / per-app grants
When you invite a Member, you can grant them Write access to specific projects or apps from the same screen. This is how you let a contractor deploy to one project without giving them keys to everything else.
"Require 2FA" team policy
From Team Settings → toggle Require 2FA. Every member of that team is then required to have 2FA enabled on their own account; without it, every dashboard request redirects them to set it up.
The toggle applies per team, so a strict policy on one team doesn't cascade into another team the same user might also belong to.
API keys are team-scoped
An API key authorises against one specific team. Switching teams in the UI doesn't change which team your API key authorises — you'd create a separate key per team if you need both. The key's scope (Account / Project / App) further narrows what it can touch within that team.
Switching the active team
Click the team name in the sidebar to open the team picker. The active team is persisted on your user — sign out / sign in keeps the same active team.
Switching teams resets your active-project selection, so you don't accidentally hit a project that belongs to the other team.