Two different actions - both useful for a client simulation:

Save to your library (personal)

• What: Bookmark while reading → appears on Saved in Reader.
• Who sees it: Only you.
• Content: Live link to the publisher's guide (updates when they update).
• Use for: Your own 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: Open the guide in Reader → fork icon (Add to channel) → pick your portal's channel.
• Who sees it: Portal members on that channel shelf.
• Content: Still the original guide (not a duplicate) unless you explicitly copy/import.
• 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's default channel.
2. Open your portal hub - confirm members would see those guides on the shelf.
3. Generate an org API key at Portal → Settings → Integrations (separate from your personal Studio key).
4. Ask AI to list catalogs with each key - personal vs portal scope should differ.

When you need an org-owned copy (client owns the bytes): import GDF via Studio or POST /api/gdf/v1/guides with the portal key - not just syndicate.