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 Dato CMS 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 Dato CMS 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 |
|---|---|
| role_id | Role assigned to the user in DatoCMS |
| is_active | Indicates whether the user account is active |
| full_name | Full name of the user |
| last_access | Timestamp when the user account was last accessed |
| id | Unique identifier for the user in DatoCMS |
| type | Resource type identifier in DatoCMS API |
| Email address of the user |
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 Dato CMS 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 |
|---|---|
| role_id | Unique identifier for role |
| is_active | A permission profile assigned to collaborators that determines their access level and actions within a project. |
| can_manage_users | Allows creating, editing, and removing users in the project. |
| can_manage_access_tokens | Allows generating, viewing, and revoking API access tokens. |
| can_manage_sso | Allows configuring and managing Single Sign-On settings. |
| can_manage_environments | Allows creating, deleting, or modifying project environments (e.g., staging, production). |
| can_edit_schema | Allows modifying content models, fields, and overall schema structure. |
| can_edit_site | Allows changing general project/site settings and configurations. |
| environments_access | Defines which environments (primary, all, etc.) the role can access. |
| can_promote_environments | Allows promoting changes from one environment to another (e.g., staging → production). |
| can_manage_webhooks | Allows creating and managing webhooks for event notifications. |
| can_manage_build_triggers | Allows configuring and managing build trigger events. |
| can_manage_search_indexes | Allows creating and managing search index configurations.ws creating and managing search index configurations. |
| can_manage_shared_filters | Allows creating and editing shared content filters. |
| can_manage_upload_collections | Allows managing media/upload collections and folders. |
| can_manage_menu | Allows customizing the CMS navigation/menu structure. |
| can_manage_workflows | Allows creating and managing editorial workflows and statuses. |
| can_access_audit_log | Allows viewing audit logs of system activities and changes. |
| can_access_build_events_log | Allows viewing logs related to build events. |
| can_access_search_index_events_log | Allows viewing logs for search indexing events. |
| can_perform_site_search | Allows using the internal site search functionality. |