> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/getting-started/login-redirects.md). # Login Redirects ## General Redirects AttackForge supports login redirects to help your users & customers access the data they need, quickly and efficiently. You can append any of the following redirects to the login URL, which can be shared with customers: * **?redirectTo=sso** * This will automatically redirect the user to sign in with Single-Sign-On (if available) * **?redirectTo=register** * This will automatically redirect the user to registration page (if available) * **?redirectTo=resetPassword** * This will automatically redirect the user to password reset page (if available) * **?redirectTo=/app/…** * This will automatically redirect the user to a page within AFE, after the user has logged in. Examples are provided below for reference: * https\://\/#!/login?redirectTo=sso * Redirect to SSO login * https\://\/#!/login?redirectTo=register * Redirect to registration page * https\://\/#!/login?redirectTo=resetPassword * Redirect to password reset * https\://\/#!/login?redirectTo=/app/projects * Redirect to list of all projects after login * https\://\/#!/login?redirectTo=/app/projects/5bdd20d8128aa82e0040a75d/dashboard * Redirect to Project Dashboard for a specified project, after login * https\://\/#!/login?redirectTo=/app/projects/5bdd20d8128aa82e0040a75d/overview * Redirect to Project Overview for a specified project, after login * https\://\/#!/login?redirectTo=/app/schedule * Redirect to Schedule / Calendar after login ## SSO Preferences If your tenant has more than one single sign-on provider, you can send someone a link that takes them straight to the right one. Add `?sso=1` or `?sso=2` to the login URL, or to any page in AttackForge, and they'll be signed in through that provider and land where the link pointed. Perfect for onboarding a client onto their own identity provider, or pointing a colleague at a finding without the detour. Examples: * https\://\?sso=1 * https\://\/projects/6aacc1455bc5bbfa0a61b47e/home?type=overview\&sso=1 --- # 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://support.attackforge.com/app/getting-started/login-redirects.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.