​
Overview

Simnet separates who you are, who owns the resources, and how those resources are grouped. Three distinct concepts, easy to conflate:

​
Tenants

A tenant is the real unit of ownership. Quotas are assigned per tenant, resources belong to a tenant, and users are granted access to a tenant. You manage tenants under Organization → Tenants. If you belong to more than one, a context switcher in the top bar controls which one you’re currently acting as — and that context travels with every action you take, so creating a VM while switched to tenant B creates it in tenant B.
Check your tenant context before creating or deleting anything. The console does not ask for confirmation of which tenant you’re in, and a resource created in the wrong tenant has to be recreated rather than moved.
Tenants were previously called teams, and the older name is still visible in places — a Teams screen remains under Settings for compatibility, and some API paths use “team” where the console says “tenant”. They are the same thing.

​
Projects

Projects group resources within a tenant. Where a tenant is a hard boundary with its own quota, a project is an organizational convenience — a way to see and manage a subset of a tenant’s resources together. Manage them under Settings → Projects.
Project management is partially built. Creating and listing projects works. Assigning existing resources to a project, and managing a project’s plan, are not yet available — both surfaces say so when you open them. Treat projects as a grouping you set up as you create resources, not one you can reorganize after the fact.

​
Users

Organization → Users manages who can access your tenant. Authentication is handled by an external identity provider rather than a password Simnet stores, and what a user can do is driven by the permissions on their account. Administrative permission is a distinct grade: it unlocks platform-wide screens, and it’s also what reveals features still in internal preview. Two people looking at the same account can legitimately see different sidebars.

​
The audit log

Organization → Audit Log records actions taken in your account — what changed, when, and who did it. Where Events track what happened to resources, the audit log is oriented around who was responsible.

​
Choosing between a tenant and a project

Use a separate tenant when the boundary needs to be real: separate quotas, separate billing, or a group that must not see the other’s resources. Use a project inside one tenant when the same team is managing everything and you just want the resources grouped — environments like staging and production being the common case.

Organization

The Users, Tenants, and Audit Log screens.

Quotas and limits

Quotas are assigned per tenant — how to see where you stand.