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 Mailchimp 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 Mailchimp 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 | ID of the user |
| name | Name of the user |
| firstname | Firstname of the user |
| lastname | Lastname of the user |
| Email address of the user | |
| contact_id | Contact ID of the user |
| email_type | Email type associated |
| status | Status of the user |
| consents_to_one_to_one_messaging | Consents for one to one messaging |
| sms_phone_number | Phone number for SMS |
| sms_subscription_status | SMS subscription Status |
| address | Address of the user |
| city | City of the user |
| phone | Phone Number of the user |
| isVip | Vip boolean flag |
| segments | Segments assigned to user |
| audience_id | Audience ID of the user |
| last_changed | Timestamp of the most recent user update. |
| segment_count | Number of Segments assigned |
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 Segment Attributes
| Attribute Name | Description |
|---|---|
| id | ID of the segment |
| name | Name of the segment |
| member_count | Total number of member in a segment |
| type | Type of the segment |
| created_at | Timestamp at which segment is created |
| created_at | Timestamp at which segment is updated |
| audience_id | Audience ID of the segment |