> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/manage-spot/audience/members/members-role.md). # Member's role Spot members can have two different roles: either `Admin` or `Member`. You can then create custom roles (see [here](/english/manage-spot/audience/user-rights.md)). ## Admin `Admins` are the users who manage the Spot. They can do more than `Members`. `Admins` can : * Attend lives * Access collections * Chat in channels * Chat with other members * Create content (live, channel, collection, document) * Manage the Spot through audience management, access to dashboards, tags, groups, etc. ## Member `Members` are the users who will be able to consume the content present on the Spot. They cannot create content. `Members` can : * Attend live shows * Access collections * Chat in channels * Chat with other members ## Change role `Admins` can change the role of other Spot members, whether they are `Admins` or `Members`. To change a member's role : * Access their profile (by clicking on their name in the audience table or on the members page) * Click on the `Edit` button to the right of their role * Select the role you wish to assign {% hint style="info" %} You can change roles in both directions: from `Member` to `Admin` and from `Admin` to `Member`. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.meltingspot.io/english/manage-spot/audience/members/members-role.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.