> 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-ping-identity.md).

# Example: setting up custom mapping for Ping Identity

Example of configuring Snyk custom mapping of roles for Ping Identity using legacy custom mapping

{% 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 Ping Identity

This page explains how to configure the custom mapping of roles for Ping Identity using [Legacy custom mapping](/platform-administration/user-management/single-sign-on-sso-for-authentication-to-snyk/custom-mapping/legacy-custom-mapping.md).

{% hint style="info" %}
This guide assumes your Ping Identity application is configured and functional.
{% endhint %}

{% hint style="info" %}
Any step on the Snyk side in setting up the Enterprise application must be performed by your Snyk contact, as self-serve SSO does not accommodate custom mapping.
{% endhint %}

1. In your application configuration, select **Attribute mappings** and click the pencil to edit the attributes.

   <figure><img src="https://1005789498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgtgtomLQ2TUgSKOMSAm%2Fuploads%2Fgit-blob-be84ee0fb4db350b687ddfc7d56c77e527fb08cc%2F6%20(4).png?alt=media" alt="Edit mapping attributes"><figcaption><p>Edit mapping attributes</p></figcaption></figure>
2. Select **+Add** and enter the following attribute, then save the change,\
   **roles**: `Group Names`\\

   <figure><img src="https://1005789498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgtgtomLQ2TUgSKOMSAm%2Fuploads%2Fgit-blob-86fb4d7c1ae68c0ecd61b01e11cc82934279286f%2FScreenshot%202023-09-05%20at%2012.02.30%20PM.png?alt=media" alt="Add roles array"><figcaption><p>Add roles array</p></figcaption></figure>
3. In the left menu, select **Identities/Groups** and add the Snyk Groups needed following the syntax explained on the [Custom mapping](/platform-administration/user-management/single-sign-on-sso-for-authentication-to-snyk/custom-mapping.md) page.

   <figure><img src="https://1005789498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIgtgtomLQ2TUgSKOMSAm%2Fuploads%2Fgit-blob-f77c9915cd118185d054dff06c95e9af522fd890%2F12.png?alt=media" alt="Adding an example Group"><figcaption><p>Adding an example Group</p></figcaption></figure>
4. If you do not select a **Population** at the bottom of the previous screen, assign the Group to the users who take part in the role assignment in Snyk. If you select a **Population**, all users in that population inherit the permissions of the assigned Snyk role.
5. To finalize the process, ask your Snyk contact to validate that the SAML payload contains the role array and to turn on the custom mapping feature.

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 in a mapped Ping Identity group logs in and receives the Snyk role named in that group, at the scope and target the assertion names.


---

# 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-ping-identity.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.