Multi-stepClients
One starting point for the whole project.
Bring intake, deliverables, feedback links, and the handover guide together for a client.
A complete worked example
Give Acorn one place to return to throughout the project.
The studio already has a brief, an asset request, and a first creative direction. The client needs a clear reading order and one dependable entry point.
Fictional project and sample data. This preview does not submit, publish, or change access.
Client project hub · illustrative result
Everything for your autumn launch.
Start with the brief, send the remaining assets, then review the creative direction.
- Project brief
- Agreed goals, scope, and milestones
- Asset request
- Add the missing photography
- Creative direction
- First draft ready for client review
One home; deliberate access
The hub links to the intended client materials. Each linked document and form has its own access setting; sharing the hub does not automatically open private source files.
What the recipient can access
The hub and the explicitly shared resources it points to.
Kept out of this handoff
Team notes, estimates, response tables, and unpublished drafts.
How it runs
- Gather the starting materialCreate an intake form and asset destination for the brief and originals.
- Build the project homePublish a page with the brief, milestones, deliverables, and relevant review links.
- Keep it currentUpdate links and the handover guide as work is delivered.
- You getA maintained project page linking to the right resources without exposing internal work.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Build a project hub for [client]. Include an intake form, an asset-request link, deliverables, and a handover guide. Give [client audience] access to the intended materials and keep internal notes restricted to [team]. Update the same hub throughout the project.
What this workflow needs
A hub is a collection of resources. Each linked resource retains its permissions; it is not a guest dashboard with private database rows.
Does sharing the hub share everything in the folder?
No. Check each resource and grant only the intended access.