Organizations and projects
Ngenaire has two layers of grouping: organizations and projects. Understanding the relationship helps you decide where to invite people and how to structure your work.
Organizations
An organization is a tenant — typically a company, a department, or a customer engagement. Each organization is isolated: its members cannot see another organization's data unless they are also invited there.
A user can belong to multiple organizations. Use the organization switcher in the top bar to move between them.
What lives at the organization level:
- Members and their organization-level roles.
- Projects owned by the organization.
- Settings — the organization's display name.
- Invitations sent to new members by email.
Organization owners and admins manage membership and send invites. See Organization settings and Invite members.
Projects
A project is a single system, product, or program — for example, "Mars Rover Navigation" or "Customer Portal v3". Every engineering artifact lives inside a project:
- Requirements, baselines, and change requests.
- CONOPS, SOW, and trade studies.
- Diagrams, data-flow diagrams, and 3D models.
- Test plans, procedures, executions, and reports.
- Schedule, risks, issues, and project memory.
Each project has its own member list, and project membership is separate from organization membership. You can be an organization member while only being a viewer on a particular project — or not a member of it at all. See Roles and permissions for what each role can do.
Why two layers
The two-layer model lets you:
- Share one organization across multiple teams while keeping each team's projects separate.
- Bring an external collaborator (a customer or contractor) onto a single project without exposing every other project.
- Apply different governance per project — one project can be locked for an audit while another is in active development.
How AI usage is billed
This is the most important billing fact to understand:
Credits are owned by the user, not the organization. Whoever runs an AI action pays from their own credit balance, no matter which organization's project they are working in.
So if you run the AI Assistant, generate a report, or run a critique inside a colleague's organization, the credits come out of your balance — not the organization's. Manage your own balance and plan on the Billing page.
Switching context
The organization switcher in the top bar shows your current organization. Switching organizations reloads the sidebar with that organization's projects. Selecting a project loads its lifecycle pages and data.