Custom user metadata

Supply metadata through the Free integration filter, or map LDAP attributes automatically with a paid plan.

sll_user_meta_data works in Free without a license. Integrations can return custom values through this filter. Automatic LDAP-to-user-meta mapping requires an active Pro or Enterprise license.

Supply values through the Free filter

The filter receives an empty array in Free. Your integration supplies the values. With an active paid license, it receives the configured LDAP mapping values first. The filter also runs when a paid license is missing, inactive, or expired; automatic mappings stop in those states. See the filter example and return values.

Automatic LDAP mappings (paid)

With an active Pro or Enterprise license, open User data → Custom user fields. Select Add row. Enter the LDAP attribute and WordPress meta key in separate fields, then select Text or Number. Save the settings. Select Remove row to remove a mapping.

LDAP attributeWordPress meta keyType
telephoneNumberphoneText
departmentdepartmentText
employeeNumberemployee_idNumber

The LDAP attribute is the source. The WordPress meta key is the base name for storage. Select Text to keep text or Number to keep digits only. The number type removes signs, spaces, decimal points, and all other non-digit characters. Use Text if those characters matter.

Only the first value of a directory attribute is copied. Protected WordPress account metadata, such as capabilities, cannot be set through a mapping.

How values are stored

Automatic mappings and the public filter use the same storage rules. With the default suffixes, a phone value creates two user meta keys:

  • phone_ldap contains the last source value from the mapping or filter.
  • phone_wp contains the editable WordPress value.

Your theme or another plugin can read phone_wp with the WordPress user metadata API. The plugin does not add a public staff directory or a profile editor.

Update behavior

When the source value changes, the plugin updates both keys. If it does not change, an edit to the WordPress value is kept. Selected recovery accounts are excluded.

Metadata writes run after a verified directory account is loaded. They can run at password login, server SSO, and scheduled import. A login test does not write user data.

Change the key suffixes

In the paid package, open Advanced → Custom field storage. Change LDAP value suffix or WordPress value suffix only if your integration needs other key names. Defaults are ldap and wp. Free uses the same saved suffixes for the public filter, including suffixes retained from an earlier version. Changing a suffix changes where later values are stored; update the code that reads those keys.

The filter accepts scalar values and rejects protected account keys. Return false to skip metadata writes. It does not add a mapping editor to Free.

Pro custom LDAP field mappings
Map directory attributes to WordPress user metadata. Select the image to see the full size.