diff --git a/packages/docs/cloud/get-started.mdx b/packages/docs/cloud/get-started.mdx index 323d911034..d283a8cc93 100644 --- a/packages/docs/cloud/get-started.mdx +++ b/packages/docs/cloud/get-started.mdx @@ -1,6 +1,6 @@ --- title: "Get started with OpenWork Cloud" -description: "Connect the desktop app to your OpenWork Cloud org and unlock shared workspaces, marketplaces, and shared providers" +description: "Connect the desktop app to your OpenWork Cloud org and unlock marketplaces and shared providers" --- OpenWork Cloud requires an active subscription at [app.openworklabs.com](https://app.openworklabs.com/). @@ -30,7 +30,7 @@ Note: You need to be logged in as an `org_owner` in order to make modifications. 3. Optional: enable `Restrict allowed email domains` and add the approved domains. 4. Optional: change any `Desktop restrictions` that should apply after people sign in from the desktop app. -These settings apply across the org. You can also create teams, share workspaces, publish marketplace plugins, and import shared providers. +These settings apply across the org. You can also create teams, publish marketplace plugins, and import shared providers. Next, you want to make sure you can sign in the desktop app. @@ -67,6 +67,5 @@ After sign-in, pick your org in `Settings -> Cloud -> Active org`. - Send members to [Connect your services](/start-here/connect-your-stack/connect-services) to sign in to team-approved accounts from the desktop app. - Use [MCP Connections](/cloud/share-with-your-team/shared-mcp-connections) to publish a managed service and grant member or team access. - Use marketplace plugins to publish grouped skills and MCPs for teams, or save a single skill directly from the desktop app and install it from `Skills -> Cloud`. -- Use [Shared workspaces](/cloud/run-in-the-cloud/shared-workspace) to deploy hosted OpenWork runtimes that teammates can open from the desktop app. - Use [LLM providers](/cloud/share-with-your-team/managed-llm-provider) or [custom LLM providers](/cloud/share-with-your-team/custom-llm-provider) to manage shared model access. - Use [Members and RBAC](/cloud/members-and-rbac) to invite people, create teams, and control access. diff --git a/packages/docs/cloud/run-in-the-cloud/shared-workspace.mdx b/packages/docs/cloud/run-in-the-cloud/shared-workspace.mdx deleted file mode 100644 index 040e49109b..0000000000 --- a/packages/docs/cloud/run-in-the-cloud/shared-workspace.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "Deploying a shared workspace" -description: "Launch a cloud worker in OpenWork Cloud and open it from the desktop app" ---- - -OpenWork Cloud currently labels shared workers as `Shared Workspaces` in the web dashboard. Once the workspace is ready, the desktop app opens it through the normal remote connect flow. - -## Deploy the shared workspace - -1. Open your org dashboard and go to `Shared Workspace`. -2. Click `Add workspace`. -3. Wait until the status becomes `Ready`. -4. Click `Connect`. - -From the connection drawer you can choose `Open in desktop`, `Open in web`, or copy the `Connection URL` plus `Owner token` / `Client token`. - -## Open it from the desktop app - -From the connection drawer, click `Connect` and copy the `Connection URL` plus -`Owner token` / `Client token`. In the desktop app, choose `Add workspace -> -Connect custom remote`, paste the connection URL and token, then click -`Connect remote`. - -## When to use this flow - -Use a shared workspace when your team needs a hosted OpenWork runtime, a stable place for long-running tasks or messaging connectors, or one workspace that several people can open from the same org. - -## Notes - -- This area is currently marked `Alpha` in the Cloud dashboard. -- A workspace must be `Ready` before the desktop app can open it. -- OpenWork Cloud plan limits apply to hosted workspaces. -- If you prefer to self-host, the desktop [Get Started](/start-here/get-started) guide still works with `openwork-orchestrator`. diff --git a/packages/docs/docs.json b/packages/docs/docs.json index 23d6ec9739..d94a84ba11 100644 --- a/packages/docs/docs.json +++ b/packages/docs/docs.json @@ -39,7 +39,6 @@ "start-here/do-work-with-it/control-the-browser", "start-here/do-work-with-it/cross-chat-memory", "start-here/do-work-with-it/what-uses-tokens", - "start-here/do-work-with-it/workflows", "start-here/do-work-with-it/skills-plugins-and-mcp", "start-here/do-work-with-it/create-a-skill-from-chat", "start-here/do-work-with-it/publish-and-copy-a-skill", @@ -85,12 +84,6 @@ "cloud/share-with-your-team/shared-mcp-connections" ] }, - { - "group": "Run in the cloud", - "pages": [ - "cloud/run-in-the-cloud/shared-workspace" - ] - }, { "group": "Model Context Protocol (MCP)", "pages": [ @@ -150,6 +143,14 @@ "source": "/introduction", "destination": "/cloud/get-started" }, + { + "source": "/cloud/run-in-the-cloud/shared-workspace", + "destination": "/cloud/get-started" + }, + { + "source": "/start-here/do-work-with-it/workflows", + "destination": "/start-here/do-work-with-it/skills-plugins-and-mcp" + }, { "source": "/roadmap/roadmap", "destination": "/roadmap" diff --git a/packages/docs/start-here/do-work-with-it/workflows.mdx b/packages/docs/start-here/do-work-with-it/workflows.mdx deleted file mode 100644 index 9c4727507e..0000000000 --- a/packages/docs/start-here/do-work-with-it/workflows.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: "Workflows" -description: "Use chat and session groups to keep OpenWork organized." ---- - -Workflows are how you turn normal OpenWork chats into organized, repeatable work. In the UI, every session can be renamed, pinned, archived, reordered, or moved into a custom group folder from the session menu. Group folders are workspace-specific: create a group like `Research`, `Ready for review`, `Shipped`, or `Bugs`, then move sessions into that group as the work changes. - -You can also describe the workflow in the composer while you work. For example: `When this is done, rename the session to "Auth cleanup", move it to Ready for review, and pin it`, or `If this turns into a bug investigation, put it in Bugs; otherwise archive it when finished.` Those instructions map to OpenWork's session management primitives: `rename` changes the session title, `move to group` stores a session-to-group assignment, `pin` keeps important sessions at the top, `archive` hides finished sessions without deleting them, and manual ordering lets you arrange sessions and groups around your process. - -This makes session organization dynamic instead of manual bookkeeping. A team can keep groups for `Triage`, `In progress`, `Needs human review`, and `Done`, then ask OpenWork in chat to classify future sessions into those buckets as work completes. The exact groups and actions are configurable from the UI, so the workflow can match how you already work instead of forcing a fixed project-management structure. diff --git a/packages/docs/start-here/get-started.mdx b/packages/docs/start-here/get-started.mdx index 10c4ad03b8..268f37012c 100644 --- a/packages/docs/start-here/get-started.mdx +++ b/packages/docs/start-here/get-started.mdx @@ -28,7 +28,7 @@ Get started by connecting your LLM provider of choice and sending your first mes Start with the desktop app, sign in, connect providers and managed services, and run tasks right away. - Meant for teams: Shared workspaces, org marketplaces, hosted workers, and managed LLM providers. + Meant for teams: org marketplaces, shared MCP connections, and managed LLM providers. Get support with an enterprise deployment if you need a private rollout or custom requirements. diff --git a/packages/docs/start-here/self-host.mdx b/packages/docs/start-here/self-host.mdx index b4ffdb452d..c8349dc243 100644 --- a/packages/docs/start-here/self-host.mdx +++ b/packages/docs/start-here/self-host.mdx @@ -143,7 +143,7 @@ OpenWork does not require many third-party services for the core runtime. These Skip the server. [**OpenWork Cloud**](/cloud/get-started) runs hosted workers for your team. -Cloud also gives you org-wide primitives you'd otherwise have to build: [team templates](/cloud/share-with-your-team/team-templates), [shared LLM providers](/cloud/share-with-your-team/managed-llm-provider), [RBAC](/cloud/members-and-rbac), and [shared workspaces](/cloud/run-in-the-cloud/shared-workspace). +Cloud also gives you org-wide primitives you'd otherwise have to build: [team templates](/cloud/share-with-your-team/team-templates), [shared LLM providers](/cloud/share-with-your-team/managed-llm-provider), and [RBAC](/cloud/members-and-rbac). ## Looking for support for a larger rollout?