Skip to content
On this page

Org-Level Intelligence

Once your repos are mapped and documents bound, connect a model provider once for the whole org so people can ask questions in plain language. For people who need only read-only access without an account, publish boards.

Important

New here? Build a landscape first. The Plugin or Chat path builds one from an interview; on the Hands-On path you draw it yourself.

What runs without a model, and what needs one

The plugin loop needs no provider. The code plugin runs inside your AI host: /analyze builds the graph locally, /sync pushes it, and /ground checks an authored board against a document repo. Nothing in the plugin loop calls a model on our servers.

Two things use a model: chat and an analysis started inside the portal. Both run on our servers and start on your organization's trial credits, at one credit per message. When the credits run out, both need a connected model provider.

Runs with no providerTrial credits, then a provider
The code plugin's /analyze, /sync, /aspects, /work-items, /skillsChat, on every board screen
The code plugin's /ground and /insightsAn analysis started from chat
Publishing, and everything a stakeholder readsWork items drafted in chat

Connecting a provider

Connect one when the trial credits run out, or from the start if you'd rather use your own account and models. Open Settings → Connectors and authorize a model provider such as OpenRouter. Every workspace in the org uses that connection, so you don't connect again for each board or person.

Tip

Integrations Reference lists every connector and how to authorize it.

What chat adds

Every board screen has a Chat button. One conversation stays with you as you move between boards, and ProvenMap works from mapped nodes, edges, aspects, bound sources and past insights.

Ask a question in chat and watch ProvenMap draw a focused context board from your landscape

In chat, you can get a context board, start an analysis, and draft work items. Drafted work items stay drafts until a person hands them off to developers. Chat covers the full process, and Insights explains where insights appear.

Publishing to everyone else

Publishing needs no model. Publish a board, and stakeholders can read it at a stable URL without an account. You choose the address, which insights, aspects, and skills to include, and the visibility: public, unlisted, protected, or, with SSO, your organization. To update the board, publish it again; the URL stays the same.

The read-only published board viewer a stakeholder opens, with interactive nodes, insights, and docs and no sign-in

Publishing Boards explains the wizard, the visibility tiers, and what a stakeholder gets.

What's next