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 Timesheets.com 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 Timesheets.com 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 |
|---|---|
| FIRSTNAME | First name of a user. |
| LASTNAME | Last name of the user. |
| FULLNAME | Full name of a user. |
| USERID | Unique identifier for a user. |
| EMAILADDRESS | Email address of a user. |
| ACCESS | Role assigned to the user (e.g., SUPER, ADMIN, EMP, AFFILIATE, SITEADMIN). |
| ADMINUSERID | User ID of the supervisor/admin responsible for this user. |
| EMPLOYEENUMBER | Internal employee number used by the company (optional / custom). |
| ACCESS | Role assigned to the user (e.g., SUPER, ADMIN, EMP, AFFILIATE, SITEADMIN). |
| EMPLOYEENUMBER | Internal employee number used by the company (optional / custom). |
| LOCATION | User's physical or office location (optional field). |
| DIVISION | Business division the user belongs to (optional). |
| DEPARTMENT | Department name (e.g., HR, IT, Sales). |
| JOBTITLE | Employee's job title (e.g., Tester, Manager). |
| USERSTATUS | Account status: 1 = Active, 0 = Archived/Inactive. |
Default Entitlement Attributes
Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to Managing Entitlements for more information.
Caution
Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.
Default Organization Attributes
| Account Name | Description |
|---|---|
| ACCESS | Role assigned to the user (e.g., SUPER, ADMIN, EMP, AFFILIATE, SITEADMIN). |