Use case · Agencies
Keep one client's context out of every other client's build
An agency cannot risk one client's private decisions appearing in another client's work. Hark isolates workshops at the database level and locks each agent session to one project until an explicit switch.
The setup
A simple way to run it in Hark
- 01Open one isolated workshop per client
Keep its people, agents, files, permissions, and private decisions inside a database-level boundary.
- 02Lock every agent session
Claude Code, Codex, or Cursor can read and write only the selected project until someone explicitly switches it.
- 03See all delivery without mixing context
Use the Agency overview for a cross-client view while each underlying client record stays separate.
- 04Invite the client safely
Give unlimited guests a branded room scoped to their project and only the sections they should see.
Starter build
Hark’s public project page
Starter builds are coming. Until then, use Hark’s own documented build as the example structure for this setup.
View the public project page placeholder →Common questions
- Can I use this setup for an existing client portfolio?
- Yes. Import a conversation or brain dump, review the drafted project, and connect the repository when you are ready. You do not have to start from scratch.
- Do all collaborators and agents see the same information?
- They work from the same Hark project and Current state, subject to the workspace and project permissions you choose.
- Can I try this without adding a card?
- Yes. Hark starts with a 14-day card-free trial, and your work remains readable if the trial ends before you choose a plan.