> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/readme/for-circle-stewards/section-5.-stewarding-a-circle/volunteer-roles.md). # Volunteer roles ### **Volunteer Roles & Responsibilities** Volunteers power every Circle. Clear, shared roles build trust, momentum, and shared ownership. #### **1. Circle Steward** * Facilitate meetups, introduce Logos, and help guide the group toward action. * Create space for others to contribute, grow, and take ownership over time. * Project manage the delivery of winnable issues #### **2. Communications Steward** * Promote the monthly Circle meetups * Post Logos Forum updates with meeting notes and progress updates for the winnable issue. * Help develop key messaging to promote what your Circle is working on and inspire others to join you. #### **3. Community Steward** * Connect with aligned communities and local channels to help grow the Circle. * Welcome new members and help them plug in. * Moderate the Circle community channel. #### **4. Impact Steward** * Take on a piece of real-world action, whether that’s outreach, research, building tools, or hosting events. * Volunteers on winnable issues may not be part of the local Circle; they may be able to contribute remotely. #### **5. Technical Steward** * Develop tools, contribute code and documentation * Provide expertise in onboarding more technical contributors * Provide the link with Logos CCs to support solutions on the Logos stack. --- # 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://circles.logos.co/readme/for-circle-stewards/section-5.-stewarding-a-circle/volunteer-roles.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.