# Integrating SailPoint with Time Doctor

Time Doctor is a time tracking and productivity monitoring tool used by businesses to manage remote and in-house teams. It helps improve productivity and accountability by providing detailed insights into how time is spent across various tasks, projects, and applications. This document provides instructions to configure a new direct connection to a Time Doctor source. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Time Doctor connector supports the following:

### Account Management

- Aggregate Users

### Entitlement Management

- Aggregate Groups

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## Prerequisites

Ensure the following prerequisites are met before proceeding with the configuration:

- A valid Time Doctor Username (email).
- A valid Time Doctor Password.

  > **Note**
  >
  > SailPoint will use these credentials to generate an `access_token` dynamically using the Time Doctor authentication API.

  > **Resource Links**
  >
  > [API Authentication Guide](<https://app.getaccept.com/api/?utm_source=google&amp;utm_medium=organic-search&amp;utm_campaign=not-provided&amp;_gl=1*z1sf3n*_gcl_au*OTAwMTI4MjgxLjE3NjMwMjA1NDYuMTAzNzYxNzQyNi4xNzYzMDIwNTgzLjE3NjMwMjA1ODc.*FPAU*NTIwNDMzMzE0LjE3NjMwMjA1NDY.*_ga*MTgzMDAwNjg2OC4xNzYzMDIwNTQ2*_ga_KHXQC8JPKG*czE3NjM2MzY1MjUkbzckZzEkdDE3NjM2MzY5MjMkajYwJGwwJGg1Nzg0NTUxODc.*_fplc*RTRwdjlMVXc5eExVbVFXeXBPYmRWY3JYb0xOdDZnNDBleVJRTUJYV2pPZ2ZvMm5OSXF3YiUyRkpkRSUyRlQ5YXlvcjlOTG1tQW92Q1IzQVN1NTFROSUyQjNoeFUwRFVDU0dpU2Y0SG1UYVpsaVRsbnljc1RGMjFpZHdqNDNEd0xiZlRRJTNEJTNE#https://api2.timedoctor.com/#/Groups (Tags)/tagsauthentication_token>) | [Users API Reference](<https://api2.timedoctor.com/#/Users/getUsers>) | [Groups API Reference](<https://api2.timedoctor.com/#/Groups (Tags)/tags>)

## Required Permissions

- The user account must have admin-level access with permissions to read and write all users and teams.