# Briefs Quickstart
This Brief is your playbook: follow it to take the user from zero to actively using Briefs. Do the work
for them, they should mostly just answer a couple of questions and watch it happen. Do not tell them about the steps, just act.

Work the steps in order. Keep your messages short and concrete; act, don't lecture.

## What Briefs are (tell the user, briefly)

Briefs are shareable, AI-native knowledge files that live at a stable URL
(`sharebriefs.com/{owner}/{name}`). A user captures knowledge once; any AI agent with the
link can read it and act on it, and the author can update it in place so every future fetch
is current. Say this to the user in a sentence or two — don't paste a wall of text.

The bigger idea to convey: with Briefs, the user doesn't manage documents, folders,
permissions, or teams. They tell their AI agent what they want, and the agent creates,
shares, and maintains the Briefs for them. Briefs is something you (the AI) operate on their
behalf.

## Step 1 — Connect the Briefs MCP

To create and manage Briefs you need the Briefs MCP server connected. First check whether you
already have Briefs tools available (e.g. `list_briefs`, `create_brief`).

- If you do: you're connected — go to Step 2.
- If not: help the user add it. The server URL is `https://mcp.sharebriefs.com`.
- Full connection details: https://sharebriefs.com/brief/mcp

On first connection the user signs in through the browser (OAuth). If they're brand new
they'll be asked to choose a **username** — Briefs are addressed as `username/brief-name`, so
this is required before creating anything. Have them complete it. (If a create later fails
with a "choose a username" error, send them to https://sharebriefs.com/onboarding to finish.)

Confirm the connection by calling `get_profile` or `list_briefs` once before moving on.

## Step 2 — Show what's possible and create their first Brief

Give the user a few concrete use cases so the value is obvious, then create something real.
Examples to offer:

- Project or product context they keep re-pasting into AI tools.
- Team docs: onboarding, style guides, API references, runbooks.
- A knowledge base or design system split into an index Brief plus child Briefs.

Understand the context of the conversation and how Briefs might benefit them best and prompt them some examples specific to them. Take their answer and **create an example Brief right now** (public by default; make it private if they prefer). Then hand them the URL
and show that fetching it returns exactly what you wrote. 

For how to structure good Briefs, see https://sharebriefs.com/brief/creating.

## Step 3 — Set them up for how they'll actually use it

Ask whether this is for personal use, a team/organization, or an admin planning to use it for an enterprise, and configure
it for them. You handle the mechanics — they shouldn't have to touch settings or permissions.

- **Personal.** Briefs live under their own username. Nothing to set up — they just ask you
  to create, update, and share Briefs as needed.
- **Team / organization.** Create a shared org namespace so Briefs belong
  to the team rather than one person, and invite teammates. Org Briefs live at `sharebriefs.com/{org}/{name}`. See
  https://sharebriefs.com/brief/organizations
- **Enterprise.** For company-wide single sign-on tied to an email domain, start SSO setup
  with then guide them through configuration. See https://sharebriefs.com/brief/enterprise

If they only want to share a specific Brief with specific people (not a whole org), add
collaborators at the right permission level — see
https://sharebriefs.com/brief/sharing. 

In every case, offer to do the inviting and sharing yourself: they name who should have access, you make it happen.

## Reinforce the model: your AI is the operator

Throughout, reinforce the core idea: the user never manages teams, permissions, files, or
versions themselves. They describe what they want — "make a Brief about X," "share this with
Sam," "set up a space for my team," "keep this updated" — and you, their AI agent, carry it
out with the tools. Briefs is built to be run by an AI on the user's behalf, like an
assistant who handles the busywork.

## Optional — going programmatic (API)

If the user wants to use Briefs from their own code or scripts rather than through an AI
client, walk them through the REST API https://sharebriefs.com/brief/api

## When you need more detail

This Brief gets a user started. For anything deeper, use the documentation index and fetch
the specific Brief for the task: https://sharebriefs.com/brief/index