# User Management Amondo uses roles and permissions to help teams work well together, ensuring clarity, security, and transparency. Access in Amondo operates on two levels. * **Teams**: a user can belong to one or multiple teams. * **Roles**: roles define what a user can see and do within each team. Each role is built on a set of specific permissions, ensuring that every user has access only to what they need in order to do their job effectively. #### Admin Admins have complete control of the platform, managing teams, integrations, and content. This role is ideal for account owners or key decision-makers responsible for setup, access, and governance. #### Social Manager Social Managers focus on integrations. They can create and manage integrations and view information elsewhere without making changes. This role suits those handling social feeds or data connections. #### Editor Editors focus on content. They handle imprints, collections, customisations, and integrations but can't change team settings. This role suits content managers and curators who decide what users see. #### Viewer Viewers have read-only access across the platform. They can see all relevant information but cannot make changes. This role is typically used for stakeholders who need visibility without operational involvement. *** Amondo curators and team members have extra access to help with customer accounts. They use admin permissions when needed but aren't shown as part of customer teams. This means Amondo can support and curate without changing customer team setups. Customers see no difference, their team stays the same. The Amondo dashboard is permission aware. Actions a user can't do are hidden or disabled for clarity. If an action is clickable, the user has the permission to do it. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.amondo.com/platform-guides/admin/user-management.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.