> ## Documentation Index
> Fetch the complete documentation index at: https://mcp.shipcontent.com/llms.txt
> Use this file to discover all available pages before exploring further.

---
title: The owner boundary
description: The owner pages, what each one decides, and the exact tool an agent reads to learn that a handoff finished.
section: start
order: 50
status: implemented
mode: both
reviewed: 2026-11-19
sources: [src/components/marketing/marketing-workspace.tsx, src/proxy.ts, src/lib/host-routing.ts, src/lib/server/auth/PrincipalResolver.ts, src/lib/youtube/youtube.ts, src/lib/server/youtube/YouTubeService.ts, src/lib/server/auth/EmailSender.ts, src/lib/server/auth/TokenVerifier.ts, src/lib/server/owner/owner-session.ts, src/lib/mcp-surface.ts, src/lib/docs/handoffs.ts, src/lib/docs/origin.ts, src/lib/docs/tools-json.ts, src/lib/server/owner/OwnerHandler.ts, src/lib/server/auth/BetterAuth.ts, src/lib/server/auth/GoogleProvider.ts, src/lib/server/auth/GitHubProvider.ts, src/lib/mcp/agent-tools.ts, src/lib/server/mcp/AgentMcp.ts, src/components/owner/owner-onboarding.tsx, src/lib/server/x/XPublishing.ts, src/components/owner/channel-tiles.tsx, src/lib/server/x/x-callback.ts, db/x.sql, src/app/login/page.tsx, src/lib/server/auth/AuthEmail.ts, src/app/reset-password/page.tsx, src/components/owner/password-recovery.tsx, src/lib/server/owner/owner-page.ts, src/lib/auth/owner-login-path.ts, src/components/owner/connections-hub.tsx, src/components/owner/agents-page.tsx, src/app/(app)/workspaces/page.tsx, src/components/workspaces-page.tsx, src/components/owner/workspace-switcher.tsx, src/lib/server/owner/connections-overview.ts, db/instagram.sql, src/lib/workspace/workspace.ts, src/lib/media/media-return-path.ts, src/lib/social/connect-path.ts, src/lib/server/social/connect-start.ts, src/app/connect/[provider]/route.ts, src/app/[workspace]/(app)/connections/page.tsx, src/app/[workspace]/(app)/agents/page.tsx, src/app/[workspace]/setup/page.tsx, src/app/(app)/workspaces/new/page.tsx, src/components/owner/setup-wizard.tsx, src/components/new-workspace-page.tsx, src/lib/server/owner/default-workspace.ts, src/lib/server/youtube/youtube-callback.ts, src/lib/server/instagram/instagram-callback.ts, src/lib/server/social/connection-failure.ts, src/components/owner/connect-notice.tsx, src/app/[workspace]/(app)/studio/page.tsx, src/app/[workspace]/(app)/brand/page.tsx, src/components/studio/studio-page.tsx, src/components/studio.tsx, src/components/owner/jobs-menu.tsx, src/lib/server/media/project-agent-tools.ts, src/app/[workspace]/(app)/calendar/page.tsx, src/components/marketing/post-calendar.tsx, src/components/owner/youtube-controls.tsx, src/components/owner/post-review.tsx, src/app/posts/review/page.tsx, src/app/[workspace]/(app)/marketing/page.tsx, src/components/owner/instagram-approval-panel.tsx, src/components/owner/instagram-destination-selector.tsx, src/lib/instagram/instagram-owner-publish.ts, src/lib/server/instagram/InstagramReadinessCheck.ts, src/lib/media/video-inspection.ts, src/lib/marketing/post-catalogue.ts, src/lib/marketing/post-scheduling.ts, src/lib/server/marketing/PostScheduling.ts, db/publishing.sql, src/components/owner/post-schedule-controls.tsx, src/app/tiktok/page.tsx, src/app/[workspace]/(app)/tiktok/page.tsx, src/components/owner/tiktok-account.tsx, src/lib/server/tiktok/TikTokPublication.ts, db/tiktok.sql, src/lib/server/tiktok/TikTokAccounts.ts, src/lib/server/tiktok/tiktok-callback.ts, src/lib/server/database/AppDatabase.ts, src/components/owner/agent-access.tsx, src/components/owner/agent-permission-rows.tsx]
tools: [list_workspaces, get_workspace, get_media_upload, get_media_job, get_post, prepare_website_import, get_website_import, get_instagram_connection, get_instagram_readiness, get_instagram_approval, list_posts, inspect_post, ads_list_connections, ads_get_connection, ads_get_approval_request, ads_get_operation, get_project, prepare_post_schedule, get_post_schedule]
next: [/docs/contracts/approval-model, /docs/start/for-owners]
---
A handoff is the point where the agent gives the owner a URL and waits. The URL carries no permission by itself. The signed-in owner reviews current saved state and makes the decision in the browser.

