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 Scrive 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(User) |
Default Account Attributes
The Scrive 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 |
|---|---|
| id | Unique identifier for the user |
| firstName | First name of the user (fstname in the API) |
| lastName | Last name of the user (sndname in the API) |
| Email address of the user, used for correlation | |
| role | Role of the user within the account, used as entitlement value |
| sysauth | Indicates how the user signs in |
| companyadmin | Boolean true/false, indicates whether the user is a company admin |
| status | Status of the user account |
| home_folder_id | Identifier of the user's home folder |
| twofactor_active | Boolean true/false, indicates whether two-factor authentication is enabled |
| twofactor_is_mandatory | Boolean true/false, indicates whether two-factor authentication is mandatory |
| personalnumber | Personal number of the user |
| phone | Phone number of the user |
| companyposition | Job title/position of the user |
| lang | Language of the user account |
| tos_accepted_time | Timestamp when the user accepted the terms of service |
| webauthn_active | Boolean true/false, indicates whether WebAuthn is enabled |
| external_id | External identifier for the user |
| internaltags | Internal tags associated with the user |
| externaltags | External tags associated with the user |
| chargebee_customer | Chargebee customer identifier, if present |
| provisioned | Boolean true/false, indicates whether the user is provisioned |