Skip to content

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 DeployHQ 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 DeployHQ 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 UUID-based unique identifier of the user
first_name The user's first name as recorded
last_name The user's last name as recorded
email_address The user's email address used to sign in and receive notifications
time_zone The user's preferred time zone
id Numeric unique identifier of the user
account_administrator Boolean flag indicating whether the user has full administrator rights
activated Boolean flag indicating whether the user account has been activated
can_manage_users Boolean flag indicating whether the user can add, edit, or remove other users
can_manage_billing Boolean flag indicating whether the user can view and manage billing details
can_create_projects Boolean flag indicating whether the user is allowed to create new projects
can_manage_agents Boolean flag indicating whether the user can manage deployment agents and servers
all_projects_allowed Boolean flag indicating whether the user has access to projects