> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workable

> Connect your Workable account to Oleria to discover recruiting and HR access, roles, and member activity.

Workable is a recruiting platform with an optional HR module (Workable HR). Connect your Workable account to Oleria to bring member access, roles, and recruiting activity into your identity and access graph.

## What Oleria discovers

Oleria reads the following from Workable on its [regular sync schedule](/integrations/overview.md#sync-model):

* **Users** - every Workable member, active and deactivated, with name, email, title, admin status, and recruiting and HR access levels. External (agency) recruiters are included as external users. The last activity date is the most recent action the member took in a job's activity stream.
* **Roles** - the built-in access levels (Super Admin, Recruiting All Access, Recruiting Standard, Recruiting Limited (Reviewer), HR All Access, HR Standard, HR Limited) and any custom permission sets, with each member's role assignments.
* **Activity** - actions members take on jobs, such as moving, commenting on, or rating a candidate. Oleria records who acted, on which job, and when. It doesn't collect candidate details, comments, or ratings.
* **Employees** (optional, Workable HR) - employees with work name, work email, employee number, job title, department, manager, start date, employment state, country, and company (the legal entity when your account uses them, otherwise the account name).

## Prerequisites

* A Workable **Admin** account. Only Admins can generate API tokens in Workable.
* Admin access on the Oleria platform to add a new integration.
* Custom permission sets require a Workable Enterprise plan. Employee data requires Workable HR.

> [!NOTE]
>
> Workable API tokens belong to the Workable account, not to the Admin who creates them. Generate the token while signed in as a long-lived Admin account that won't be removed, and record who created it.

## Create an API token in Workable

**1. Open the API access tokens settings**

Sign in to Workable as an Admin. Go to **Settings**, and under **Integrations** select **Apps**. Scroll to **API access tokens**.

![Workable Settings with Integrations > Apps selected and the API access tokens section](https://mintcdn.com/oleria/RxJESG6ZscWV5CXM/images/integrations/workable/step-1.png?fit=max\&auto=format\&n=RxJESG6ZscWV5CXM\&q=85\&s=ee28cbcc4dd063530df02446db9a2ba7)

**2. Generate an API token**

Select **Generate API token**. In **Name**, enter a recognizable name, such as `Oleria`.

**3. Select the scopes**

Select only the scopes Oleria needs.

**Read access** - required for discovery:

| Scope | Required | What Oleria reads with it |
| :- | :- | :- |
| `r_jobs` | Yes | Account details, members, external recruiters, and the list of jobs whose activity Oleria reads. |
| `r_account` | Recommended | Custom permission sets, Workable HR department names, and legal entities (each employee's company). |
| `r_candidates` | Recommended | Job activity streams, used for activity and last activity dates. Workable bundles candidate read access into this scope. Oleria reads only job activity and doesn't collect candidate records. |
| `r_employees` | Optional | Workable HR employees, departments, and managers. Skip it if you don't use Workable HR. |

**Remediation access** - add only if you want Oleria to run remediation actions:

| Scope | What it allows |
| :- | :- |
| `w_members` | Deactivate and reactivate members, add or remove a member's role, and invite members. |

![Workable Generate API token form with the Oleria name, a one-year expiry and the read scopes selected](https://mintcdn.com/oleria/RxJESG6ZscWV5CXM/images/integrations/workable/step-2.png?fit=max\&auto=format\&n=RxJESG6ZscWV5CXM\&q=85\&s=e9b1f5bc7b32d2779eeef983e78b13a6)

![Workable Generate API token form with the w\_members scope selected](https://mintcdn.com/oleria/RxJESG6ZscWV5CXM/images/integrations/workable/step-3.png?fit=max\&auto=format\&n=RxJESG6ZscWV5CXM\&q=85\&s=4a3ac8a6d39af02642e4a763b078fa38)

**4. Choose an expiry and generate**

In **Expires in**, choose an expiry from 30 days to 2 years, then select **Generate token**. Copy the token right away. Workable shows it only once.

> [!NOTE]
>
> When the token expires, the integration stops syncing. Select **Renew** on the token in Workable before it expires to extend it without changing the token value.

**5. Find your subdomain**

Your subdomain is the first part of your Workable address. For example, for `https://acme.workable.com`, the subdomain is `acme`.

## Connect Workable to Oleria

**1. Open the integration**

Go to your Oleria workspace, select **Integrations**, then select the **Workable** tile.

**2. Complete the connection form**

Fill in the connection form:

| Field | Notes |
| :- | :- |
| Subdomain | Required. Your Workable subdomain, for example `acme`. You can't change it after you connect. |
| API Token | Required. The API token you generated in Workable. |

**3. Authenticate**

Select **Authenticate** to validate the token and save the integration.

## Verify the integration

Confirm the Workable instance appears on the **Connected** tab of your Oleria **Integrations** page with a status of **Healthy**. After the first sync completes, you can review Workable members, roles, and activity in your Oleria workspace.

## Remediation actions

If the token includes the `w_members` scope, Oleria can take these actions in Workable. Oleria can't check for `w_members` in advance, so with a token that doesn't have it, the actions fail when they run.

| Action | What it does | Reversible |
| :- | :- | :- |
| Disable user | Deactivates the member in Workable. Workable also deletes the member's collaboration rules when it deactivates them; Oleria saves the rules and puts them back if you revert. Workable doesn't allow deactivating the last Admin or the last HR Admin. | Yes |
| Enable user | Reactivates a deactivated member. | Yes |
| Add user to role | Adds a role. A built-in Recruiting or HR access level replaces the member's current level in that area. Super Admin and permission sets are added alongside existing roles. If the new level doesn't allow some of the member's collaboration rules, Workable removes them; Oleria saves the rules and puts them back if you revert. | Yes |
| Remove user from role | Removes a role from the member. If the remaining roles don't allow some of the member's collaboration rules, Workable removes them; Oleria saves the rules and puts them back if you revert. Workable rejects removing the member's only recruiting access level. | Yes |
| Create user | Invites a new member with Recruiting Standard access. Workable emails the invitation, sent in the name of an active Super Admin (or, if there is none, a Recruiting All Access member). If the email already has a pending invitation, Oleria leaves it as is. | After the invitation is accepted, reverting deactivates the member. A pending invitation can only be withdrawn in Workable. |

If Oleria can't read a member's collaboration rules, it refuses Disable user, Add user to role, Remove user from role, and the revert of a role change, instead of risking the loss of those rules.

Actions apply to Workable members only, not to external recruiters.

## Limitations

* **No groups** - Workable has no user groups.
* **No jobs or departments as resources** - Oleria doesn't show Workable jobs, hiring teams, or department collaboration rules as access to resources. Each activity names the job it happened on.
* **No API tokens, connected apps, or AI agents** - Workable's API doesn't list API tokens, connected apps, or AI clients, so Oleria doesn't discover non-human identities or credentials from Workable.
* **No sign-in details** - Workable's API doesn't expose single sign-on settings, a member's sign-in method, last login, or last password change.
* **Last activity covers recruiting only** - Oleria sets a member's last activity from their actions on jobs, such as comments, ratings, and stage moves. Members with only HR access, and members who only view candidates, have no last activity date.
* **Pending invitations** - Workable's API doesn't return invited members until they accept. A pending invitation can only be withdrawn in Workable.
* **Employee visibility** - Oleria reads published employees with the information Workable makes available to account-level tokens.

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.