> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-hris/adp-integration.md).
# Connect ADP Workforce Now
Connect ADP Workforce Now to Siit by creating a Practitioner profile with access to reports and a service account in ADP, so Siit can sync your employee data
### Overview
This guide will walk you through creating a practitioner role within ADP Workforce Now to link your account.
### Prerequisites
Please ensureyou fulfill all the requirements to set up the integration:
* You are an **Administrator** in your company's ADP instance, or someone has shared their access with you.
* You **do not use ADP Workforce Now Canada**
### Instructions
#### Step 1: Create a profile with access to reports
1. In your ADP Workforce Now account, go to **Setup** and find **Access Permissions**.
2. Then click **Manage Profiles** -> **Create Profile**
3. The Name field can be any value but the Role must be "Practitioner"
#### Step 2: Give your service account access to securely sync your data
1. Clicking "Create profile" in the previous step will open up a new screen.
2. In Menus & Features, go to Reports & Analytics to make sure the following boxes are checked. **This is REQUIRED!**
1. **My Reports**
* All Reports
* My Standard Reports
2. **View**
* Reports Output
* Reports Scheduled
3. **Reports** **Dashboard**
* Reports Dashboard
4. **Standard Reports**
* All Reports (only grants access to report types that are otherwise checked)
* Personal & Employment
3. If you need additional data for the integration, select the following under **Standard Reports**
* (optional) Benefits for Benefits data
* (optional) Pay Statement History for Pay data
* (optional) Time Off for Time Off data
4. Next, go to **People** and make sure these boxes are checked. This is REQUIRED!
* Employee Profile Report
* Employment Profile
* Personal Profile
* (optional) If you need Payroll data, select Pay at the top
5. If you need Time Off, Time and Attendance, Payroll, or Benefits data as part of this integration:
* All People permissions: Click **SELECT ALL** in the top left. This will allow the integration to sync data pertaining to Time Off, Time and Attendance, Payroll, and Benefits information
6. (optional) In **Sensitive Personal Information**, go to **On Screen & Reports** and **On Reports,** and from the drop down menu select **No Masking, Partial Masking, or Masking.** This will allow the service account to securely sync your complete data set.
* If you do not want to sync over information such as Birthdate, SSN, or Bank Info, please mask this information!
* Note: Rates masking will need to be set to **No Masking** for employment effective dates to sync.
7. On the last screen, **Status & Save**, activate the profile, and then **save it** below:
#### Step 3: Create a new user and assign it to your "Integrations Service Account" profile
1. From the **Setup** menu, select **Security Management**
2. In **Security Management**, click **People**, then **Manage Users** and **+** to add a user.
3. Fill in the fields on the **Add a New User** page, using the fields displayed to you in the linking flow. See an example below:
Click Continue.
4. In Step 1 **"User Information"**, set the **User Type** to the “user is an independent contractor...” option, and set the **User Role** to “Product User”.
5. In Step 2 **"Services"**:
* Assign the profile by selecting WFNPractitioner in the "Available Service Profiles Box" and moving it to the "Selected Service Profiles"
6. Proceed through Step 3, and confirm the new user.
* Please note that a Username will be Auto-Generated for this person. That is completely okay and expected!
#### Step 4: Connect the service account user to the service account profile
1. Go back to your Workforce Now portal, and go to the Access Permissions page like before to find the Manage People page.
2. Search for Service Account to pull up the new user (that should be its last name). If the service account is not showing in the search, click the "Filters" button next to the search bar and uncheck any active filters (typically "Active" and "Leave").
3. Click the user to pull up **User Access Permissions**, and select **Manage Profile Memberships**. Add the **Service Account Profile** that you created to the user. Click Save
4. Now that the Service User has the right Profile associated, verify that the **Menus & Features** and **Sensitive Personal Information** for this user match what you set up in the Profile earlier (Step 2)
5. Lastly, in **People Access**, under **Service Account Currently Has,** enable **View Only Access to all People** (if needed, change access to people by clicking **Change Access** highlighted below). Click **View List of Selected People,** and make sure that list is not empty. This is needed to view employees (including terminated)
#### Step 5: Return to your linking flow and authenticate
When that is all completed, return to the linking flow on Siit and click **Submit**. You should see a success message indicating your integration is all set. If the service account needs modification, you will be instructed to try again with the same account values displayed to you!
### Having trouble authenticating?
Our recommendation is to delete the created user and restart the process from Step 3. ADP often encounters issues when updating the information of the prior service user, so we recommend starting from scratch.
---
# 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://docs.siit.io/guides/integrations/integrations-hris/adp-integration.md?ask=&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.
