[ManuelGerding]

The Teams page explained that experiments belong to a team but said nothing about services or anything else that is team-scoped. This adds a "What Belongs to a Team" section:

• Owned by exactly one team: experiments (incl. runs and schedules, plus sharing with other teams) and services (stay with the team they were created in; owners edit, members work within them).
• Scoped to teams: saved Landscape views, team/wildcard access tokens, and webhooks, preflight webhooks, preflight actions, and Slack notifications (optionally restricted to one team).

Verified against the platform domain model (teamId on Service, Experiment, ExperimentSchedule, LandscapeView, Webhook, PreflightActionIntegration, AccessToken). Experiment suites are left out because they are still behind a feature flag.

Also fixes the Permissions page: "Work within services" said team members ❌, but ServicePermissions.isEditServiceAssociationPermitted allows admins, owners, and members of the service's team to create provided experiments and link/unlink custom ones. A footnote clarifies that which provided experiments exist comes from the service profile, and changing it requires managing the service (admin or team owner).

🤖 Generated with Claude Code