Teams docs

When to use teams

Use teams when more than one group owns webhook traffic in the same workspace. Teams help route operational access by source and keep everyday work focused.

• Create a team for a product area such as Billing, Fulfillment, Platform, or Integrations.
• Add members who operate that area.
• Assign sources to the team so members see the feeds they are responsible for.
• Use audit history to review important workspace changes.

Workspace members

Members sign in with GitHub before they can manage sources, destinations, alerts, Dispatch apps, API keys, billing, or team settings.

• Invite teammates from the team settings page.
• Remove members when they no longer need access.
• Use API keys for backend services instead of adding service accounts as people.
• Use portal sessions for your customers instead of inviting them into your workspace.

Team-scoped work

Team scoping keeps source lists, incident work, and ownership cleaner as the number of feeds grows.

• Assign production sources to the team that owns the receiving system.
• Keep test feeds and development feeds separate from production ownership when possible.
• Name teams and sources the way your incident process names them.
• Review team source assignments when a product area changes ownership.

Recommended setup

1. Create teams for the groups that actually respond to webhook issues.
2. Add members before handing off alert ownership.
3. Assign sources to the right team.
4. Create alert channels that match the same ownership model.
5. Review audit history after changing membership, source settings, destinations, API keys, or replay controls.

Access hygiene

• Remove people promptly when they leave a team or company.
• Rotate API keys when a backend service changes ownership.
• Keep customer endpoint management in the hosted portal, not the workspace dashboard.
• Prefer team-owned alert channels over personal destinations for production issues.