Teams

Documentation Index

Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt

Use this file to discover all available pages before exploring further.

A team is the boundary that owns every other resource in Cyberun Cloud — agents, models, custom nodes, workflows, tasks, credentials, members, webhooks, container services. Two teams are isolated: an agent connected to Team A cannot pick up Team B’s tasks, and a Team A credential cannot read Team B’s data.

​

What a team holds

​

Roles

Only the owner can promote another member to owner — that happens via Settings → Transfer ownership rather than the role picker. After a transfer, the previous owner becomes an admin.

​

Switching teams

You can belong to many teams. The currently active team is shown in the top-left of Cloud. Click it to switch. The selection affects which team’s resources you see in the dashboard. (Programmatic access uses team-bound credentials, not a session-level setting — see Generate an API key.)

​

When to make a new team

• One team per real-world organization or project boundary.
• Don’t create a team per environment (dev / staging / prod) — use the same team and tag credentials and webhooks by environment instead.
• Don’t create a team per member — Cyberun’s permission model is role-based within a team, not team-per-user.

​

How teams are created

Two paths, depending on how your deployment is configured (see Feature availability for the full list):

• Auto-team — a personal team is created automatically when you register. Most public deployments work this way.
• Self-serve create — a Create team button is visible to any signed-in user.

If neither is available, your team admin creates teams on request — reach out to them.

​

Related

• Credentials — how scoped access works.
• Manage members — invite, change role, transfer ownership.
• Create your first team — the walkthrough.