Skip to content

Integrating SailPoint with Timesheets.com

This document provides instructions to configure a new direct connection to a Timesheets.com source. It is a cloud-based time tracking and employee management service. It helps businesses manage employee hours, project time, expenses, and generate reports for payroll and billing. For terminology specific to SailPoint products, refer to Source and Connector Definitions. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Timesheets.com connector supports the following:

Account Management

  • Aggregate Accounts

Entitlement Management

  • Aggregate Groups(ACCESS)

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

Before configuring the connector, ensure the following setup in Timesheets.com:

  • Timesheets.com account with Admin-level access.
  • API Key and X-TS-Authorization credentials.

To generate API credentials:

  1. Log in to Timesheets.com with administrative credentials.
  2. Go to the Tools section.
  3. Select the option to “Generate API keys for programmatic access to your account”.
  4. Select Generate Credentials.
  5. Copy the generated apikey and x-ts-authorization values.

Required Permissions

Only “Primary Administrator” is authorized to generate API credentials for themselves in Timesheets.com, and there is no current support for fine-grained 'Read-Only' API roles for non-admin service accounts.

Note

You can refer to Getting Started with the API (Beta) for latest information about required permissions for accounts.