# connect-cloud-partition — Connect lists cloud-runnable capabilities and Extensions stays local

Cast is Alex, the Acme Robotics admin, using the OpenWork desktop app against the local Den stack. The proof seeds one organization marketplace with a ready cloud skill, one plugin that still needs an admin MCP connection, one desktop-only plugin, and one per-member team connection.

1. Alex opens Connect with the organization capability enabled. The From your organization list is grouped, Ready to use contains the seeded cloud-ready plugin, and the desktop-only plugin is absent from the entire Connect page.

2. Alex reviews the Needs your sign-in group. The per-member team connection appears there with a Connect action, showing that personal sign-in work is separated from already-ready capabilities.

3. Because Alex is an admin, Connect also shows Needs admin setup. The plugin with an unmatched MCP dependency appears with the setup affordance that sends admins to Cloud connection management.

4. Alex switches to Extensions and opens Marketplace. Organization marketplace plugins are absent there now — including the desktop-only seed — because legacy Extensions only keeps local/built-in affordances while marketplace delivery runs through Connect.
