> For the complete documentation index, see [llms.txt](https://glow-docs.xrpl-commons.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glow-docs.xrpl-commons.org/technical-resources/user-roles-permissions.md). # User Roles & Permissions The Glow platform uses a robust role-based access control system with five distinct user roles. Each role has specific permissions and responsibilities within the platform ecosystem. ### Admin Role Administrators have full system access and management capabilities. #### Permissions * Create, edit, and delete users of all roles * Manage Waves (create, update, close) * Access all platform data and metrics * Configure system settings * View audit logs * Manage projects and contributors #### Responsibilities * System oversight and maintenance * User management and support * Monitoring program integrity * Managing the Wave lifecycle * Overseeing the disbursement process ### Scout Role Scouts identify and nominate valuable contributions to the XRPL ecosystem. #### Permissions * Create and manage nominations * Create and edit project records * Create and edit contributor profiles * View nomination status and voting metrics * Access personal profile settings #### Responsibilities * Identify impactful projects and contributors * Submit high-quality nominations * Ensure nomination data accuracy * Follow the Glow Code of Conduct #### Nomination Process 1. Search for or create project records 2. Search for or create contributor profiles 3. Create a nomination with detailed contribution description 4. Monitor nomination status through voting and judging phases ### Judge Role Judges evaluate submissions and determine reward allocations. #### Permissions * Review all submissions in assigned Waves * Access voting statistics and community feedback * Create and edit assessments for submissions * Rate contributions according to defined criteria * Approve final distributions #### Responsibilities * Evaluating eligibility of submissions * Reviewing contribution quality and impact * Assigning appropriate shirt sizes (Small, Medium, Large) * Providing feedback on contributions * Participating in final assessment meetings * Approving Wave distributions #### Assessment Criteria Judges evaluate submissions based on: * Eligibility (18+, not in sanctioned regions, etc.) * Whether the contribution falls within an eligible category * Recency of work (within 6 months) * Whether the work was previously funded (through Glow or another program) * Community votes and support * Overall impact on the XRPL ecosystem ### Contributor Role Contributors are developers recognized for their valuable contributions to XRPL projects — whether they submitted their own work directly or were nominated by a Scout. #### Permissions * Submit their own projects directly * Complete eligibility verification * Submit funding applications * Connect XRPL wallet for payments * View application status * Access personal profile settings #### Responsibilities * Confirming eligibility status * Disclosing whether a contribution overlaps with their employment * Accepting terms of service and code of conduct * Providing accurate application information * Connecting a valid XRPL wallet for disbursements * Completing KYC verification when required #### Application Process 1. Submit a project directly, or be nominated by a Scout 2. Review and accept terms of service 3. Review and accept code of conduct 4. Complete eligibility questionnaire 5. Register wallet for fund reception 6. Submit application with additional project details 7. Complete KYC verification ### Voter Role XRPL wallet holders who participate in the community voting process. #### Permissions * Connect XRPL wallet to the platform * Cast votes on submissions * View public submission details and metrics * Monitor voting impact #### Responsibilities * Evaluating submissions objectively * Providing community input on contribution value * Supporting deserving projects through votes #### Voting Process 1. Connect XRPL wallet to the platform 2. Verify wallet ownership through a small transaction 3. Browse and review submissions 4. Cast votes (yay, nay, or null) on submissions 5. Monitor voting impact on submission prioritization ### Role Interactions The Glow platform facilitates seamless interaction between these roles: 1. **Scouts** identify worthy contributions and create nominations 2. **Contributors** can also submit their own projects directly 3. **Voters** provide community input through voting 4. **Judges** evaluate submissions and determine shirt sizes 5. **Contributors** complete applications and receive rewards 6. **Admins** oversee the entire process and manage platform operations Each role plays a vital part in ensuring that valuable contributions to the XRPL ecosystem are properly recognized and rewarded. --- # 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://glow-docs.xrpl-commons.org/technical-resources/user-roles-permissions.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.