Custom fields relationships
2024-01-12Last updated
Use the following custom fields information to understand the relationship between Genetec ClearID™ identity field names and Security Center entity type fields.
Cardholder fields
Cardholder fields are used to synchronize cardholder information with an identity in ClearID.| Field name | Data type | Default value | Group name (And Priority) |
|---|---|---|---|
| Company | Text | ClearID (1) | |
| Department | Text | ClearID (1) | |
| Employee Number | Text | ClearID (1) | |
| External ID | Text | ClearID (1) | |
| Home Site | Text | ClearID (1) | |
| Identity ID | Text | ClearID (1) | |
| Identity Management Status | ClearIdManagementStateCustomType | Unreconciled | ClearID (1) |
| Job Title | Text | ClearID (1) | |
| Middle Name | Text | ClearID (1) | |
| Phone Number | Text | ClearID (1) | |
| Secondary Email | Text | ClearID (1) | |
| Supervisor | Text | ClearID (1) | |
| Worker Type Code | Text | ClearID (1) | |
| Worker Type Description | Text | ClearID (1) |
Cardholder group fields
Cardholder group fields are used to synchronize cardholder group information with a role in ClearID.- The Team ID represents the role ID in ClearID.
- The Team Management Status indicates whether ClearID is managing cardholders and credentials or not (managed by ClearID, not managed by ClearID, deleted by ClearID, or unreconciled).
| Field name | Data type | Default value | Group name (And Priority) |
|---|---|---|---|
| Team ID | Text | ClearID (1) | |
| Team Management Status | ClearIdManagementStateCustomType | Unreconciled | ClearID (1) |
Credential fields
Credential fields are used by ClearID to keep the credentials up to date.| Field name | Data type | Default value | Group name (And Priority) |
|---|---|---|---|
| Credential Cloud Etag | Text | ClearID (1) | |
| Credential Type | ClearIdCredentialTypeCustomType | Unknown | ClearID (1) |
Visitor fields
These visitor fields are used to synchronize visitor information.| Field name | Data type | Default value | Group name (And Priority) |
|---|---|---|---|
| Company Name | Text | ClearID (1) | |
| Expected Arrival | Date and time | 12/31/2099 7:00:00 PM | ClearID (1) |
| Expected Departure | Date and time | 12/31/2099 7:00:00 PM | ClearID (1) |
| Export Control | Text | ClearID (1) | |
| Host Phone Number | Text | ||
| Meetup Location | Text | ClearID (1) | |
| Non Disclosure Agreement | Text | ClearID (1) | |
| Notes | Text | ClearID (1) | |
| Parking Location | Text | ClearID (1) | |
| Registration Code | Text | ClearID (1) | |
| Site ID | Text | ClearID (1) | |
| Site Name | Text | ClearID (1) | |
| Visit Event Name | Text | ClearID (1) | |
| Visit Reason | Text | ClearID (1) | |
| Visitor ID | Text | ClearID (1) | |
| Watchlist Status | Text | ClearID (1) |
Custom data types
Custom data types are used for some custom fields to define the accepted values associated with the data types.
Note: All custom fields are labels used to define a property
associated with a Security Center entity type that might be useful to an organization. The
fields included in the description here are merely descriptive labels. All the custom data
types might not be applicable to or used by ClearID.
| Data type | Values |
|---|---|
| ClearIdManagementStateCustomType | Managed by ClearID, Unreconciled, Not managed by ClearID, Deleted by ClearID |
| ClearIdCredentialTypeCustomType | Unknown, Permanent Badge, Biometric Credential, Temporary Badge, Visitor Badge, Mobile Credential, License Plate Credential, Pin Credential, Toll Tag, QR Code |