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 Doppler 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 |
|---|---|
| Identifier | Account |
Default Account Attributes
The Doppler 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 |
|---|---|
| Identifier | Unique UUID of the user in the current workplace, different for different workplace | | Role | Workplace role assigned to the user (for example, owner, admin, collaborator) | | Created at | Timestamp when the user was added to the workplace | | Kind | Member type of the account (for example, user) | | Slug | Slug of the user, same across all workplaces the user is a member | | Email | Email address of the user | | Name | Display name of the user | | Username | Username handle for the user | | MFA Enabled | Indicates whether OTP or security-key MFA is enabled on the account | | Third Party SSO Enabled | Indicated whether the user signs in via third-party SSO (for example, Google or Okta) | | SAML SSO Enabled | Indicated whether the user signs in via workplace SAML SSO |
Note
A user's Slug remains the same across all workplaces the user belongs to, while the Identifier attribute changes for each workplace. Identifier is the account identity attribute because retrieving an individual user from the Doppler API requires the Identifier ($.id), not the Slug.
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.
| Attribute Name | Description |
|---|---|
| Name | Display name of the workplace role (for example, Owner, Admin, Collaborator) |
| Identifier | Unique identifier of the workplace role (for example, owner, admin, collaborator) |
| Created At | Timestamp when the workplace role was created |
| Is Custom Role | True if the role is a custom role created in the workplace; false for built-in roles |
| Is Inline Role | True if permissions were manually selected at assignment time rather than from a named role |
| Permissions | Workplace permission slugs granted by this role (for example, team, logs, billing, settings) |
Note
Doppler provides three built-in workplace roles - Collaborator, Admin, and Owner. Custom workplace roles are available on Team and Enterprise plans. Built-in roles cannot be deleted; custom roles can be created and managed from Team > Roles in the Doppler Dashboard.