Hosted owner URLs use `https://app.shipcontent.com`. This includes sign-in, consent, channel connections, review, upload and media pages. Agents continue to call `https://mcp.shipcontent.com/mcp`. `SHIPCONTENT_OWNER_ORIGIN` selects the browser origin; owner APIs require that host and retain their session and CSRF checks. A GET to an owner page on the MCP host forwards to the dashboard.

## Owner pages

App pages carry the workspace number of the signed-in owner: `/3/dashboard`. The number is short and belongs to one owner. Two owners each have a workspace `/1/…`. A number the account does not have shows "This workspace is not available for your account." The API and the agent tools keep the workspace ID, not the number.

| Page | Owner action |
| --- | --- |
| `/login` and `/oauth/consent` | Sign in with a password or a configured Google or GitHub option. A plain sign-in opens the workspace last opened, at `/{n}/dashboard`, or at `/{n}/setup` while its setup is not done. An agent link continues to its own page, and an MCP request continues to consent: one sentence names the client, plain-language lines say what `mcp:access` and `offline_access` allow, and the client ID and raw scopes sit behind **Details**. The owner picks **Allow** once for all workspaces or **Don't allow**. Publish is optional: select its box and type `allow agent`. |
| `/{n}/setup` | Set up a new workspace in four steps: name (required), then channels, agents and website (optional). The saved step is in the database, not in the URL. **Go to dashboard** is always available. |
| `/{n}/dashboard` | See and edit the business details, and see posts, draft posts, delivery issues, channels and agents of one workspace. While setup is not done, **Continue setup** opens the saved step. Agent setup is optional. |
| `/reset-password` | Request an email link, then set a new password. The link expires after one hour and works once. |
| `/agent-access` | Connect an agent to all your workspaces, set **Publish social posts** and the **Generate images and videos** budget, or disconnect it account-wide. |
| `/{n}/connections` | See each channel of one workspace. Connect, reconnect or manage a channel. |
| `/{n}/agents` | Updated 2026-11-07: see the same account agents in every workspace. Copy MCP setup. In **Publish social posts**, select **Allow** and type `allow agent`, or **Turn off**. In **Generate images and videos**, select **Set budget**, **Change**, **Raise budget** or **Turn off**. **Disconnect** revokes the agent's access. |
| `/{n}/settings` | Rename the workspace, open its business details on the Dashboard, open Connections. Account items are in the account menu. |
| `/media/upload` | Upload an MP4 when the agent has no Publish permission, or when the owner chooses the file. The page takes video only. An agent with Publish uploads images with `directUpload`. |
| `/{n}/studio` | Make a video, carousel, image or Story, edit it, convert it and export each size. Approve a generation or render from an agent in **Jobs**. The **Create … for review** button makes one Posts draft for each supported channel. Quick AI shows estimated credits and format fit under **Make it fit**. |
| `/{n}/calendar` | Open Month or Week, create a planned draft, or open a saved post. A planned date does not approve or publish. |
| `/posts/review` | Open the selected post under `/{n}/marketing?tab=posts&post=<id>` after the workspace ownership check. Preview and edit it in the shared app layout. For Instagram, select **Publish** to check and queue the saved Reel. |
| `/connect/x`, `/connect/youtube` and `/connect/instagram` | Open the link to authorize the channel. The link needs the workspace ID and a return page: `setup` or `connections`. The provider screen is the confirmation. A signed-out owner signs in first. |
| `/advertising/connect` and `/advertising/review` | Connect TikTok Ads and review a plan operation. |
| `/workspaces` and `/workspaces/new` | List all workspaces by number, and start an extra workspace at its channels step. `/workspaces` also continues an agent's website import. |
| `/{n}/marketing`, `/{n}/library`, `/{n}/review` and `/{n}/brand` | Continue post work, inspect saved media in the owner browser, review media, and edit the brand text. |

