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. The dashboard Site template card (on home) and Settings, Workspace hold context. API keys live under the developer setup on this app, not in an owner form.

1. Sign in on this site and finish any first-login steps.
2. Copy the workspace env lines (tenant slug, API base, contact endpoint).
3. Put those values on the live project. Confirm forms and content read back.
4. If Requests is on, 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. An optional public runtime key is for blog or other dynamic content. The host still prompts for keys. xTerminal does not push secret values into the host for you.

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.