> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/user-management/single-sign-on-sso-for-authentication-to-snyk/custom-mapping/examples-setting-up-custom-mapping-for-idps/example-setting-up-custom-mapping-for-onelogin.md).

# Example: setting up custom mapping for OneLogin

Example of configuring Snyk user roles after setting up OneLogin SSO

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Example: setting up custom mapping for OneLogin

This example shows how to configure user roles after you have [configured OneLogin SSO for Snyk](/platform-administration/user-management/single-sign-on-sso-for-authentication-to-snyk/set-up-snyk-single-sign-on-sso.md).

You need permissions in OneLogin to create roles and edit application parameters, and a Snyk contact who can turn on custom mapping for your Group. Self-serve SSO does not accommodate custom mapping, so any step on the Snyk side must be performed by your Snyk contact. See [Custom mapping](/platform-administration/user-management/single-sign-on-sso-for-authentication-to-snyk/custom-mapping.md) for the requirements and the role assertion format.

OneLogin has the concept of groups and roles. However, OneLogin does not support the assignment of multiple groups to a user.

Therefore, roles will be assigned to users directly instead of indirectly through groups.

1. In OneLogin, go to the **Users** and then to the **Roles** section and create the roles following the naming convention outlined for [custom mapping](/platform-administration/user-management/single-sign-on-sso-for-authentication-to-snyk/custom-mapping.md). Each role should have the Snyk SAML app enabled as the role app.\
   Assign the users to their roles as needed.

<figure><img src="https://1005789498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgtgtomLQ2TUgSKOMSAm%2Fuploads%2Fgit-blob-8c660bfa4dbd1b4808111bfab2a46d1893713e2d%2Fimage%20(156).png?alt=media" alt="OneLogin Roles section"><figcaption><p>OneLogin Roles section</p></figcaption></figure>

2. To transfer the user roles in the SAML assertion to Snyk, go to **Applications**, select the Snyk SAML app, and select the **Parameters** section on the left.
3. Create a **new parameter** named **roles**, with both checkboxes **Include in SAML assertion** and **Multi-value parameter** checked. **Save.**\\
4. On the next screen, select **User Roles** as the **default value** and **Semicolon Delimited Output (Multi-value output).**\
   Ensure that the checkbox **Include in SAML assertion** is checked. **Save**.

Custom mapping is not active until Snyk turns it on for your Group. After Snyk confirms it is active, the mapping works when a user assigned to a Snyk role in OneLogin logs in and receives that role in Snyk.


---

# 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.snyk.io/platform-administration/user-management/single-sign-on-sso-for-authentication-to-snyk/custom-mapping/examples-setting-up-custom-mapping-for-idps/example-setting-up-custom-mapping-for-onelogin.md?ask=<question>&goal=<user_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.
