---
title: Identifying inbound provisioning group attributes for LDAP
description: You must identify the datastore attributes you want to provision when writing group information to the datastore.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:help_userprovisioningattributeswritegroupsstate
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/help_userprovisioningattributeswritegroupsstate.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 5, 2022
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Identifying inbound provisioning group attributes for LDAP

You must identify the datastore attributes you want to provision when writing group information to the datastore.

## About this task

You can identify these attributes on the **Attributes** tab.

![Screen capture of the Attributes tab.](_images/xom1564003536976.jpg)

|   |                                                                                                                                                                        |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | This tab only appears if you are configuring an LDAP user store for provisioning and the **User and Group Support** option is selected on the **Connection Type** tab. |

PingFederate internally manages several attributes that do not require mapping:

* `objectClass`

* `objectGUID`

* `member`

You can override the internal management of `objectClass` by selecting and mapping it to a System for Cross-domain Identity Management (SCIM) attribute on the **Attribute Fulfillment** tab. In this case, the values you supply are used. The `objectGUID` and member attributes cannot be overridden and are ignored if selected.

## Steps

1. Select a root object class and an attribute from the lists, and then click **Add Attribute**.

2. Repeat the previous step for each attribute requiring provisioning.
