> For the complete documentation index, see [llms.txt](https://docs.meeds.io/meeds-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meeds.io/meeds-guides/user-guide/administering-a-space/managing-space-roles.md). # Managing Space Roles ### :question: What are my options? Here are the different roles available for spaces * **Admin**: Full control over space settings, customization, apps, members, and content. * **Publisher**: Edit and publish space content such as articles, notes, text blocks, images and links. * **Content Writer:** Creates written posts, articles, and notes for the space. * **Member**: Engages in space activities. In most situations, spaces only need admins and members, but you can promote publishers and content writers if you want to have more advanced control over how content is added to the space. ### :bulb: Good to know * In *Restricted Content Creation* mode, only content writers can add posts, articles, and notes. * That means regular members cannot anymore write contents. * Of course, admins and publishers can still add contents. * If needed, you can remove the content writer role to publishers. * You cannot leave a space where you are the only admin. ### :tools: How to promote or demote users from roles? Go to the space Settings > Roles screen. * Admins, publishers and members are listed. * You can toggle the *Restrict Content Creation* mode in order to activate the content writer role For each role, find listed users. Click to one of them to understand more the role and to manage users: * You can promote members to the role * You can revoke members from the role **Note:** For member list, we suggest you to invite users to join your space from there. :point\_down: More details in the video below {% embed url="" %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.meeds.io/meeds-guides/user-guide/administering-a-space/managing-space-roles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.