Hodoflow nests your work two levels deep. An organization is the account — usually one per company — and it is the hard boundary that keeps your data away from everybody else's. A workspace is an environment inside that organization, so you can keep production separate from whatever you are still experimenting with.
The rule worth learning first: workspaces partition data, not people. Any active member of the organization can reach every workspace in it. If you need a genuinely separate set of people, that is a separate organization.
Choose your next task
- Invite people and set roles — who can do what, and how access is taken away.
- Organize work into workspaces — separate staging from production inside one organization.
- Organizations and trials — switching between organizations, renaming, ownership, and what happens when a demo ends.
- Service accounts — access for software rather than people.
Where everything lives
| Setting | Page |
|---|---|
| Organization name, ownership, plan usage | Settings → Organization |
| Workspaces | Settings → Organization → Workspaces |
| People, invitations, roles | Settings → Users |
| Machine credentials | Settings → Service Accounts |
What belongs to a workspace
Whatever you build belongs to the workspace you were in when you built it — its workflows, dashboards, widgets, data models, connectors, imported API Specs, and credentials. Switching workspaces switches all of it at once.
The organization and workspace you are working in come from the pickers in the top bar, not from the address you visited, so there is no URL to memorize or share.