> For the complete documentation index, see [llms.txt](https://docs.voting.works/arlo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voting.works/arlo/user-roles.md). # User Roles Arlo has three types of user roles. Depending on the audit, users may play multiple roles. ### **Audit Administrator** The audit administrator is responsible for setting up the audit, monitoring progress during the file upload and ballot retrieval process, starting additional rounds of auditing, and downloading the final audit results. Audit administrator user credentials are set up by VotingWorks. ### **Jurisdiction Manager** The jurisdiction manager is responsible for uploading all necessary files prior to the audit and coordinating the retrieval of ballots/batches and associated data entry. Jurisdiction manager user credentials are set up by audit administrators as [participants](/arlo/audit-administrator/ballot-manifest/participants.md) in the audit setup process. ### **Audit Board** The audit board is responsible for retrieving ballots and entering their marks into Arlo. Audit board user credentials are set up by jurisdiction managers by [selecting the number of audit boards](/arlo/jurisdiction-manager/audit-conduct-1/audit-conduct.md). ### Tally Entry In batch comparison audits, the audit board may not be designated to enter batch tallies into Arlo. [Tally entry user account(s)](/arlo/jurisdiction-manager/audit-conduct-1/batch-entry-into-arlo.md) can be created as needed to enter batch tallies. The jurisdiction manager may also enter batch tallies. --- # 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.voting.works/arlo/user-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.