Garba provides a flexible user management system based on teams, roles, and access policies. This guide explains how users are assigned to teams, their roles, and their access to meetings and emails.
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 access policies, which determine how users can access meetings and emails:
Own team only – Users can only access meetings and emails within their own team.
Own and specified teams – Users can access meetings and emails within their team and any additional teams they have explicit access to.
All teams – Users can access meetings and emails across all teams.
Own only – Users can only access meetings and emails they own.
Note: Private meetings and emails are only visible to the owner and participants, regardless of access policy. This is controlled by the Default Meeting And Email Privacy setting in User Settings.
Garba offers three user roles, each with different permissions:
✅ Full access to all teams, meetings, and public emails.
✅ Can create and manage Summary Templates.
✅ Can set up Playbooks.
✅ Can view and edit everything in the system.
⚠️ Cannot see private emails — only the email owner and participants can.
✅ Can manage meetings and emails created by users within their own team.
✅ Can manage their own team’s settings and members.
✅ Meeting and email access is determined by their team’s access policy.
✅ Can only edit meetings they have created themselves.
By structuring your users, teams, and access policies properly, you can ensure a seamless and controlled experience in Garba.
If you have any questions, feel free to reach out to our support team! 😊
