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 Dropbox 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 Attributes
The Dropbox 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 |
|---|---|
| team_member_id | The team member's unique identifier |
| status | Status of the member, whether active or inactive |
| surname | The team member's surname |
| given_name | The team member's first name |
| The team member's email address | |
| email_verified | Boolean attribute which describes whether an email address is verified to be owned by a specific team member |
| role | Roles on the Dropbox server, it can be administrator or member |
| groups | List of groups connected to team member |
| external_id | The team member's external ID |
| familiar_name | Locale-dependent name. In the US, a person's familiar name is their given name, but elsewhere, it could be any combination of a person's given name and surname. |
| display_name | A name that can be used directly to represent the name of a user's Dropbox account |
| abbreviated_name | An abbreviated form of the person's name. This is their initials in most locales. |
| account_id | A user's Dropbox account identifier |
| joined_on | The date and time the user joined as a member of a specific team |
| persistent_id | Persistent ID that a team can attach to the user. The persistent ID is a unique ID to be used for SAML authentication. |
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 Dropbox 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 |
|---|---|
| group_id | The group's unique identifier |
| group_external_id | This is an arbitrary ID that an admin can attach to a group |
| group_name | Name of the group |
| member_count | Total count of the members connected to the group |
| members | List of group members |
| group owners | List of group owners |
| group_management_type | The group type determines how a group is managed. For example, user_managed/company_managed |
Documentation Feedback
Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.