Connect Claude
Connect Claude links a workspace to Claude, Anthropic's AI assistant, so you can work in it by asking: "create a short link for our summer campaign", "build a private page for the spring launch", "add these new hires to our People directory".
Availability: the AI connector must be included in your plan. Custom connectors work on all Claude plans (the Free plan allows one custom connector; on Claude Team/Enterprise plans an organization Owner must add it). Anthropic currently marks custom connectors as a beta feature.
How the connection works
Every connection is bound to one workspace:
- Each workspace has its own connector URL, shown on Settings → Connect Claude.
- When you authorize the connection you sign in with your linkable.id account. Claude can only see and do what your role allows, in that workspace only, within your plan's limits.
- To work with several workspaces, add each workspace's connector URL as its own connector in Claude.
Connecting
- In your workspace, open Settings → Connect Claude and copy the connector URL.
- In Claude (claude.ai, the desktop app or Claude Code), open Settings → Connectors and choose Add custom connector.
- Paste the connector URL and confirm.
- Sign in with your linkable.id account and authorize the workspace on the consent screen.
Permissions
The consent screen lists what the connection may do. Each permission only works together with your role's permission for the same action.
| On the consent screen | What Claude can do | Your role also needs | More |
|---|---|---|---|
| View links, domains, tags and templates | Find and read links, domains, tags, QR themes and share-preview templates | Branded URLs | |
| Create and update links | Create links and change them (the short address never changes) | Create or update links | Branded URLs |
| View widget, layout and QR themes | Read themes and which settings they accept, and preview a QR theme as an image | Layout Themes | |
| Create and update widget, layout and QR themes | Create and restyle themes, set a Layout Theme's logo, background and favicon and a QR theme's logo | Create or update themes | Widget Themes |
| Write custom CSS on widget and layout themes | Write a theme's custom CSS (where custom CSS is on) | Update Custom Css | Custom CSS |
| View Brand Vault assets and folders | Read vault assets and folders | Brand Vault | |
| Create and update Brand Vault value assets and folders | Create colors, links, contact details and texts; edit any value asset; organize folders | Create or update vault assets and folders | Brand Vault |
| Upload files to your Brand Vault | Upload images, icons, fonts, audio and documents | Create vault assets | Brand Vault |
| View branded pages and their widgets | Find and read pages and their widgets | Branded Pages | |
| Create and edit branded pages and their widgets | Create pages (always private) and build them with widgets | Create or update pages | Widgets |
| Make branded pages public or private | Publish or unpublish a page | Update pages | Branded Pages |
| View branded sites… / Create and edit branded sites… | Read sites; create them, add pages, arrange the menu, add site widgets | Create or update sites | Branded Sites |
| View custom pages… / Create and edit custom pages… | Read Custom Pages; create them (always private) and upload builds to private pages | Create or update Custom Pages | Custom Pages |
| Make custom pages public, publish builds to public pages, and loosen a page's sandbox | Publish, upload to or roll back a public page, allow embeds | Update Custom Pages | Custom Pages |
| View design systems, their versions and files, and export them | Use a design system, download its files, export it | View design systems | Design systems |
| Create design systems and bring in new versions of their packages | Create a design system and upload new versions | Create or import design systems | Design systems |
| Publish design system versions or roll back, set the default design system and the current version, and create, change and revoke share links | Change the default or current version, make members-only share links | Update design systems, Share link | Design systems |
| View the People directory, its custom fields, card templates and cards | Read people, card templates, signatures and change requests | View people, card templates, signature templates | People |
| Create, update, import and deactivate people; manage custom fields, … approve or reject employee change requests (the employee is emailed) | Add, update, import and deactivate people; custom fields; card templates, variants and per-person card changes; email signatures; decide change requests | Create or update people, Bulk import, Manage custom fields, Customize card, Review change requests, card and signature template permissions | Card templates, Signature templates |
Custom CSS, design systems and team cards appear on the consent screen only while they're turned on for linkable.id, and Claude only sees their tools then. Your plan still decides whether your workspace can use them.
What Claude can do
- Links: create, find and update short links with tags, UTM parameters, a QR theme and a share preview. Try "make a short link for our webinar, tagged events".
- Themes: read and restyle Widget and Layout Themes, and write custom CSS. Try "restyle my landing: dark background, green accents, rounded corners".
- Brand Vault: create and edit brand values (colors, links, contact details, texts), organize folders and upload files, including from a public link. Try "write our brand guidelines as a text asset".
- Branded Pages and Sites: build pages with widgets, arrange them into sites, and publish when you ask. Try "build a page for our spring launch with a header, a booking button and our contact details".
- Custom Pages: host a static build (HTML, CSS, JS) under
/c/your-slug/. Try "build a one-page launch site and host it as a Custom Page". - Design systems: pick the right design system for a task, work from its
SKILL.mdand files, bring new versions in, export it or share it as a skill. Try "make an event flyer that follows our design system". - Team cards: manage the People directory and custom fields, build card templates, variants and email signatures, and decide employees' change requests. Try "add these new hires" with a pasted table.
Some things stay in the panel: Claude can't see analytics, manage domains, QR themes, scripts or users, delete records, or make a share link public.
Safety
- New pages and Custom Pages are always private. Making them public is a separate permission, and Claude publishes only when you ask.
- Some changes go live at once, as in the panel: theme edits, Brand Vault value edits, widget changes on public pages, card template and people edits (cards and signatures re-render). Claude tells you how many places a change affects and gives you a link to review.
- Some actions email people: approving or rejecting an employee's change request emails that employee. Claude does it only when you decide.
- Images in email signatures become public files, so they show in every mail client.
- Nothing is deleted through Claude: deletion stays in the panel. Taking a page out of a site or an asset out of a folder deletes nothing. The only exceptions: a design system draft that was never published can be discarded, a widget's own uploaded file is replaced when you give it a Brand Vault file instead, and resetting one person's card removes the widget only that card had.
- Everything Claude does is recorded in the activity log under your name, marked as done via Claude.
- Only Claude's own apps can connect (claude.ai, the desktop and mobile apps, and Claude Code). The consent screen shows where access will be sent; for Claude Code it warns that it's an app on your computer.
- Leaving a workspace, or the workspace being deleted, revokes its connections automatically.
Large files
Claude sends small files (up to 700 KB) right in the conversation. For anything larger, such as a Custom Page build, a Brand Vault image or a design system file, it asks linkable.id for an upload link and sends the file to uploads.linkable.id. That needs a place where Claude can run commands with network access: Claude Code, Cowork, or a claude.ai conversation with code execution turned on.
If your organization limits which websites Claude's code execution can reach, allow:
uploads.linkable.id, for uploads.- Your workspace's own address (the one in your connector URL), so Claude can download files back, for example to check a design system file.
Each upload link is made for one file, has a size limit, and expires within 30 minutes. The file goes straight to linkable.id's storage.
Rate limits
Per connection, on top of your plan's limits:
- 60 requests a minute.
- 120 Brand Vault files an hour (uploads and imports from a link together; a refused import counts).
- 10 Custom Page builds an hour.
- 10 design system syncs, 200 design system file links and 20 design system exports an hour.
- 30 people imports an hour, up to 200 people each.
- 30 card template refreshes an hour.
Reconnecting
A connection keeps the permissions you approved when you made it. When linkable.id adds a new area (as it did for pages, sites, Custom Pages, file uploads, custom CSS, design systems and team cards), a connection made before doesn't have it, and Claude gets this answer:
This connection was not granted the 'people:write' permission. Reconnect the linkable.id connector and approve it to continue.
To reconnect:
- In Claude, open Settings → Connectors, remove the linkable.id connector for this workspace and add it again with the same connector URL.
- Sign in and approve the permissions on the consent screen.
Claude also keeps the connection alive on its own while you use it. If you don't use a connection for 30 days, Claude asks you to sign in and authorize it again.
Disconnecting
- On Settings → Connect Claude, Your active connections lists every connection you've authorized for the workspace. Revoke disconnects one immediately.
- Removing the connector in Claude's settings also stops it from using the workspace.
For developers and AI agents
The Claude connector reference lists every tool by area with its permission, role permission and step-by-step workflows. It's generated from the connector, in English.