Connect a site

Connect means the public site and this dashboard share the same tenant. Forms land in Inbox. Content you edit here can show on the live site. Requests can point at a page path. Signing up does not create those pages.

What connect means

• The live URL is whatever the developer deployed.
• Environment values tell the site which dashboard to talk to.
• Contact and content reads use this site's slug and keys, not a guess.

What the owner does

Owners do not connect a repo from Settings. They name the site, invite the developer, and run the dashboard after connect.

1. Finish signup and name the site.
2. Invite the person who built (or will build) the site from Settings, Team.
3. When the public URL works, try a small Edit and a test Inbox note.

What the developer does

The developer holds the repo and the host. First login opens a four-step setup: template, Runtime, site env, then Connect your agent. API Keys keeps the same Runtime door and the same one-liner for later. Owners never see those keys.

1. Sign in and finish first-login setup, or open API Keys anytime.
2. Mint or reuse a Runtime key in the wizard, on API Keys, or from GET and POST /api/developer/v1/runtime-keys.
3. Copy the workspace env lines (tenant slug, API base, contact endpoint, and the Runtime key when you have the secret).
4. Put those values on the live project. Confirm forms and content read back.
5. Connect your agent from the lab pages, or say Set up my xTerminal site. The agent fetches /xterminal/skills/setup-site/v1.
6. Managed and Requests are a later session. If Requests is on later, write the site repository as org/repo under Settings, Requests.

Environment values

The usual copy lines are the site slug, the API base for this dashboard, and the contact endpoint. A public Runtime key is for blog or other dynamic content. The host still prompts for keys. Sitedio does not push secret values into the host for you.

A connect agent signed in as admin or developer can mint that Runtime key from GET and POST /api/developer/v1/runtime-keys, then write the env lines on the host. The human wizard uses the same door. GET lists prefixes and the tenant slug. POST returns the raw key once, or reuses an active key with the same name. Worker keys cannot call this door.

Where this sits in Settings

• Workspace: name, slug, and domain context.
• Site: public site name and tagline.
• Requests: site repository and, for admin or developer, worker connection.

After connect

Everyday copy the owner edits in the dashboard. Anything else is a Request when that tool is on. If the public site is down and the dashboard is up, that is usually the host or DNS, not this control panel.