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

# Changelog

> Changes to the Enginy public API and MCP server that can change how your integration behaves.

**18 November 2026**

Roles: API keys and MCP clients follow the creator's role

## API keys and MCP clients follow the creator's role

Roles are now on for every workspace. An API key acts as the person who created it, and an MCP client acts as the
person who connected it, so both hold that person's role. Scopes still apply: a call needs the scope on the key or
connection, and the creator's role must include the permission the endpoint needs. When the role lacks it, the
call answers HTTP `403`:

```json theme={null}
{
  "message": "The API key creator does not have permission to perform this operation",
  "restriction": "RESTRICT_CAMPAIGN_LAUNCH"
}
```

`restriction` says which permission is missing; the tables below map each value to its name in **Settings → Roles**.
An MCP tool fails with an error that carries the same `403` status and body.

### New refusals

These checks came with Roles: either the permission is new, or the endpoint did not check it before. A workspace
applies them only while Roles is on, which is now every workspace.

| Endpoint | MCP tool | Permission the creator needs | `restriction` |
| - | - | - | - |
| `PATCH /v1/campaign/{campaignId}/status`, for every status change | `update_campaign_status` | Launch and pause campaigns | `RESTRICT_CAMPAIGN_LAUNCH` |
| `POST /v1/inbox/messages` | `send_inbox_message` | Reply from the inbox | `RESTRICT_INBOX_SEND` |
| `POST /v1/actions` with an enrichment action | `start_an_actions_run` | Run enrichments | `RESTRICT_ENRICHMENT` |
| `POST /v1/workflow/{workflowId}/publish` and `POST /v1/workflows` with `publish: true`, when publishing sets up enrichment steps; `POST /v1/workflow/{workflowId}/run` on a workflow with enrichment steps | `publish_workflow`, `create_workflow`, `run_workflow` | Run enrichments | `RESTRICT_ENRICHMENT` |
| The same publish and run endpoints, for the steps listed under [Workflow steps](#workflow-steps) | `publish_workflow`, `create_workflow`, `run_workflow` | The permission of each step | The step's restriction |
| `POST /v1/identities/connection-link`, `PATCH /v1/identities/{identityId}`, `POST /v1/identities/{identityId}/mailboxes` | `create_identity_connection_link`, `update_identity`, `create_or_update_an_identity_mailbox` | Connect and share identities | `RESTRICT_IDENTITY_SETTINGS` |
| `POST /v1/webhooks`, `PATCH /v1/webhooks/{webhookId}`, `DELETE /v1/webhooks/{webhookId}`, `POST /v1/webhooks/{webhookId}/test` | `create_webhook_subscription`, `update_webhook_subscription`, `delete_webhook_subscription`, `test_webhook_subscription` | Connect and configure integrations | `RESTRICT_INTEGRATIONS` |
| `GET /v1/credits/statement`, `GET /v1/credits/transactions` | `get_credit_statement`, `get_credit_transactions` | View credit usage (the creator must also be a workspace admin, as before) | `RESTRICT_CREDIT_USAGE` |
| `PUT /v1/ai-playbook`, and every write under `/v1/ai-variables`: AI variables, their folders, AI messages, AI snippets and message templates | `update_ai_playbook`, `create_an_ai_variable`, `update_an_ai_variable`, `delete_an_ai_variable` and the other AI variable write tools | Manage AI variables, playbook and message library | `RESTRICT_AI_ASSETS` |
| Social Selling writes: drafts and their scheduling, tracked and scheduled posts, comments and replies, the reply queue, media uploads | The matching Social Selling write tools | Post and engage on LinkedIn, and Edit contacts and companies | `RESTRICT_SOCIAL_SELLING` |
| `POST /v1/tasks/{taskId}/complete` and `POST /v1/tasks/complete-batch` with `pauseConversation: true` | `complete_task`, `complete_tasks_batch` | Create and edit campaigns | `RESTRICT_CAMPAIGNS` |
| `DELETE /v1/tasks` | `delete_tasks` | Delete contacts and companies | `RESTRICT_DELETE` |

Publishing checks the steps that the publish sets up: a step it adds, or the steps of a graph it gives an automatic
trigger for the first time. Running checks every step of the published version. When `POST /v1/workflows` with
`publish: true` is refused, the workflow is still created as a draft, and the `403` body carries `status`,
`message` and `details.workflowId` instead of `restriction`.

A creator whose role lacks **Manage teammates’ work** reaches only the workflows they created or that are shared
with them. The workflow endpoints answer `404` for the others, and `GET /v1/workflows` leaves them out.

#### Workflow steps

| Steps | Permission | `restriction` |
| - | - | - |
| Export or sync contacts and companies to the CRM | Send records to the CRM | `RESTRICT_CRM_EXPORT` |
| Export contacts or companies to CSV | Export to CSV and Excel | `RESTRICT_EXPORT` |
| Delete contacts or companies | Delete contacts and companies | `RESTRICT_DELETE` |
| Add contacts to a campaign, pause contact or company conversations | Create and edit campaigns | `RESTRICT_CAMPAIGNS` |
| Edit properties, assign the company owner, add to or remove from lists, add to the blocklist | Edit contacts and companies | `RESTRICT_EDIT` |
| Send an HTTP request | Connect and configure integrations | `RESTRICT_INTEGRATIONS` |

### Refusals that already existed

These checks applied before Roles as per-member restrictions. A role now decides them, so a creator can lose one when
an admin changes their role.

| Permission | `restriction` | Endpoints |
| - | - | - |
| Edit contacts and companies | `RESTRICT_EDIT` | `PATCH /v1/contact/{contactId}`, `PATCH /v1/company/{companyId}`, `POST /v1/contacts/fields`, list writes (`POST /v1/lists` and adding, removing or moving contacts and companies), contact and company tag writes, `POST /v1/blocklist/items`, `POST /v1/blocklist/add-entities`, `PATCH /v1/blocklist/{itemId}`, every Social Selling write endpoint |
| Delete contacts and companies | `RESTRICT_DELETE` | `DELETE /v1/contact/{contactId}`, `DELETE /v1/company/{companyId}`, `DELETE /v1/lists/{listId}` (these three also need Edit contacts and companies), `DELETE /v1/blocklist/{itemId}`, `POST /v1/blocklist/bulk-delete` |
| Import contacts | `RESTRICT_IMPORT_LEADS` or `RESTRICT_IMPORT` | `POST /v1/contact`, `POST /v1/contacts/bulk`, contact imports from AI Finder (`POST /v1/ai-finder/import`, `POST /v1/ai-finder/previews/{previewId}/import`), `POST /v1/actions` with `SEARCH_LEADS_FROM_LINKEDIN_COMPANY`, `POST /v1/social-selling/engagers/export` |
| Import companies | `RESTRICT_IMPORT_COMPANIES` or `RESTRICT_IMPORT` | `POST /v1/company`, `POST /v1/companies/bulk`, company imports from AI Finder |
| Send records to the CRM | `RESTRICT_CRM_EXPORT` | `POST /v1/actions` with `EXPORT_TO_CRM`, `SYNC_LEAD_WITH_CRM` or `SYNC_COMPANY_WITH_CRM` |
| Create and edit campaigns | `RESTRICT_CAMPAIGNS` | `POST /v1/campaigns`, `PATCH /v1/campaign/{campaignId}`, `PATCH /v1/campaign/{campaignId}/status`, `POST /v1/campaign/{campaignId}/clone`, `POST /v1/campaign/{campaignId}/steps/clone`, `POST /v1/add-contact-to-campaign`, `POST /v1/add-contact-group-to-campaign`, `POST /v1/pause-contact-in-campaign` |
| Create and edit workflows | `RESTRICT_WORKFLOWS` | `POST /v1/workflows`, `PATCH /v1/workflow/{workflowId}/draft`, `POST /v1/workflow/{workflowId}/publish`, `POST /v1/workflow/{workflowId}/run`, `POST /v1/workflow-runs/{runId}/cancel`, `DELETE /v1/workflow/{workflowId}`, workflow folder writes |

The MCP tools built from these endpoints are refused the same way.

### Fix a refusal

* A workspace admin gives the creator a role that includes the permission, in **Settings → Roles**.
* Or someone whose role includes the permission creates the API key, or connects the MCP client.


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