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 FreeAgent 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
url Account(User)

Default Account Attributes

The FreeAgent 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
url Unique identifier (API URL) for the user within FreeAgent
first_name First name of the user
last_name Last name of the user
email Email address of the user
hidden Stores boolean true or false, whether the user account is hidden (for example, deactivated)
role Role of the user within the FreeAgent account (for example, Owner, Director, Employee), used as an entitlement value
permission_level Numeric permission level assigned to the user, indicating the scope of access
opening_mileage Opening mileage value recorded for the user, used for mileage expense tracking
created_at Timestamp indicating when the user record was created
updated_at Timestamp indicating when the user record was last updated

Note

User role is modeled as an account entitlement on the role attribute. A separate entitlement schema is not used.