> ## Documentation Index > Fetch the complete documentation index at: https://docs.aciona.me/llms.txt > Use this file to discover all available pages before exploring further. # Team members > Who joins a team, and why that matters for on-call and assignment. Being a member of the **organization** gives someone access to aciona.me. Being a member of a **team** defines which services they answer for. ## Add and remove Owners and admins manage team composition. You can only add someone who is already an active member of the organization — invite them first under [Members](/en/organizations/members). ## Why team composition matters Only team members can be participants in that team's schedule. A **member** can only assign an incident to someone else if both are on the incident's team. Owners and admins are not restricted. When nobody acknowledges an incident, escalation walks the participants of the team's schedule — that is, members of that team. Removing someone from a team does **not** remove them from the schedule automatically. Review the schedule after changing team composition, so you do not leave an invalid participant in the rotation. ## Team services The link between service and team can be made from the team screen or from the services screen — it is the same relationship seen from two sides. A service has one responsible team; a team can answer for many services.