A failed channel connection can return a fixed `reason` value. Setup and Connections show its recovery action. Unknown or repeated reason values are ignored. A return notice does not change saved connection status.

The Posts page creates, opens and duplicates posts. Its editor shows the published text and media, with no separate Hook, Call to action or internal Title inputs. The selected post keeps the Posts tabs, workspace header and app navigation. The Instagram **Publish** button runs current video and account checks, then saves the exact owner approval and queues one job. No separate readiness action or confirmation checkbox is required. Open Studio from the navigation to create media, then attach saved media to a post.

The header of each app page shows the current workspace. The owner selects it to switch to another workspace on the same page, start a new workspace, or open `/workspaces`.

A signed-out visit to an app page or a channel link redirects to `/login` and returns to the same page after sign-in. This includes a project link with `project`, `step` or `mediaJobId`: the owner returns to the same project or render job after sign-in.

An agent link keeps the workspace ID, for example `/studio?workspaceId=<id>&mediaJobId=<id>`. A project link is `/studio?workspaceId=<id>&project=<id>`; with `mediaJobId=<id>` it also opens that render job in **Jobs**. In the app, the same page is `/{n}/studio?project=<id>`, and `step=export` opens the export view. The old unnumbered paths `/dashboard`, `/marketing`, `/studio`, `/library`, `/review`, `/connections`, `/agents`, `/brand` and `/settings` check that the signed-in owner has that workspace, then redirect to the numbered page. Another account sees "not available". A link without a workspace ID opens the workspace last opened, or its setup while that is not done.

Use **Create account** with your email address. Signup stores no usable password and sends a one-hour, single-use setup link. Open the link, choose your password, then sign in. Signup and setup grant no session, workspace or agent access. Repeating signup sends no extra email and does not change an existing password. Use **Sign in** or **Forgot password?** instead. If the setup link expires or no link arrives, use **Forgot password?** to get a new link. Contact support if no link arrives.

A password reset ends the account's browser sessions, MCP access and refresh tokens, native OAuth consent, application grants and pending consent requests. Queued grant work is cancelled. Other owners keep their access. Sign in with the new password, reconnect each agent, and approve consent again. An old access token stays invalid after reconnect. Historical verification links cannot activate a password chosen before mailbox proof.

Google or GitHub can link only when the ShipContent email and the provider email are both verified. Eligible linking keeps the user ID, password and workspaces. Email verification does not approve an MCP client or grant agent access.

After verified sign-in, ShipContent creates workspace 1, named "My workspace", if none exists. Its setup starts at the name step. Repeated session reads do not create duplicates. An MCP request can connect the client to all owned workspaces at once; setup waits for the owner's first visit to the app. The original permitted owner destination or signed MCP authorization request is retained through mailbox setup. An expired MCP request must restart from the client. Email verification and sign-in never approve MCP consent or grant agent access.

If a signed MCP request changes or expires, consent stops and says "This connection request is invalid or expired. Start again from your agent." An already-connected client can select **Allow** again; the active account grant stays and consent saves the new Publish choice. **Don't allow** sends `access_denied` to the client and creates no grant. If the account has no workspace, consent shows one line that opens workspace setup in a new tab, so the signed consent tab stays open; the owner finishes setup there and returns to the open consent tab. In practice this does not happen, because sign-in already created workspace 1.

**Allow** keeps the OAuth redirect back to the client; ShipContent does not control what the client shows next. For a terminal client, the owner can close the browser tab once the client reports it is connected. Updated 2026-11-07: `/agent-access` lists the newest grant first with its connection date, so the owner has one place to confirm the connection if the client gives no confirmation of its own.

