What an enterprise changes: seats, the console, shared templates and entitlements.
An enterprise 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 enterprise is what lets work be owned by the body rather than a person, so it survives that person leaving.
Three things, and they answer different questions.
| What it decides | Where it comes from | |
|---|---|---|
| Tier — Free, Basic, Pro or Max | How much: data items, storage, maps, tool runs, API requests | Haiyz gives the enterprise a tier; every active member holds the higher of it and their own |
| User type — User, Contributor, Creator, Publisher, Content manager, Security admin, Admin | What: read, edit, make, publish, administer | The enterprise's administrator assigns it in the Console |
| Seat | How many people of the paid types the enterprise may have | On Haiyz Cloud, the enterprise's seat limit; on a self-hosted install, the licence's count per paid user type |
A User needs no seat. Usage is counted per person, never pooled: joining an enterprise raises your tier while you are a member, and leaving returns you to your own.
The Console is where an enterprise is run:
Editing the confidentiality text bumps its version and re-asks everyone for acknowledgement. That is deliberate — a policy nobody re-read is not a policy.
Data can be owned by the enterprise rather than by a person. Such resources are metered against the enterprise, not the uploader, on the enterprise's own tier.
Two kinds of shared template come with that:
Neither carries data: a template is an arrangement, and the map you build from it is your own.
The Enterprise GIS API is how a pipeline calls Haiyz without a browser. Keys are created in the Console under an application, belong to the enterprise rather than a person, and run on the enterprise's tier: its tool runs per window and its API requests per day. Fixed limits apply too: 60 requests a minute per key, 4 runs at once per enterprise, 50 MB in per request, results kept 90 days.
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.
A Tool API is a narrower way in: one tool with its settings and a reference layer fixed, called with a key of its own that opens that one call and nothing else. Its calls count against the same API requests a day. See Tool APIs.
One resolver answers this for the whole platform, in this order:
Separately, anything owned by an enterprise is metered on the enterprise's tier, whoever created it.