Organizations and projects
You manage organizations and projects in CrossXWeb, the browser companion, then open a project in the desktop app to build. This guide covers the everyday flow.
For the split between the two surfaces and how the handoff works, see Desktop and web.
Where things live
Section titled “Where things live”| Thing | Where it lives | What you do there |
|---|---|---|
| Organization | CrossXWeb | Create, invite members, manage teams. |
| Project | CrossXWeb | Create inside an org, set its defaults. |
| Infrastructure canvas | Desktop app | Build, Plan, Apply. The web canvas is read-only. |
You create orgs and projects in the browser, then move to the desktop app to actually draw infrastructure. CrossXWeb never holds cloud credentials and never makes provider calls. It hands off to the desktop app for that.
Create an organization
Section titled “Create an organization”In CrossXWeb, create an organization. You can invite team members and manage them through the org’s teams.
Create a project
Section titled “Create a project”Inside an organization, create a project. A project is the container for one piece of infrastructure: its canvas, its history, and its connection to a provider.
The project is the unit you open in the desktop app.
Open a project in the desktop app
Section titled “Open a project in the desktop app”With a project selected in CrossXWeb, use the “Open in Desktop” action. CrossXWeb issues a short-lived signed deep-link and the OS opens the CrossXCloud desktop app, navigated to that project.
The deep-link carries enough context for the desktop app to know which org and project you opened, and a token that lets it authenticate. You do not need to sign in again in the desktop app.
See Desktop and web for how the handoff works end to end.
What happens after the handoff
Section titled “What happens after the handoff”The desktop app opens with your project loaded. If live infrastructure exists for the connected provider, CrossXCloud reads it and lays it out as the starting canvas. From there, everything you do follows the Plan and Apply loop.
- Desktop and web for the two-surface model.
- Your first canvas for what to do after the handoff.
- Version history for how the desktop app’s commits flow back to the web viewer.