Your client finds every logo file, font, color value, and usage rule in one signed-in page, forever. The zip file that gets lost in a download folder is replaced by a living handoff page you can update when the brand does.
The Internal Docs App is a live Taskade Genesis app embedded on this page and the nearest match for an asset library. Explore how a structured file set is organized and labeled, then choose "Use this app" to clone it in about ten seconds and load your own brand deliverables into it.
The build gives you an asset register with everything a client needs to actually use what you made. Each row carries the asset name, category, file format, the file itself, where it should and should not be used, and the version. Colors carry their values in the formats a designer and a developer each need. Fonts carry the licence note so nobody installs something they are not entitled to. A short usage section written in plain language does the job the twenty-page brand book never got read for.
The question this answers arrives at 6pm on a Thursday: which logo goes on a dark background, and can we stretch it. A handoff page with a usage note beside each asset answers it in the client's own hands. Without one, the answer lives in your head, arrives by email the next morning, and sometimes arrives after the artwork has already gone out wrong. Publishing usage guidance beside the file, rather than in a separate document nobody opens, is the single change that makes a brand handoff hold up over time.
Workspace DNA keeps the handoff useful after handoff day. Memory holds every asset and version. Intelligence, powered by 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, writes the usage guidance from your design decisions and answers a client's question about which mark to use where. Execution notifies the client when you publish an update and archives the superseded version.
The register renders in every layout you need:
- Table view for the full asset library with format, version, and usage
- List view for the client-facing browse-by-category page
- Board view for tracking assets through drafted, approved, and delivered
- Mind Map view for showing how the brand system fits together
- Plus Calendar, Gantt, and Org Chart across the 7 project views
Automations handle delivery and updates. Connect Taskade automations so a newly approved asset publishes to the client page and sends a notification, and a superseded version moves to the archive rather than lingering as a trap. With 100+ bidirectional integrations, your design and storage tools pull files in, while Slack and email push the update notice out.
Include the formats people actually need rather than the ones you exported by default. Vector and raster, light and dark, plus a favicon and a social avatar, will cover most of what a client is asked for in their first year.
The AI agents in the app carry 34 built-in tools including file analysis and persistent memory. An agent answers "which logo do I use on a dark background" from your own usage rules, which is the question that would otherwise reach you by email at 6pm.
A living handoff page also changes what happens when the brand evolves. Instead of emailing a new zip and hoping it replaces the old one everywhere, you publish the updated asset, archive the previous version, and the client's page shows the current file with a note about what changed. Anyone on their side who checks before using an asset gets the right one. That is a materially better outcome than the usual situation, where three versions of a logo circulate inside a client organization for years.
Clone the app, invite the client, and the library is yours. Client sign-in is available on Business plans and up, $25/mo billed annually, and App Users is in beta.
Read App styles for applying a brand to your own app, App uploads for the file mechanics, or browse design builds in the Community Gallery. Start at Taskade Genesis. Pair this with Build a Client Document Library With Uploads and Publish a Client Deliverables Approval Queue.
Frequently Asked Questions
Why not just send a zip file?
Because a zip is a snapshot. A handoff page stays current, tells the client which version is live, and answers usage questions without another email to you.
Can clients download everything at once?
Yes. Offer both: a full download for convenience and the browsable register for finding the one file they actually need.
How do I stop old logos staying in circulation?
Archive superseded versions rather than deleting them, mark the current one clearly, and let the update notification tell the client what changed.
Can I include usage rules?
Yes, and you should. A short plain-language note per asset about where it belongs and where it does not prevents most brand misuse.
Does this work for more than logos?
Yes. Photography, icon sets, templates, tone-of-voice notes, and presentation decks all belong in the same register.
Can different client teams see different assets?
Yes. Tag assets by audience and scope the page, so a marketing team sees campaign templates while a product team sees the interface kit.
What if the client asks for a format we did not export?
Track the request as an item on the register. It also tells you which formats to include by default next time.
How do I handle assets we did not create?
List them with their source and any licence note. Clients frequently do not know which of their assets are licensed and which are owned, and the register is a good place for that to become clear before it becomes a problem.
