> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-pages/get-started/learn-more-about-various-team-roles.md). # Learn more about various team roles We believe in teamwork, as well as security. Maker enables you to set specific roles for your team members, allowing you to moderate permissions wherever necessary. Here's a breakdown of the available roles and corresponding permissions: ### Analyst The most basic role with minimal permissions. Ideal for SEO Analysts or anyone requiring read-only permissions. * Access to stories manager * Access to insights in stories manager * Access to in-page insights for each story ### Moderator Great for UGC content moderators. This role has all the permissions of an Analyst plus the ability to: * Approve / Reject UGC stories ### Editor This is the most common role for design and marketing team members. Editors have all the permissions of a Moderator plus the ability to: * Edit any team member's story * Create new collections * Add / remove stories from a collection * See any team member's draft stories * Cross-post to any social network or shop belonging to the team ### Admin This is the most powerful role and the default for account owners. Admins have all the permissions of a Editor plus the ability to: * Invite new members to the team * Delete any collection * Delete any story --- # 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.maker.co/maker-pages/get-started/learn-more-about-various-team-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.