Skip to main content

Custom Attribute Sync from Tenant to Building

Learn how to enable and manage custom attribute value syncing from the tenant portal to the building portal.

Hiral Dave avatar
Written by Hiral Dave
Updated over a month ago

This article explains how the Custom Attributes can be synced from the Tenant Portal to the Building Portal, the prerequisites for enabling sync, and how the sync behaves once enabled.

Overview

Custom Attribute Sync allows tenant-level custom attribute values to be automatically updated in the corresponding building portal, ensuring consistency across portals.


Enabling Custom Attribute Sync

1. During Tenant Creation

  • While creating a tenant in the Building Portal, admins will see an option to enable "Sync Custom Attribute" Sync

  • Default state: Disabled

  • To enable syncing, the admin must manually check this checkbox.

If this option is not enabled during tenant creation or from Tenant Profile, custom attribute values will not sync to the building portal by default.

2. From the Tenant Portal

  • Navigate to User Management → Attributes → Custom Attributes.

  • You will see a column named Sync with Building.

  • Each custom attribute has a toggle in this column.

  • Default state: Toggle OFF

To enable syncing for a specific attribute:

  1. Turn ON the Sync with Building toggle.

  2. The system will validate the attribute name and data type against the building portal.


Attribute Validation Rules

Attributes must be created manually in both portals.
The system does not auto-create custom attributes in the building portal. Attribute name, data type, and options must match to sync the values.

When the Sync with Building toggle is enabled, the system checks the following:

  1. Attribute Name

  • The attribute name must exist in the building portal.

  • Attribute name matching is case-insensitive.

    • Example: Department, department, and DEPARTMENT are considered a match.

Renaming may break the sync.
If a custom attribute name is changed after sync is enabled, updates will no longer sync—even if a space is added/removed from the name.

2. Attribute Data Type

  • The data type of the attribute must exactly match between the tenant and building portals.

    • Example: Text, Date Picker, Dropdown, Checkbox, Boolean (Yes/No)

If either the name or data type does not match, the attribute values will not sync.


Sync Behavior

Enabling sync does not update existing values. Only values updated after sync is enabled will be updated in the building portal.

  • Enabling Custom Attributes Sync in Building Portal for a Tenant and the Sync with Building toggle in Tenant Portal does not trigger a backfill of the existing values.

  • Only attribute values updated after both settings are enabled will be synced to the building portal.


Special Considerations for Dropdown and Checkbox Attributes

For Dropdown and Checkbox custom attributes:

  • The available options must exist in both tenant and building portals.

  • Option values are case-sensitive.

    • Example: HRhr

  • Only values that exactly match (including case) between both portals will be synced.

If a value does not match exactly, it will be ignored and will not be updated in the building portal.


Summary of Rules

Rule

Behavior

Tenant creation checkbox

Disabled by default; must be enabled manually

Sync with Building toggle

Disabled by default per attribute

Attribute creation

Must be manually created in both portals with exact match

Attribute name match

Case-insensitive

Attribute data type

Must match exactly

Dropdown/Checkbox options

Case-sensitive

Tenant attribute deletion

Does not impact already-synced values in building portal


Best Practices

  • Ensure custom attributes are created consistently in both tenant and building portals before enabling sync.

  • Double-check data types and option values for dropdown and checkbox attributes.

  • Enable sync before performing large-scale updates to attribute values.


If you have questions or encounter issues with Custom Attribute Sync, please contact your system administrator or Genea Support.

Did this answer your question?