When Google sign-in is configured, select **Continue with Google**, marked with the full-color Google logo.

## Resume after the owner acts

Read the corresponding saved record: `get_workspace`, `get_media_upload`, `get_media_job`, `get_project`, `get_post`, `get_instagram_connection`, `get_instagram_readiness`, `get_instagram_approval`, or `ads_get_operation`. Do not infer completion because the owner opened the URL. A queued Instagram publication job still needs a final state and receipt.

The [tool reference](/docs/reference/tools) lists each tool's handoff field and follow-up read. An agent never uses a browser owner session or CSRF token as its own credential.

## Channel connections

`start_x_connection`, `start_youtube_connection` and `start_instagram_connection` return `connectionUrl` for `/connect/{provider}`. The owner opens it and signs in if needed. Each channel goes straight to the provider. YouTube opens Google authorization with no intermediate ShipContent page. The link carries the workspace ID and a fixed return page. It contains no other URL. After the provider answers, the owner returns to `/{n}/connections` or `/{n}/setup` with one notice. Sign-in does not authorize a channel or a publication. On the Connections page, **Connect** is the same link, and **Manage** shows reconnect, refresh and disconnect.

For Instagram, `start_instagram_connection` saves a request bound to the agent grant. The link carries that request, so the binding stays. Read `get_instagram_connection` to confirm.

For YouTube, the first channel is saved when Google returns it. After a disconnect deletes the stored channel data, every reconnect waits for the owner to confirm the destination. An account with no YouTube channel shows a failure with a create-channel action and a Connect action. Read `get_youtube_status` after either step.

## Review before publishing

`prepare_youtube_publication` returns `reviewUrl` for `/posts/review`. The editor saves the selected video, YouTube title, description and settings in the background. Publishing waits until the current edits are saved. Then the owner selects **Approve and upload** to approve the exact saved video and destination. No separate confirmation checkbox is required. Saving does not upload. The editor reads saved upload progress automatically; failed reads show **Retry**. General hook, caption and call-to-action inputs are not shown for YouTube. For X, `prepare_x_publication` returns `reviewUrl`. The owner approves the exact post. Read `get_youtube_status` or `get_x_status` for saved publication evidence.

## Confirm a schedule

`prepare_post_schedule` takes `requestId`, a future UTC `runAt` and an IANA `timeZone`. With Publish and an `automatic` post it returns `mode: "scheduled"` and a saved schedule, with no review URL. Otherwise it returns `mode: "owner_review"` and `reviewUrl`; the signed-in owner checks and confirms saved content, destination and time. The URL grants no access. Replay the same request ID and input after a lost response, and read `get_post_schedule`. See [schedule confirmation and recovery](/docs/workflows/post-draft#automatic-schedules).

TikTok Accounts follows the same direct connection link at `/connect/tiktok`. The owner authorizes the account at TikTok, then confirms a changed destination in Connections. This connection grants no publication approval. Call `start_tiktok_connection` and read `get_tiktok_status` after the callback.

TikTok video reviews use `/posts/review` with a saved review ID and manifest hash. The owner action verifies the current video bytes and account settings again. Review URLs carry no approval authority. Agents save all draft fields first. With Publish and an `automatic` post, `prepare_tiktok_publication` returns `mode: "queued"`, the saved `operation` and `review: null`. Otherwise it returns `mode: "owner_review"` and `review.url`; the owner checks and approves once. Read `get_tiktok_status` with `postId` to recover `operation.id`, then call `get_tiktok_operation`. The owner can upload directly in Posts or select a video already saved in Media.

The protected `/tiktok` handoff, with `workspaceId` and `reviewId`, reply handoff checks ownership and opens `/[workspace]/tiktok` at that exact review. The owner checks the parent comment, reply text and destination before approval. Agents resume with `get_tiktok_status` using `reviewId`, then `get_tiktok_operation`. Connections opens the same account page for post, thread and performance reads.
