From approved brand to published page, with
control at every step
Define your brand once. People or Claude build with it, nothing Claude builds goes out without permission, and every change lands in the history.
linkable.id runs the work in four steps: the brand lives in the Brand Vault and your themes, people or Claude build with it, the work is reviewed in private, and someone with permission publishes it. Then links and QR codes distribute it and analytics measure it.
Your team, your agency and Claude work inside the same system
Claude connects through one person's account, inside a single workspace, with that person's permissions. It can't delete anything, and the pages it creates stay private until someone with permission publishes them. One caveat: changes to themes, Brand Vault values or widgets on pages that are already public go live immediately, whether a person or Claude makes them. If you need strict control, give people who use Claude a role without those permissions.
The flow in four steps
Define your brand system
Approved logos, colors, fonts, copy and documents go into the Brand Vault, and themes define how every page and QR code looks. If your design team already has a system in Figma or Claude Design, you import it.
Build with it
Your team or Claude builds short links, branded pages and sites with those assets and themes. Anything an agency or an AI builds in its own code is uploaded as a custom page.
Review in private
Pages Claude creates start private, and your team can keep any page private while it is reviewed. Each page keeps a history of who did what and when, including when it was Claude.
Publish, distribute, measure
Someone with permission makes it public. Every page and site gets its own short link and dynamic QR code on your domain, and analytics track views, clicks and interactions, with humans and bots separated.
Why the order matters
One source for the brand
Change the logo in the Brand Vault and it changes on every page that uses it. Assets in use can't be deleted, so nobody leaves a page without its logo by accident.
A record you can check
Every page shows who changed it and when. If compliance asks about a promotion, the answer is in the history, not in the team chat.
Publishing stays a decision
Claude can build a complete page, but publishing it takes a separate permission the person grants when connecting, and Claude can't delete anything. Printed QR codes never need reprinting: you change the destination.
Want to see this flow in a test workspace?
We will walk you through every step: the Brand Vault, a page Claude builds that stays private, the history, and publishing by someone with permission.