Garba provides a flexible user management system based on teams, roles, and meeting access policies. This guide explains how users are assigned to teams, their roles, and their access to meetings.
Every user in Garba belongs to a team.
If a team is not specified during user creation, the user is automatically assigned to the General team.
The General team is a default system team and cannot be edited or removed.
Each team follows one of the following meeting access policies, which determine how users can access meetings:
Own team only – Users can only access meetings within their own team.
Own and specified teams – Users can access meetings within their team and any additional teams they have explicit access to.
All teams – Users can access meetings across all teams.
Own meetings only – Users can only access meetings they have created.
Garba offers three user roles, each with different permissions:
✅ Full access to all teams and meetings.
✅ Can create and manage Summary Templates.
✅ Can set up Playbooks.
✅ Can view and edit everything in the system.
✅ Can manage meetings created by users within their own team.
✅ Can manage their own team’s settings and members.
✅ Meeting access is determined by their team’s meeting access policy.
✅ Can only edit meetings they have created themselves.
By structuring your users, teams, and meeting access properly, you can ensure a seamless and controlled meeting experience in Garba.
If you have any questions, feel free to reach out to our support team! 😊
