Sharing and project hubs
A place your clients and teammates can return to.
Organize project pages and files in folders, then share with the people who need them. Give a client a clear starting point and keep internal work restricted.
Everything for Acorn.
Put the project in order
Bring briefs, reports, files, and guides together with folders and useful links. Publish a folder when it should become a browsable site.
Choose the audience
Set each page to Restricted, Password, or Anyone with the link. Grant view, comment, or edit access where supported.
Keep the handoff useful
Update documents at their existing links. Keep the hub current as the project moves from discovery to delivery.
Make it your own
A prompt to get you started.
Connect your AI to Fermium, replace the bracketed details, and bring the source material.
Create a project hub for [client] with links to the brief, deliverables, and handover guide. Share the intended client materials with [audience]. Keep internal notes restricted to [team].
What to know
Linking to a document doesn't share it. Each document keeps its own access, so Restricted material stays Restricted. A project hub is a set of pages and files, not a client portal into your databases.
Questions about sharing and project hubs
How do I turn project files into a useful hub?
Organize the brief, deliverables, reports, and handover guide in a folder. Publish the folder when it should become a browsable site, and give readers a clear starting page. Keep updating the underlying documents as the project progresses so the same links remain useful after the first handoff.
Does sharing a hub share everything it links to?
No. A link to a document keeps that document's own access rules. Check the intended client's access to each resource, and keep internal notes Restricted to your team. A hub brings pages and files together; it does not give a client access to your response databases.
Which sharing option should I choose?
Use Restricted when access should belong to selected people or groups. Use Password when the audience should enter a shared password. Choose Anyone with the link when everyone who receives or is forwarded the URL should be able to open the content. Readers need a browser, with sign-in when the access rules require it.
Put it to work.
Workflows
Publish a pageTurn notes or a brief into a readable page for your team, a client, or anyone with the link.- Context to shared understandingTurn the research, files, and decisions your local agent has gathered into a detailed brief, client presentation, or public guide. Choose the audience and keep refining the same link.
