Human resources system connections

Some organizations can join a limited pilot that reads information from their human resources system. This page explains what to discuss with FTE Tree and how to review an enabled connection. You can use ordinary file imports without joining a pilot.

Before you begin

Connection pages become available only after you and FTE Tree agree to a pilot. Reviewing enabled connections requires the View HRIS integrations permission; creating connections, storing credentials, and testing require the Manage HRIS integrations permission. Changing compensation ownership also requires the Manage actual compensation permission for All departments. See Roles and permissions.

Availability

Human resources system connections are not generally available. Some Workforce Planning customers may qualify for a limited, paid early-access pilot that only reads information from their human resources system. You can request a conversation about your needs, and FTE Tree will confirm whether the pilot fits before you commit.

FTE Tree does not publicly promise support for a specific human resources system. Do not send passwords, sign-in details, or employee information while discussing a possible pilot.

Work with human resources information today

You can configure employee, position, and assignment external IDs as not used, optional, or required. When FTE Tree manages an ID, authorized users and reviewed imports can maintain it. Standard imports and exports can support a reviewed manual process without creating a direct connection.

These tools do not synchronize with a human resources system. Review every import before applying changes, and use only files your organization is authorized to handle.

A future certified connection may manage a supported external ID. That choice is separate from whether the ID is shown or required. When a connection manages the ID, local forms and imports cannot change it, and missing required values need to be reviewed through the connected system. The option appears only for identifier types the connection is certified to manage.

Use an agreed pilot

Use these pages only for the provider account, environment, and work agreed with FTE Tree. A provider appearing in a form is not a promise that every product or feature is supported.

1. Open the enabled human resources connections area in organization settings and create a connection. Enter a recognizable name, the agreed provider, product when applicable, and environment. An optional account identifier is not a password.
2. Select Save connection and confirm the provider and environment on its details page.
3. Select Store credentials. Enter only the approved credentials requested by that connection form, then save. Use this form for secrets; never put them in a connection name, account identifier, comment, contact form, or support email.
4. Select Test connection. The test runs separately; review the result on the connection page. Storing credentials or starting a test does not itself confirm that a synchronization succeeded.
5. Review Status, Last successful sync, and Sync history. Check which information has been received and any items requiring review. Follow the agreed pilot process when a connection or data check fails.

Change who maintains compensation

Use Change compensation owner only for an agreed transfer of responsibility between FTE Tree and a connected human resources system.

1. Choose Assignment scope for an assignment-specific exception, or leave it blank for all assignments.
2. Choose Managed by after cutover. Select the HRIS connection when the connected system will maintain compensation; leave it blank when FTE Tree will.
3. Enter the Cutover date, the first date the new source should maintain compensation, and a reason.
4. Select Review cutover. Check which system manages pay now, which will manage it next, the affected assignments, the change date, and the reason. Target baseline is the prepared pay information from the system taking over. Check its people, amounts, and dates. The connection check and its first complete pay update must succeed before that system can take responsibility.
5. When the review is ready, select Complete cutover and confirm only after checking the consequences below. A draft is not an active ownership change.
6. Review the resulting ownership period and employee pay on the cutover date. Wait for actual compensation results to update, then open an affected record and check its amount.

Completing the change ends affected pay entries from the previous owner at the cutover date and removes its affected scheduled entries that begin on or after that date from current use. Their history remains. When the connected system takes over, its prepared compensation information applies from the cutover date. When FTE Tree takes over, confirm the locally maintained pay entries needed from that date; changing the owner does not invent the replacement pay.

A change to ownership after your review can prevent completion. Review the current information again rather than assuming the earlier preview is still valid. Contact FTE Tree through the agreed pilot process when a draft remains blocked or the result differs from the agreed transfer.

When to contact FTE Tree

Contact FTE Tree if your organization wants to discuss:

• the human resources system and product you use;
• its approximate managed-position count;
• the employee, status, or compensation information it would need;
• identity matching and exception review;
• security and credential requirements; or
• timing for a possible controlled pilot.

Do not send credentials, access keys, passwords, employee records, compensation details, or other sensitive information through the contact form.

Optional practice: check an enabled HR-system connection

Use prepared practice records for this exercise. Follow its setup instructions before making changes.

This optional lesson requires an agreed HR-system pilot. Ordinary CSV imports do not require a connection.

1. Open the connection with the person responsible for it.
2. Check its current status and latest update.
3. Open one employee and assignment you are allowed to review.
4. Compare their identifiers and dates with the connected system.
5. Check which system is responsible for maintaining the pay.

When an ID or pay period is maintained in the connected system, correct it there using the agreed process. Do not overwrite it locally just to make an error disappear.

For an update problem, use the offered recovery action and check the result before repeating it. Keep the connection/update reference for support, but leave credentials and protected files out of ordinary messages.

Form choices

Use this reference to choose form values. Available choices depend on the task, selected date, and your access.

HRIS connection

Choose the connected account that supplies this information. Names identify your organization’s connections, not interchangeable copies of the same source.

Confirm the provider account, environment, and information managed before choosing a connection. Only eligible connections are offered for the task. If the expected account is missing, review connection setup with the person who manages it.

HRIS provider

Choose the supported provider for the organization account you are connecting.

Provider and product identify the human resources source. Confirm that the provider is available for your organization’s connection arrangement before entering configuration. Store credentials only in the dedicated credentials form, not in the display name or account identifier.

Environment

Choose the provider environment that matches the account and credentials.

A sandbox and production account can have different identifiers and data. Choosing Sandbox does not make production credentials into test credentials. Confirm the provider account before testing or reviewing a connection.

Managed by after cutover

Choose who may maintain compensation from the cutover date.

Leaving assignment scope blank changes the owner for all assignments. Selecting one assignment creates an exception for that assignment. Review the cutover date and connection before activation; the date is the first date the new owner may publish changes.

Assignment scope

Leave blank for all assignments, or select one assignment for a deliberate ownership exception.

Use an assignment exception only when that employee-position relationship needs a different compensation owner. Check the existing owner, proposed owner, connection, and cutover date together before activation.