> For the complete documentation index, see [llms.txt](https://docs.fortunaway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortunaway.com/fortuna-id/what-is-fortuna-id/user-identity-and-membership-roles.md). # User Identity & Membership Roles Fortuna ID organizes users through identity profiles and membership roles. These roles help the community understand a user’s level of participation, contribution, and trust within the FortunaWay ecosystem. A user may begin as a new participant and gradually move into higher membership roles by completing quests, earning credentials, contributing to the community, and participating in campaigns. Membership roles can be used for: * Community access * Campaign eligibility * Quest permissions * Event participation * Contributor recognition * Ambassador applications * Partner campaign access Example roles may include Observer, Believer, Holder, Contributor, and Ambassador. These roles are not only labels. They are identity states supported by user activity, credentials, and contribution records. This role-based structure helps FortunaWay build a community that rewards meaningful participation rather than short-term attention. --- # 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.fortunaway.com/fortuna-id/what-is-fortuna-id/user-identity-and-membership-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.