Review team roles and remove old access
Keep permissions aligned with the work each person is responsible for.
Access changes when responsibilities change. Review the team list after a role change, a seasonal program or a departure rather than treating account setup as a one-time task. The right question is what the person needs to do now.
The Team list shows people, roles and sign-in information. Use it as the starting point for an access review, then confirm any important change with the person responsible for the workspace.
Match each role to current work.
Open Settings, then Team. Review who manages the organization, who changes templates and who works at the desk. Do not use recent sign-in activity alone to decide that an account is unnecessary; confirm whether the person still has a legitimate operational responsibility.
Make role changes with the owner.
Use the available role control when your account can manage roles. The app protects some actions, including changes to your own role through the list. Ask the owner to handle changes outside your permission rather than exchanging credentials or creating another owner account as a workaround.
Remove access that is no longer needed.
For a departed teammate, choose Remove and read the confirmation. The app explains that the person loses access immediately and must be added back if access is needed again. Finish any required operational handoff before removing the account from the organization.
Try it with a realistic visit.
Review the team after a seasonal program ends. Separate people who are leaving from people staying on in a different role, then confirm the list with the workspace owner. A teammate who no longer runs events may still need reception access, while a former employee should not remain active simply because their account has not been used recently.
Each remaining account should have a clear current purpose and an appropriate role. Confirm that the organization still has responsible owner access before completing changes. Make the review repeatable by assigning a person and a business event, such as the end of a season, to trigger it.
A role control or removal action is missing.
Check your own role and whether the row is your account. Some controls are intentionally unavailable. Ask the owner to review the intended change and keep a clear record of who should retain organizational responsibility.
Does removing a teammate delete signed waivers?
The team action removes the person’s access to the organization. It is not a signed-record deletion workflow. Handle any separate retention or record-management task through the appropriate authorized process.
A quick check before you go.