Share your work

Once a project holds real thinking, Crux gives you three ways to get it in front of the people who need it.

Share with your organisation

Projects are private by default — only you can see them. When you are ready, share a project with your organisation so teammates can open it, read the research, and see how experience entities trace back to evidence. See Sharing projects for the options, and Teams and organisations for workspace setup.

Show stakeholders the live site

For stakeholders who think in screens rather than documents, the browser extension overlays your experience entities on the live site. View on site takes them straight from an entity in Crux to the real thing, where the overlay tells the why-story behind each tagged element — no export or deck required.

Let coding agents inherit the why

The deepest form of sharing is with the people (and agents) building the product. Connect your coding tools through MCP (Settings → Setup MCP) and they can read your experience graph directly: what each page and feature is for, and the evidence behind it. Builders stop guessing at intent, and code stays linked to the entities it implements. See MCP, overlay, and the browser extension.

You've finished the guide

That completes the Introduction to Crux. The natural next step is to go deeper on the AI system:

• Using Ask — the full reference for modes, context, sources, and slash actions, and the start of the Working with Ask guide.
• Applying and materialising answers — how answers become real artefacts.