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 8x8 XCaaS 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 |
|---|---|
| userId | Account |
Default Account Attributes
The 8x8 XCaaS 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 |
|---|---|
| userId | Unique identifier for the user account |
| orgUserId | Organization-specific username used to identify the user within the org |
| firstName | First name of the user |
| lastName | Last name of the user |
| userStatus | Current state of the account (ACTIVE, INACTIVE, SUSPENDED, PENDING) |
| userType | Classifies the user's role within the platform (CONSUMER, MERCHANT) |
| primary | Boolean flag indicating whether this is the primary account holder within the organization |
| createdAt | Unix timestamp recording when the account was created |
| kyc | Indicates whether the user has completed KYC verification (true = verified, false = not verified) |
| tnc | Indicates whether the user has accepted the terms and conditions (true = accepted, false = not accepted) |
| permissions.MANAGE_USERS | Controls ability to create, edit, or deactivate user accounts |
| permissions.RISK_CONTROL | Controls access to risk management settings and controls |
| permissions.REPORTS_AND_SETTLEMENT | Controls access to financial reports and settlement data |
| permissions.CONSUMER_ACCOUNTS | Controls ability to view or manage consumer account records |
| permissions.PROOF_OF_RESERVES | Controls access to proof-of-reserves documentation and audits |
| permissions.AUDIT_LOGS | Controls ability to view system audit logs and activity history |
| permissions.APIS | Controls ability to generate or manage API keys and integrations |
| permissions.BUSINESS_MONITORING | Controls access to business performance dashboards and monitoring tools |
| permissions.FUND_MANAGEMENT | Controls ability to initiate or manage fund transfers and balances |
| permissions.KNOW_YOUR_TRANSACTION | Controls access to transaction monitoring and KYT compliance tools |