When setting up Directory Sync with Kadence, attribute mapping controls how users, groups, teams, and profile photos are provisioned from your directory into Kadence.

This guide covers:

Required attribute mappings for users and groups
Syncing custom teams using the kadence_teams attribute

All mappings are managed through Entra ID and WorkOS, which Kadence uses to provision directory data.

Prerequisites

You must be a Global Admin in Kadence
You must have an Entra ID (Azure AD) directory sync enabled with Kadence

Attribute Mapping Basics (Users and Groups)

During directory sync setup, you will be prompted to configure attribute mappings.

The default mappings created by Azure can be used as long as:

objectId is mapped to externalId

This ensures Kadence can correctly identify and manage users and groups over time.

Syncing Custom Teams from Your Directory

Why use custom team mapping?

Directory groups are often too broad. Custom team mapping allows you to:

Represent real business teams accurately in Kadence
Automatically manage joiners, movers, and leavers
Produce more meaningful analytics and reporting by team

How it works

Kadence uses one or more kadence_teams custom attributes to map team names from your directory to users.

These values are synced to Kadence and used to automatically create and manage dynamic teams.

Configure Entra ID

Go to Enterprise Applications
Select your Kadence SCIM application
Navigate to Provisioning → Mappings
Add a new attribute for kadence_teams
Choose one of the following:
- Direct mapping from an existing field (for example, department)
- Expression mapping (if combining multiple fields)
Click Save to trigger a sync

Custom attributes in Entra ID cannot be used inside expressions due to an Entra limitation.

Configure WorkOS

For new customers

Follow Step 4 in the Entra ID directory sync setup guide
Map directory fields to the available kadence_teams attributes

For existing customers

Navigate to Settings → Integrations in Kadence
Click the kebab menu next to your directory sync integration
Select View Directory Sync
Edit or add the kadence_teams mappings manually

Changes may take up to 24 hours to reflect in Kadence.

Tips for using `kadence_teams`

Multiple teams per user

You can assign users to multiple teams in one of two ways:

Map multiple attributes (kadence_teams_1, kadence_teams_2, kadence_teams_3, etc.)
Use a semicolon-separated list in a single field
Example: Marketing;Belfast;APAC

Each value will be parsed and created as a separate team in Kadence.