Team members & access

Bring your team into Helicarrier and control who can see what. Sharing works per project — there’s no organisation-wide membership to hand out. Each collaborator keeps their own Helicarrier workspace and their own billing, and sees only the projects you’ve shared with them.

Share a project

From Team, generate an invite link:

1. Pick which projects to share. At least one is required — an invite grants project access and nothing else.
2. Optionally pre-fill the invitee’s email, which locks the link to that address.
3. Share the link — it’s valid for 7 days and single-use.

You can revoke an unused invite any time before it’s accepted.

What the invitee gets

Accepting an invite gives them their own workspace. The projects you shared appear in it alongside their own, badged with your account’s name so it’s clear whose they are. Anything they create themselves belongs to — and is billed to — their own account, never yours.

If they already have a Helicarrier account, they can accept while signed in and the shared projects are simply added to what they already see.

Limit someone to certain environments

Sharing a project shares all of its environments by default. To give someone Development without handing over Production, open the project’s row — in the share panel or on their entry under Members — and switch from All environments to Only selected, then pick the ones they should have.

They’ll see only those environments: the environment switcher lists nothing else, the services in the others are invisible, and their canvas opens on an environment they’re allowed in rather than your default. Projects with a single environment don’t offer the choice, since there’s nothing to narrow.

You can change this at any time, and it takes effect immediately. If you later delete the only environment someone was limited to, their access to that project is removed rather than quietly widened to the rest.

Per-project access

As the account owner you can grant or revoke a collaborator’s access to any of your projects at any time, from the Team page. You can’t see or change access they have in anyone else’s workspace, and you can’t reset their password — that account is theirs. The account owner can’t be removed, so you never lock yourself out.

Removing someone

Removing a collaborator revokes their access to every project you’ve shared with them, immediately. Their account, their own projects, and their access to other workspaces are untouched.

Transfer a project to another account

You can hand an entire project — its services and their data volumes — to another account by email. The project’s env groups are re-homed to the destination (copied, with a suffix on any name collision), the services’ data volumes come along untouched, and the move is audit-logged. The new owner takes over; you lose access.

Next

• Give a teammate’s agent scoped access with an API key instead of a login.
• Share configuration across services with environment groups.