# 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 Domo 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 Domo 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 |
| --- | --- |
| title | Job title of the user |
| email | Primary email address of the user |
| alternateEmail | Alternate email for the user |
| role | Role assigned to the user in Domo (for example, Editor) |
| phone | Contact number of the user |
| name | Full name of the user |
| roleId | ID associated with the user's role |
| employeeNumber | Employee number as assigned within Domo |
| createdAt | Timestamp when the user account was created |
| updatedAt | Timestamp when the user account was last updated |

## 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](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) 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 Domo 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 |
| --- | --- |
| id | Unique identifier of the group (role) in Domo |
| name | Name of the role or group |
| description | Description of the group's access and permissions |
| userCount | Number of users assigned to the role |
| authorities | List of permissions or capabilities assigned to the role |
| authorities\[\].title | Title of the authority (e.g., "Use Alerts", "Create API OAuth Clients") |
| authorities\[\].description | Description of what the authority allows |
| authorities\[\].userCount | Number of users assigned to that authority |
| authorities\[\].roleIds | List of role IDs that have the authority |
| authorities\[\].dependsOnAuthorities | Dependencies required for this authority to function correctly |