Skip to content

docs: mention that services belong to a team #226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ManuelGerding merged 4 commits into from
Oct 14, 2026
Merged

docs: mention that services belong to a team #226

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d7cdf4e
docs: mention that services belong to a team
ManuelGerding Oct 14, 2026
6780281
docs: list what else is owned by or scoped to a team
ManuelGerding Oct 14, 2026
a239b40
docs: say team members can create provided service experiments
ManuelGerding Oct 14, 2026
a17ff63
fix: let team members work within services in the permissions table
ManuelGerding Oct 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions install-and-configure/manage-teams-and-users/permissions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ The roles in Steadybit are associated with permissions, which cannot be altered.
## Doing Chaos Engineering
| Permission/Role | Admin | Team Owner | Team Member | Shared-with Team Member[^4] | Any Authenticated User |
|-----------------------------------------------------------------------------------------------------------|-------|------------|-------------|------------------------------|------------------------|
| [Work within services](/use-steadybit/services/) | ✅ | ✅ | ❌ | ❌ | ❌ |
| [Work within services](/use-steadybit/services/)[^6] | ✅ | ✅ | ✅ | ❌ | ❌ |
| [Design experiments](/use-steadybit/experiments/design.md) | ✅ | ✅ | ✅ | ❌ | ❌ |
| [Share Experiment](/use-steadybit/experiments/share/share-experiment/) | ✅ | ✅ | ❌ | ❌ | ❌ |
| [Run](/use-steadybit/experiments/run.md), and [schedule experiments](/use-steadybit/experiments/schedule) | ✅ | ✅ | ✅ | ✅ | ❌ |
Expand All @@ -47,4 +47,6 @@ The roles in Steadybit are associated with permissions, which cannot be altered.

[^4]: A member of a team that an experiment has been [shared with](/use-steadybit/experiments/share/share-experiment/)

[^5]: A shared-with team member can edit the properties of a run, but not the properties of the design
[^5]: A shared-with team member can edit the properties of a run, but not the properties of the design

[^6]: Within the services of their team, members can create and run provided experiments, link custom experiments, and validate advice. Which provided experiments a service offers is defined by its [service profile](/install-and-configure/manage-service-profiles/), and changing a service's profile requires [managing the service](/use-steadybit/services/#managing-services)
15 changes: 14 additions & 1 deletion install-and-configure/manage-teams-and-users/teams.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Teams

# Teams

Teams are the grouping element for multiple users. Each team consists of multiple users and has its own permissions for environments and attacks, allowing fine-grained access control for your experiments. Creating teams requires the `admin` permission. A team can also have owners, who manage the team and its members.
Teams are the grouping element for multiple users. Each team consists of multiple users and has its own permissions for environments and attacks, allowing fine-grained access control for your experiments and services. Creating teams requires the `admin` permission. A team can also have owners, who manage the team and its members.

## Default Team: Administrators

Expand All @@ -16,6 +16,19 @@ In the create dialog, you first enter a **name** for the team. The name can be e

You must enter a **key** for the team consisting of one to eight characters. The key cannot be changed after the creation. Each experiment belonging to this team is assigned an identifier with the team key as a prefix.

## What Belongs to a Team

Each experiment and each [service](../../use-steadybit/services/README.md) belongs to exactly one team:

* **Experiments** — including their runs and schedules. Admins and team owners can [share an experiment with other teams](../../use-steadybit/experiments/share/share-experiment/README.md), so that their members can run and schedule it, too.
* **Services** — a service stays with the team it was created in and can't be moved to another team later. Admins and owners of that team can create and edit its services. Team members can create and run the service's provided experiments, link custom experiments, and validate advice.

Other things are scoped to teams as well:

* **Saved views** in the [Landscape](../../use-steadybit/explorer/landscape.md#saved-views) are shared with the members of your team.
* **Team and wildcard [access tokens](../../integrate-with-steadybit/api/api.md#token-types)** grant access to the experiments and operations of their teams.
* **[Webhooks](../../integrate-with-steadybit/webhooks/custom-webhooks.md), [preflight webhooks](../../integrate-with-steadybit/webhooks/preflight-webhooks.md), [preflight actions](../../integrate-with-steadybit/preflightactions/preflight-actions.md), and [Slack notifications](../../integrate-with-steadybit/slack-notifications.md)** can be restricted to a single team. Without a team, they apply to all teams.

## Permissions

In the edit/create dialog, admins can control
Expand Down
Loading