# 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](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Celigo 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](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) 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 Celigo 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 access-record ID in the current account or environment |
| userId | Underlying user ID |
| email | Email address of the user, used for identity correlation |
| name | Display name of the user, when returned |
| createdAt | Date and time when this access record was created |
| lastModified | Date and time when this access record was last changed |
| userLastSignIn | Most recent sign-in of the user across accounts, when returned |
| lastSignIn | Last sign-in to the user account, when returned |
| accountSSOLinked | SSO linkage state of the user for the account |
| allowedToResetMFA | Indicates whether the caller can reset MFA for the user |
| createdVia | Method used to create the access record |
| userType | Access-record type |
| accessLevel | Account-wide role, may be absent when access is limited to specific integrations |
| integrationIds | IDs of integrations with explicit access entries |
| integrationRoles | Positional Monitor or Manage roles that correspond to integrationIds |
| accountMFARequired | Indicates whether MFA is required in this account |
| accountSSORequired | Indicates whether SSO is required in this account |
| allowToEditRetryData | Indicates whether Monitor-level retry payloads may be edited |
| mcpServerIds | MCP server IDs with explicit access entries |
| allMcpServerAccess | Indicates whether the user has access to all MCP servers in the account |
| isProductionAdmin | Indicates whether the user has production-admin privileges in the account |