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 7shifts 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 | Users |
Default Account Attributes
The 7shifts 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 internal 7shifts identifier |
| identity_id | Links to the identity record for the person |
| company_id | ID of the company this user belongs to |
| first_name | User's official first name |
| last_name | User's official last name |
| preferred_first_name | Optional preferred first name |
| preferred_last_name | Optional preferred last name |
| pronouns | Optional pronouns |
| User's email address | |
| mobile_number | Mobile phone number |
| home_number | Home phone number |
| address | Street address |
| postal_zip | Postal code or ZIP code |
| city | City of user |
| invite_status | Invitation status: accepted, pending, etc. |
| last_login | Last login timestamp |
| active | Whether user is active in the company |
| timezone | User's timezone |
| employee_id | Employee number |
| max_weekly_hours | Max weekly hours allowed |
| invited | Timestamp when invite sent |
| invite_accepted | Timestamp when invite accepted |
| is_new | Whether user is newly created |
| birth_date | Birth date |
| language | Preferred language locale |
| appear_as_employee | Appears in schedules or listings |
| subscribe_to_updates | Opted in for notifications |
| skill_level | Internal skill rating |
| hourly_wage | Hourly pay rate |
| wage_type | Wage type: hourly, salary, etc. |
| permissions_template_id | ID of permissions template assigned |
| onboarding_required | Needs onboarding completion |
| reactivation_status | Reactivation state |
| created | Timestamp of user creation |
| modified | Timestamp of last modification |
| type | User type |