Organizations and Projects
Organizations and Projects

Structure organizations, folders, projects, and branches for team-scale architecture work in IOModel Studio.

IOModel scopes architecture work in layers: an organization for the team, folders to group related projects, projects for each product or domain, and branches when multiple contributors edit the same cloud project in parallel.

Organization home — Projects tab with folders, project rows, and the New menu

Onboarding a new team? Walk through Create Project and Teams and Access once, then reuse them as your standard provisioning checklist.

Section map

Hierarchy

Organization → folder → project → branch → content

LayerHoldsExample
OrganizationMembers, groups, folders, projectsIOModel Tech
FolderRelated projects (may nest)examples
ProjectModel, specs, artifacts, membersIoT Gateway
BranchCommits and a working copymain, feature/alerts
ContentYAML, MDX, generated artifactsobjects/gateway.yaml

Hosted in IOModel Studio. Branches, commits, and collaboration apply. Open any cloud project from the org Projects tab.

Create the project

Create Project or First Project. Choose a stable key before links and automation depend on it.

Verify the seed tree

Open Specs and Explore. A new cloud project includes branch main, a model skeleton, and spec common/welcome.

Assign access before editing

Add members or groups at folder or project scope. See Teams and Access.

Define branch policy

Treat main as reviewed canonical state. Use feature branches for non-trivial work. See Branches.

Before you start

  • Membership in an organization (or a local workspace).
  • Editor or higher on the target project — creation and edit controls are hidden for viewer.
  • Org admin (org_owner / org_admin) or folder admin to create projects at that scope. Org admins have owner access to every project in the organization.

Decide folder layout and project keys early. Renaming later breaks URLs, published links, and CI references.

Last updated on