# Members Expand your Avo team and manage your members access by opening the workspace settings modal from the settings wheel located next to your workspace name: ![Accessing workspace settings](https://www.avo.app/docs/images/workspace/members/accessMembers.png) ## Roles Admins can assign roles when inviting new users as well as for existing users, excluding yourself. Role overview: | | [Billing](https://www.avo.app/docs/workspace-management/members.md#billing-only) | [Viewer](https://www.avo.app/docs/workspace-management/members.md#viewer) | [Editor](https://www.avo.app/docs/workspace-management/members.md#editor) | [Admin](https://www.avo.app/docs/workspace-management/members.md#admin) | |----------------------------------------|---------|--------|--------|-------| | View tracking plan | | ✅ | ✅ | ✅ | | Pull generated code using the Avo CLI | | ✅* | ✅ | ✅ | | Comment | | ✅ | ✅ | ✅ | | Create branches and edit tracking plan | | | ✅ | ✅ | | Change branch status | | | ✅ | ✅ | | Edit tracking plan rules | | | ✅ | ✅ | | View members | | | ✅ | ✅ | | View workspace settings | | | ✅ | ✅ | | View service accounts | | | ✅ | ✅ | | Manage and invite members | | | | ✅ | | Manage workspace settings | | | | ✅ | | Manage stakeholder teams | | | | ✅ | | Manage governance (custom fields and PII types)\*\* | | | | ✅ | | Manage service accounts | | | | ✅ | | View and manage billing | ✅ | | | ✅ | > 💡 \* Viewers can pull code using the CLI on the team and enterprise plans by activating a monthly active implementer seat. On the free plan, only admins and editors can pull code. [See details below](https://www.avo.app/docs/workspace-management/members.md#implementer-access-for-viewers). > > \*\* Managing [Governance](https://www.avo.app/docs/data-design/avo-tracking-plan/governance.md) custom fields and PII types is available on the Enterprise plan only. ### Admin Members with the _Admin_ role can change your workspace name, publish integrations, edit other members roles, invite new members and manage service accounts. Admins can access the Audit Log, Billing page and all workspace settings. If the _protected main branch_ config is active, Admins can override merging a branch without approval. On the Enterprise plan, only Admins can manage [Governance](https://www.avo.app/docs/data-design/avo-tracking-plan/governance.md) custom fields and PII types — all other roles see the Governance page read-only. ### Editor Members with the _Editor_ role can: - Make changes to your workspace like adding events and properties, changing property values and opening new branches. - Pull code generated Avo Codegen using the Avo CLI. - View other members but can not change their roles or add new ones. - View service accounts but can not delete them or add new ones. - Edit the [tracking plan audit rules](https://www.avo.app/docs/audit/rules.md). - _Not_ change your workspace name. On the Team and Enterprise plans you can limit editor edits to just branches, requiring peer approval before the changes are merged to main: ![The protected main branch toggle](https://www.avo.app/docs/images/workspace/members/protectedMainBranch.png) ### Viewer Members with the _Viewer_ role can access your workspace and comment, but cannot make any modifications and cannot access workspace settings including the members and settings modal, audit log or billing page. On the team and enterprise plans, viewers can activate a monthly active implementer seat to pull Avo Codegen with the Avo CLI and use the Inspector Debugger (not available on free). Assign the _Viewer_ role to a member when you want to allow them to view your tracking plan but don't want them to be able to make changes. All new plans can add an unlimited amount of _Viewer_ users. ### Billing Only Members with a _Billing Only_ role can only access the Billing page of the workspace. They can update payment methods and sign up for new subscriptions. Billing users are free of charge. ### Implementer access for Viewers Editors and Admins have full implementer access (including pulling code with the CLI and using the Inspector Debugger) on all plans: free, team and enterprise. Viewers on the team and enterprise plans can also get implementer access by activating a monthly active implementer seat. Each viewer who needs to pull code or use the Inspector Debugger must have an active implementer seat, which is charged per monthly active viewer using these features. See the [pricing page](https://www.avo.app/pricing) for more details. Implementer access is not a role that can be assigned to members on invite. Viewers activate their implementer seat when they first use an implementer feature each month. Learn more about [codegen and its benefits](https://www.avo.app/docs/implementation/avo-codegen-overview.md). ### Legacy Roles #### View Only (Legacy) Members with the _View Only_ role can access your workspace but cannot make any modifications and can not access workspace settings including the members and settings modal, audit log or billing page. Additionally, _View Only_ users don't have access to pull Avo Codegen with the Avo CLI. Assign the _View Only_ role to a member when you want to allow them to view your tracking plan but don't want them to be able to make changes. All new plans can add an unlimited amount of _View Only_ users. #### Comment Only (Legacy) Members with a _Comment Only_ role have the same limitations as the _View Only_ role but can comment on events, properties, branches and more. The _Comment Only_ role is available on plans with extended collaboration, [see more](https://www.avo.app/pricing). ## What's next? Now when you when you have your team in Avo it's time to [learn how to collaborate](https://www.avo.app/docs/data-design/collaboration.md).