---
title: SCIM Components and Roles
description: SCIM contains three main components, as with a number of the federation protocols, the terminology can be slightly confusing so we describe the components below:
component: developer-resources
page_id: developer-resources:scim_11_developer_guide:scim-components-roles
canonical_url: https://docs.pingidentity.com/developer-resources/scim_11_developer_guide/scim-components-roles.html
revdate: September 30, 2020
page_aliases: ["dev_scim11_overview_components_roles.adoc"]
---

# SCIM Components and Roles

SCIM contains three main components, as with a number of the federation protocols, the terminology can be slightly confusing so we describe the components below:

* **Service Provider** The provider of the identity information (in a traditional enterprise scenario, the SCIM Service Provider is most likely the same as the SAML Identity Provider). For a majority of this guide we will use the PingOne Directory as an example of a SCIM Service Provider.

* **SCIM Consumer** The application or service that will consume the SCIM data. For example in a federated provisioning scenario, the SCIM Consumer will be the 3rd party receiving the identity information.

* **Resource** The object (i.e. a User or a Group) that the SCIM request is being performed on.