> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/access/cloud/single-sign-on-sso/set-up-google-sso.md). # Set up Google SSO Article to help you setup an Googgle SAML application for use with DecisionRules. **Create custom SAML Application** In the Google admin portal navigate to **Apps** -> **Web and mobile apps** -> **Add app -> Add custom SAML app**. ### App details Once there choose a name for the app and optionally a description and icon. Click on Continue ### Google Identity Provider details In the next step, you will see the SSO URL, Entity ID and Certificate. From these values, save the **SSO URL** and **Certificate** that we will need later. Click Continue. ### Service provider details In the next step, set the necessary information and save it for later. * For the **Entity ID** you can put in any easily identifiable name. * For the **ACS URL** put the address of your server (API) container with "/saml/callback" following. * example: "*"* * For the **Name ID format** choose **EMAIL** * For the **Name ID** choose **Basic Information > Primary email**
Click Continue. ### Attribute mapping Leave as is, no need to set anything up. ### Decision Rules SSO setup {% hint style="info" %} [Here](/doc/access/cloud/single-sign-on-sso.md#how-do-i-set-up-a-single-sign-on-access-for-my-organization) you can find more info how set up SSO in DR application. {% endhint %} * Entry point - **SSO URL** * Issuer - **Entity ID** * Callback Url - **ACS URL** * Certificate - **Certificate** ### Adding Groups In the created custom SAML application click on User Access. * Click on Groups * Search for a group a click on it. * Change **Service status** to **ON.** --- # 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://docs.decisionrules.io/doc/access/cloud/single-sign-on-sso/set-up-google-sso.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.