Create and Manage Teams

Create operational teams, add or remove members, and keep team ownership aligned with real production boundaries.

Written By 4ALL.LIVE

Last updated 12 days ago

Create operational teams, add or remove members, and keep team ownership aligned with real production boundaries.

Best for: Owners and team/organization administrators.

Before you start

Team count and advanced permission behavior may depend on plan; organization role still applies.

  • Sign in with an individual account in the correct organization.
  • Confirm your role permits the requested change.
  • Record the current state and intended owner before making a production-impacting change.

Steps

  1. Define the boundary. Name the events, members, geography, client, or production unit the team represents.
  2. Create the team. Use a clear unique name and description; avoid duplicating the General team.
  3. Add members. Include only people assigned to the team and verify their organization roles.
  4. Assign team responsibilities. Configure team-level roles/permissions where supported.
  5. Assign events. Create or edit events under the correct team.
  6. Test with a non-admin. Confirm intended event visibility and denied actions.
  7. Maintain membership. Remove people promptly after handoff and review inactive teams before deletion.

What success looks like: The requested change is applied to the intended organization, is visible after refresh, and grants no more access than required.

Check your setup

  • The team represents an understandable boundary, members see intended events, and administrators can explain effective access.

Troubleshooting

Member sees no team events

Check invitation acceptance, organization role, team membership, active team, and event team.

Member sees too much

Review privileged organization role and other team memberships.

Duplicate teams

Choose an authoritative team and migrate deliberately rather than leaving ambiguous access.

Security and operational notes

  • Team names may be visible to operators; avoid sensitive client data when unnecessary.
  • Use least privilege even for temporary production teams.
  • Do not delete a team until event ownership is resolved.