Organizations and seats

What an organization is¶

An organization is an account container for a company, a government body, an academic institution or an NGO. It holds people, its own data, its own API keys and its own governance settings.

It is not a separate tenant. Everyone still signs in with their own account and keeps their own library; the organization is what lets work be owned by the body rather than a person, so it survives that person leaving.

Seats are not memberships¶

This is the distinction that catches people out.

	What it means	Grants Enterprise?
Organization membership	You are listed in the organization with a role — owner, admin, editor, contributor or viewer — governing what you may do to its resources.	No
Seat	You own an active organization, or you hold an active member row on its tools subscription.	Yes

A seat is an entitlement that costs the organization something; a membership row is bookkeeping. So being added to an organization does not silently upgrade your personal plan.

The console¶

The console at /enterprise/console is where an organization is run:

• Members — who may run Haiyz tools charged to the organization, with a role, a status and an optional per-member credit cap.
• API keys — server-to-server credentials, their scopes, expiry and IP allow-list, plus rotation with a grace period.
• Usage — runs, credits and data volumes, by member, by tool and by key.
• Governance — the confidentiality policy members acknowledge before opening organization workspaces, and the defaults every map sheet starts from.
• Audit log — every key, member and subscription change: who did what, when.

Organization-owned data and sheet defaults¶

Data can be owned by the organization rather than by a person. Such resources are metered against the organization, not the uploader, and resolve to the Enterprise column of the limits table by definition.

Two kinds of shared template come with that:

• Organization map templates — a map flagged as a template, so colleagues start new work from an approved arrangement instead of a blank canvas.
• Sheet defaults — the classification text, its printed colour and the entity name every print sheet pre-fills with. Set once in Governance.

Neither carries data: a template is an arrangement, and the map you build from it is your own.

API keys¶

The Enterprise GIS API is how a pipeline calls Haiyz without a browser. Keys are created in the console, belong to the organization rather than a person, and are metered against its pool over a fixed usage window.

Secrets are shown once, at creation. Rotation issues a replacement and keeps the old key working for a short grace period.

The full reference — authentication, the response envelope, idempotency keys, the tool catalog and the error codes — is in the API documentation.

How a member's plan resolves¶

One resolver answers this for the whole platform, in this order:

1. On an Enclave instance, everyone is Enterprise. The server belongs to the customer; there is nobody to sell a tier to. See Haiyz Enclave.
2. Platform administrators are Enterprise — not exempt. They meet the same walls a customer does, or the walls are never tested.
3. A seat holder is Enterprise.
4. Otherwise your own membership decides — Plus, Basic, or Free.

Separately, anything owned by an organization is governed as Enterprise, whoever created it.

Good to know¶

• A membership row is not a seat. If a colleague's plan did not change after being added to the organization, this is why.
• The seat check is live, never stored, so nothing goes stale when a seat is removed.
• Removing a member frees the seat at once. Runs already in flight finish; new ones are refused.
• Organization-owned things are metered against the organization, not against your personal storage allowance — see Plans & limits.
• Keys are server-side credentials. Never ship one in browser code; scope it to the tools it needs and give it an expiry.