# 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 Cobot 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 Cobot 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 identifier of the membership account |
| name | Full name of member |
| email | Email address of the member |
| phone | Phone number of member |
| company | Company associated with the member |
| confirmedAt | Membership confirmation date |
| canceledAt | Membership cancellation date, if any |
| photo | URL of the members profile photo |
| space\_id | Identifier of the space associated with the membership |
| team\_id | Identifier of the team assigned to the member |

> [!NOTE]
>
> `team_id` is of type team and is flagged as an Entitlement attribute - it links each account to the Team entitlement schema below.

## 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 Team Attributes

| Attribute Name | Description |
| --- | --- |
| team\_id | Unique identifier of the team |
| team\_name | Team name |
| customerNumber | Customer number associated with the team |
| billingCompany | Company name in the billing address |
| billingEmails | Billing email address of the team |
| space\_id | Identifier of the space associated with the team |

> [!NOTE]
>
> Cobot teams are flat - a space can have multiple teams, but teams do not nest inside one another. Each team is exposed directly as an entitlement.