Two different actions - both useful for a client simulation:

AI workshop (build before deploy)

Consultants often author on personal, then Publish & placement to the client portal:

1. Personal shelf named for the project (e.g. "Lake Assoc - WIP").
2. AI via Studio key or ChatGPT OAuth (personal scope).
3. Review in Reader; deploy when ready.
4. After move → portal Integrations key for further AI edits.

→ AI workshop workflow

Save to your library (personal)

• What: Bookmark while reading → appears on Saved in Reader.
• Who sees it: Only you.
• Use for: Reference while testing; AI reference mode with /g/{slug}/gdf URLs.

Add to your portal channel (org hub)

• What: Syndicate a public, completed guide into a channel on your portal.
• How: Reader → fork icon (Add to channel) → pick your portal's channel.
• Use for: Simulating "client publishes a doc library to their team."

Try this after creating your portal:

1. Add Connecting AI to Guides and this guide to your portal channel.
2. Generate an org API key at Portal → Settings → Integrations.
3. Ask AI to list catalogs with each key - personal vs portal scope should differ.

When you need an org-owned copy: import GDF with the portal key - not just syndicate.