Schema Reference
The application schema is used to configure the objects returned from a connector.
Note
-
The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.
-
The schema attributes that are not present by default must be defined as strings if not specified.
The EZOfficeInventory connector uses the following default correlation and object configurations.
Default Account Schema
Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.
The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.
Default Account ID
SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.
Caution
Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
To resolve issues caused by changing account IDs, reconfigure them to their default values.
The following table lists the default account IDs for this connector:
| Account ID | Schema Object Type |
|---|---|
| id | Account |
Default Account Attributes
The EZOfficeInventory connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
| Attribute Name | Description |
|---|---|
| id | Unique numeric identifier assigned to the user record |
| User's email address, used for login and notifications | |
| first_name | User's given (first) name |
| last_name | User's family (last) name |
| full_name | User's complete name (first and last combined) |
| status | Indicates whether the user account is currently active or inactive |
| confirmed_at | Timestamp when the user confirmed/verified their account (for example, via email confirmation) |
| is_ldap_user | Boolean flag indicating whether the user authenticates via LDAP |
| saml_user | Boolean flag indicating whether the user authenticates via SAML-based SSO |
| auto_sync_with_ldap | Boolean flag indicating whether the user's account is automatically kept in sync with the LDAP directory |
| otp_required_for_login | Boolean flag indicating whether one-time password (OTP)/MFA is required for this user to log in |
| consumed_timestep | Internal counter used to track the last valid OTP time-step, preventing reuse of the same OTP code |
| password_changed_at | Timestamp of the last time the user's password was changed |
| reset_password_sent_at | Timestamp of the last password reset email sent to the user |
| role_id | Numeric identifier of the role assigned to the user, which determines their permissions |
| role_name | Display name of the role assigned to the user (for example, "Admin", "Assigned Role") |
| team_id | Identifier(s) of the team(s) the user belongs to; supports multiple team memberships |
| settings_access | Boolean flag indicating whether the user has permission to access account/company settings |
| manager_id | Identifier of the user's manager, used to reflect reporting hierarchy |
| created_at | Timestamp when the user record was created |
| updated_at | Timestamp of the most recent update made to the user record |
| deleted_at | Timestamp indicating when the user record was soft-deleted, if applicable |
| deactivated_at | Timestamp indicating when the user account was deactivated, if applicable |
| offboarding_date | Date on which the user is scheduled to be or was offboarded from the organization |
| inactive_by_id | Identifier of the user/admin who marked this account as inactive |
| unsubscribed_by_id | Identifier of the user/admin who unsubscribed this account from email notifications |
| created_by_id | Identifier of the user/admin who created this account |
| creation_source | Indicates how the account was created (for example, "manual", SCIM, sync) |
| subscribed_to_emails | Boolean flag indicating whether the user is subscribed to receive system emails/notifications |
| alert_type | Specifies the type/level of alerts the user is configured to receive (for example, "all_alerts") |
Default Entitlement Attributes
Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to Managing Entitlements for more information.
Caution
Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.
Default Group Attributes
The EZOfficeInventory connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.
| Attribute Name | Description |
|---|---|
| name | Display name of the team |
| id | Unique identifier of the team |
Default Role Attributes
The EZOfficeInventory connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.
| Attribute Name | Description |
|---|---|
| name | Display name of the role |
| id | Unique identifier of the role |