# SailPoint Tallyfy Connector Documentation

> Tallyfy Connector Documentation

# Documentation

# Connecting SailPoint and Tallyfy

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Tallyfy API base URL as **Base URL**. For example, `https://api.tallyfy.com/organizations`.
2. Enter the **API Token**.
3. Enter the **Organization ID**.
4. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Tallyfy

Tallyfy is a cloud-based, no-code workflow and process management platform for organizations that need to document, run, and track repeatable business processes and approvals - without flowcharts, spreadsheets, or manual follow-ups. It lets teams turn any recurring task into a step-by-step template, assign steps to people or AI, and get real-time visibility into where every task and approval stands. This document provides instructions to configure a new direct connection to a Tallyfy source.

> [!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 Tallyfy connector supports the following:

### Account Management

- Aggregate Account (Users)

### Entitlement Management

- User roles are captured as part of the Account aggregation itself (embedded within each Organization User record), so a separate Entitlement aggregation is not required.

> [!NOTE]
>
> This connector is read-only. It supports account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported. Roles on the account are captured as part of account aggregation. Separate entitlement aggregation is not required.

> [!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:

1. Sign in to [Tallyfy](<https://account.tallyfy.com/register>).
2. Go to **Settings \> Integrations \> REST API \> VIEW YOUR API ACCESS TOKEN**, and copy the **Organization ID**.
3. Copy and securely store the following details, which are required during connector configuration:

   - **Organization ID**
   - **API Access Token**

> [!NOTE]
>
> - API tokens are tied to the Tallyfy user account that generated them. Deactivating that account or revoking the token immediately invalidates it.
> - Tokens should be transmitted only over HTTPS and stored securely.
> - Tallyfy authenticates API requests using the HTTP Authorization header with a Bearer token in the format: `Authorization: Bearer <API_TOKEN>`. For the Organization Users endpoint used by this connector, the Authorization header alone is sufficient. Some other Tallyfy API endpoints may additionally require an `X-Tallyfy-Client: APIClient header` - if you extend this connector to other resources and get a `401` or `endpoint not found` error, add that header.
> - OAuth 2.0 (application tokens) is also supported for server-to-server/Enterprise integrations, but personal access token authentication is the standard method for direct API integrations.

For more information about Tallyfy API authentication, refer to the [Tallyfy API documentation](<https://go.tallyfy.com/api/>).

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

## Required Permissions

- **Admin** - Full access, including account settings and API token management.
- **Standard/Light users** - Access is scoped to what their role permits within Tallyfy; a token generated under such a user inherits the same visibility.
- Tokens inherit the permissions of the user who created them. If a user's role doesn't have access to a given resource in the web interface, API calls to that resource will fail with an authorization error, even if the token itself is valid.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Tallyfy connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| id | Account (User) |

### Default Account Attributes

The Tallyfy connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| id | Unique identifier for the user in Tallyfy |
| email | User's email address |
| username | Unique username for the user |
| first\_name | First name of the user |
| last\_name | Last name of the user |
| full\_name | Full display name of the user |
| profile\_pic | URL to the user's profile picture |
| resize\_profile\_pic | URL to the resized version of the profile picture |
| country\_id | Identifier of the user's country |
| phone | User's phone number |
| job\_title | User's job title |
| job\_description | Free-text description of the user's job |
| team | Team the user belongs to |
| timezone | User's configured timezone (for example, Asia/Kolkata) |
| UTC\_offset | UTC offset corresponding to the user's timezone |
| type | User type (for example, member or bot) |
| role | Tallyfy role assigned to the user - used as the Entitlement value (for example, admin, standard, light) |
| status | Current account status (for example, active, invited) |
| is\_active | Whether the user account is active |
| is\_support | Whether the user is a support-designated account |
| is\_partner | Whether the user is flagged as a partner account |
| is\_default\_admin | Whether the user is the organization's default admin |
| date\_format | User's configured date display format |
| cadence\_days | Days configured for the user's process reminders |
| step\_preferences | User's step display preferences |
| last\_country | Last known country of the user |
| last\_city | Last known city of the user |
| last\_known\_ip | Last known IP address used by the user |
| last\_known\_country | Last known country derived from IP |
| initial\_signup\_method | Method used for initial signup (for example, manual) |
| invited\_by | ID of the user who sent the invitation, if applicable |
| created\_at | Timestamp when the user account was created |
| updated\_at | Timestamp when the user account was last updated |
| activated\_at | Timestamp when the account was activated |
| approved\_at | Timestamp when the account was approved |
| last\_login\_at | Timestamp of the user's last login |
| last\_accessed\_at | Timestamp of the user's last access |
| disabled\_at | Timestamp when the account was disabled, if applicable |
| disabled\_by | ID of the user who disabled the account, if applicable |
| reactivated\_at | Timestamp when the account was reactivated, if applicable |
| reactivated\_by | ID of the user who reactivated the account, if applicable |
| deleted\_at | Timestamp when the account was deleted, if applicable |