> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/account-and-access.md). # Account & access Manage your Argos account, configure how your team signs in, and control who can access which projects. Manage your Argos account, how you sign in, and who on your team can access what. * [Account management](/docs/learn/account-and-access/account-management.md) – Sign up, create projects and teams, and manage login methods and emails * [Analytics](/docs/learn/account-and-access/analytics.md) – Track builds, screenshots, change rate, and approval rate across your projects * [Team members & roles](/docs/learn/account-and-access/team-members-and-roles.md) – Invite members and control their permissions with roles * [Passkeys](/docs/learn/account-and-access/passkeys.md) – Sign in with your fingerprint, face, screen lock, or a hardware security key * [GitHub single sign-on](/docs/learn/account-and-access/github-single-sign-on.md) – Sync your Argos team with a GitHub organization * [SAML single sign-on](/docs/learn/account-and-access/saml-single-sign-on.md) – Enforce single sign-on through your SAML identity provider * [SCIM provisioning](/docs/learn/account-and-access/scim-provisioning.md) – Let your identity provider add, remove and assign roles to team members * [Security and compliance](/docs/learn/account-and-access/security-and-compliance.md) – Data hosting, SOC 2, GDPR and the DPA, data retention, export and deletion --- # 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://argos-ci.com/docs/learn/account-and-access.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.