Give a developer access
Developers build on Ferndesk with an API key. You create the key, pass it to the developer safely, and revoke it when it's no longer used. Everything is in Settings > Workspace > Developers.
Owners and admins can open this page and create keys.
Choose what the key can do
Name the key after where it will run, such as "Zapier sync", then pick its access:
Access | What the key can do |
|---|---|
Full access | Read and change content, publish, read reports and AI agent conversations, work the Support inbox, change settings and manage webhooks. It cannot reply to customers or invite teammates. |
Read only | Read content, reports, AI agent conversations, the Support inbox and settings. It changes nothing. |
Custom | Pick each permission, including replying to customers and inviting teammates. |
Ferndesk shows the key once. Send it to your developer through a password manager or your secrets store, not in chat.
Whose key it is
A key acts as the person who created it, with that person's current role. If they become a Contributor, the key keeps working but can only save drafts: it can no longer publish, change settings or manage webhooks. If they leave the workspace, their keys stop working. Keys do not expire.
Revoke a key
Choose Revoke from the key's menu. Anything using it stops working at once. The list shows who created each key and when it was last used, which helps you spot keys nobody uses.
Webhooks, sign-in and AI tools
The same page has Webhooks, the addresses Ferndesk notifies when content changes. See Webhooks.
Customer sign-in holds the signing secret your developer uses to sign readers and widget visitors in. See Sign readers in with JWT or OIDC.
AI tools connect through MCP with no key: each person signs in from the tool and approves access.