> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-ukg-ready.md).

# Integrating with UKG Ready

Step-by-step guide to authenticate and connect UKG Ready with Drivetrain.

To authenticate your UKG Ready account, you will need to provide the following information:

* Domain
* Company Short Name
* API Key
* User ID
* Password

This guide will walk you through finding or creating those credentials within UKG Ready.

### Prerequisites

Please ensure you fulfill all the requirements to set up the integration:

* You are an **Administrator** in your company's UKG Ready instance, or someone has shared their access with you.

### Instructions

#### Step 1: Get your domain

1. Find your domain in your UKG Ready sign-in URL. For example, if you sign in at `acme.com/ta/Default.login`, your domain is `acme.com`.
2. Store your domain in a document to be shared with your Drivetrain team.

#### Step 2: Find your company short name

* Log in to your UKG Ready account and open the menu in the upper left. Then, go to your **settings icon** and click **Global Setup**, followed by **Company Setup**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-8e2361bee5d64c05492e03d467da966b0da459f3%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Open **Company Info**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-83b47aea827a5b0fca858370ba9b1d8a9692ee9b%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Scroll down to find **Company Short Name** under **Company Address**. Copy your **Company Short Name**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-0fe9c7d982b6098f64730af4ebc17c6e2b21d62e%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Store your **Company Short Name** in the document.

#### Step 3: Find your API key

* In your **Company Setup** page, go to **Login Config**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-9ebe344bfbeb361659b3cff8f5e9200cdcdbaca2%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Scroll to find **API Keys** and click the **eye icon** to reveal the key. Copy the API key and store it in a secure place.

{% hint style="info" %}
If there is no key, you can click **GENERATE** to create one. If there are existing integrations using this key, **DO NOT click GENERATE**.
{% endhint %}

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-21005f5044c244171adc005af0684f706847b8af%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Store your **API Key** in a secure document.

#### Step 4: Create a security profile

* In your menu on the left, go to **Settings**, **Profiles/Policies**, and then **Security**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-d2419750366efa713ae6b8dd784a1b954aa1fb55%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Click **NEW SECURITY PROFILE** on the upper right-hand side.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-9095ea399d2053f61a9a5b35d06195d3020d8340%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* In this profile, make sure all relevant permissions are enabled for the following endpoints.

{% hint style="info" %}
These permissions may be different based on your specific use case.
{% endhint %}

* In your **HR** tab:
  * Find **Employee Management**, **Base Compensation**.
    * Select **View** from the drop-down menu.
  * Find **Benefit Management (Plans)**.
    * Select **View**.
  * Find **Cost Centers**.
    * Select **View**.
  * Find **Total Compensation**.
    * Select **View**.
  * Find **HR Custom Values**.
    * Select **View**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-271331efafe5b20c01e355299f4bf395714e4f76%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-3146260b27f7e75d292aab1b0d348b2cedd4970b%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Under **Leave of Absence Management** near the bottom, select **Manage Requests** (if applicable).

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-79f680ba7bdf67bd40951de73c1bcac9d019d824%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* In your **Modules** tab (if applicable):
  * Scroll to **Rest API Resources**.
    * Select **Employee Demographics**, **Employee HR Custom Fields**, **Employee Profiles**, **Employee Pay Information**, **Employees**, **Employees (Changed)**, and **Employees (me)**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-30516343b6a1d88daa7ff90474f69b006e4a3199%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

* In your **Global** tab (if applicable):
  * In **Global Setup**, find **Company EINs**, **Cost Center Definitions**, and **Leave of Absence Custom Fields Definitions**.
    * Select **View** for each.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-525d702e1479457d1a13b40887fd87cef7840633%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* In **Object Lists**, find **Company EINs**, **Cost Centers**, **Leave of Absence Categories**, and **Pay Period Profile**.
  * Select **View** for all.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-5af831d9e5c1204bab278c951049c2d183e054e0%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* In your **Payroll** tab (if applicable):
  * Find the **Payroll** section. Click **Create/Edit Payroll** and **View/Edit/Add** next to payroll adjustment.
  * Select **Payroll Prep Process**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-a25545cd269ac2f1f4319c54679af5c438e530a3%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Step 5: Create your service account

* From **Settings > Global Setup > Company Setup**, go to **Edit Tabs**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-49a90fe9c3330633a91dbb5d2bcbb3b1ee63dc8d%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* From the **Available Windows** box on the right side of the screen, scroll down to **Service Accounts**. Drag it to the top section in the middle. Click **Save**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-8da5b567d6a337f6042285147b37d22caf606146%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Click **Add Service Account**. To create a new account, enter the following details:
  * Username: **Drivetrain Integration**
  * Password: Generate a secure password.
  * Store these two details in a secure document.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-10f0ee6412f585349a1404f0ca3c7c486b3351c5%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

* Then, enter the **Security Profile** you created. Click the **magnifying glass** for Account Groups and select **All Company Employees**.

<figure><img src="https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-2988104b33d40277883e312acd2fc21a41578b35%2Funknown.png?alt=media" alt=""><figcaption></figcaption></figure>

#### Step 6: Share details with your Drivetrain team

Share the following credentials via a secure document with your Drivetrain team:

* Domain
* Company Short Name
* API Key
* User ID / Username
* Password


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-ukg-ready.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
