Custom attributes are organization-specific user attributes that you can set up and define for your organization. All organizations start with zero custom attributes. You can add custom attributes as needed for your organization, but you can only have up to 15 custom attributes.

Display names for custom attributes

By default custom attributes are named extensionAttribute1, extensionAttribute2, and so on, up to 15, but you can assign display names to those attributes. Display names can have up to 128 characters and can't have the same display names as other custom attributes in the organization or any existing user attributes.

When custom attributes are given display names, those names are used during user onboarding in Control Hub and when mapping extension attributes to tracking codes on Meeting sites. However, when using APIs and CSV files to onboard users, the standard fixed names for custom attributes apply.

Values for custom attributes

User values for custom attributes can be open text, picked from a predefined set of values, or a combination of both. These values can be uploaded in the same part of Control Hub where you add custom attributes for your organization. A custom attribute can have up to 500 predefined values.

Values should be organized in the CSV files in the order that you want them to appear. Only upload values that you want the admin or host to see; all values in the CSV file will be shown. This is different than the file format previously used to upload values for Meeting site tracking codes if you've done that before.

Removing custom attributes

If you need to replace a custom attribute, you can remove them only if no meeting site tracking codes are mapped to that attribute. To remove a custom attribute that's mapped to tracking codes on a meeting site, you need to first unmap that attribute from tracking code maps for all meeting sites that use it.

Removing a custom attribute doesn't delete the data that's associated with that attribute. That means that if you accidentally remove a custom attribute and add it back again, the attribute will have the same previous display name. You may not see the custom attributes in the same sequential order when you remove an attribute.

How are custom attributes used?

Custom attributes can be used in any way you want, but we have a preexisting use of custom attributes for tracking codes on Meeting sites. Previously, each site had its own tracking codes that had to be populated for users on each site. Now, you can map those tracking codes to user profile attributes and custom attributes. This enables tracking codes for meeting sites to be auto-populated from those attributes.

We provide a wizard in Control Hub to help you map tracking codes to custom attributes or other profile attributes. Additionally, all sites can now use the same custom attributes.

Required attributes

When you map a site's tracking codes to custom attributes and profile attributes that are marked as required, those tracking codes inherit the properties of the mapped attributes. That means those tracking codes automatically become required for new users added to the organization. Note that this doesn't affect existing users in the organization who may not have that attribute populated.

If you mark custom attributes as required, then those values must be provided at time of user onboarding to the organization or else user onboarding will fail. Proceed with caution before marking custom attributes as required.

Synchronized attributes only come in to Control Hub from external sources like Directory Connector. Automated user onboarding processes, such as Directory Connector, Azure AD, or SAML, don't support custom attributes. You shouldn't use custom attributes if your organization uses one of those automated processes.

Instead, we recommend that you use synchronized attributes. Synchronized attributes can't be set for users outside your organization; in such organizations, use synchronized attributes rather than required custom attributes.