An enterprise has a tier and people. The tier decides how much each person may hold and run; the user type an administrator gives each person decides what they may do. This page puts it together: the products, the tiers, the user types, one table saying which type may do each thing, and how people are added.
The table is not written by hand. Every tick is read from the platform's own permission model when the documentation is built, and the build fails if the two disagree — so nothing here can promise something the product refuses.
Products¶
Everything in the list is one platform and one sign-in — a layer published in one is the layer the others read.
- Hyz Workspace — Load your layers, run the analysis, share the result — in the browser. from Contributor
- Hyz Maps — Publish an interactive map your teams or the public open by link. from Creator
- Hyz Dashboards — Operational dashboards over your data — indicators, charts and a map that filter each other. from Creator
- Hyz Field — Send crews out with a form, capture offline, review what comes back. from Contributor
- Hyz Data Items — Your enterprise's data as items people can open, download, edit and version. from Contributor
- Hyz Services — Turn a layer into tiles, features and OGC endpoints other systems can call. from Publisher
- Hyz Catalog — One index of everything published — searched in Arabic and English. from User
- Hyz Data Rooms — Hand a data item to a party outside the enterprise, with an access log. from Creator
- Hyz AI — Describe the dashboard, the map style or the layer you want and review what it proposes. from Contributor
- Hyz Console — Members, roles, sign-in, seats, applications and the audit log for the whole enterprise. from Security administrator
- Hyz API — Call the same geoprocessing from your own systems. from Administrator
- Hyz Desktop — The native workbench with a local engine, for the heavy work. from Contributor · coming soon
- Hyz Earth — A globe for the data you already publish — briefings and flythroughs rather than a workbench. from User · coming soon
Tiers¶
Four tiers set how much a person may hold and run — data items, storage, maps, dashboards, tool runs, AI requests and API calls. The numbers each tier carries are in Plans & limits.
- Free — Every signed-in account starts here.
- Basic — More of everything, for a person working on their own.
- Pro — For daily professional work, with API keys of your own.
- Max — The widest allowance: nearly every limit is unlimited.
Which tier a person holds¶
- An enterprise is given one of the four tiers. Every member holds the higher of their own tier and their enterprise's, whatever their user type; leaving the enterprise returns them to their own.
- Usage is counted per person, never pooled: a colleague's use never spends yours.
- What the enterprise itself owns, and what its API keys run, is measured on the enterprise's tier.
- On a self-hosted installation the licence names the tier everyone holds.
User types¶
These are the roles an administrator assigns in the Console. Two more exist and are not seats you buy: the enterprise's owner, and any custom role your administrator writes.
- User — Opens and downloads what the enterprise has shared with them. Changes nothing.
- Contributor — The field and data-entry seat: adds and edits records, uploads a new version, creates a data item or a workspace.
- Creator — Makes the things people open — maps, dashboards, campaigns and data rooms — and shares them inside the enterprise.
- Publisher — Everything a Creator does, and decides what leaves the enterprise: publishes a layer, a service or a map.
- Content manager — Answers for the enterprise's content as a whole — publishes, deletes, and transfers ownership when someone leaves.
- Security administrator — Members, roles, sign-in and the audit log. Reads content but does not author it — the split that lets you separate the two duties.
- Administrator — Both halves at once: everything the content manager and the security administrator hold, and the enterprise's API applications.
What each user type may do¶
Read across a row to see which seats include it. A blank is a refusal the product enforces, not a limit we chose for this page.
Open and read¶
|
User |
Contributor |
Creator |
Publisher |
Content manager |
Security administrator |
Administrator |
| Open a data item shared with them |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
| Download the data behind it |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
| Open a map |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
| Open a dashboard |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
| Open a data room |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Collect and edit data¶
|
User |
Contributor |
Creator |
Publisher |
Content manager |
Security administrator |
Administrator |
| Add records to a layer |
— |
✓ |
✓ |
✓ |
✓ |
— |
✓ |
| Edit and delete records |
— |
✓ |
✓ |
✓ |
✓ |
— |
✓ |
| Upload a new version of a data item |
— |
✓ |
✓ |
✓ |
✓ |
— |
✓ |
| Create a data item |
— |
✓ |
✓ |
✓ |
✓ |
— |
✓ |
| Create a workspace and run analysis |
— |
✓ |
✓ |
✓ |
✓ |
— |
✓ |
Make maps, dashboards and campaigns¶
|
User |
Contributor |
Creator |
Publisher |
Content manager |
Security administrator |
Administrator |
| Create a map |
— |
— |
✓ |
✓ |
✓ |
— |
✓ |
| Create a dashboard |
— |
— |
✓ |
✓ |
✓ |
— |
✓ |
| Create a field campaign |
— |
— |
✓ |
✓ |
✓ |
— |
✓ |
| Create a data room |
— |
— |
✓ |
✓ |
✓ |
— |
✓ |
| Make a layer editable, and lock its features |
— |
— |
✓ |
✓ |
✓ |
— |
✓ |
| Share inside the enterprise |
— |
— |
✓ |
✓ |
✓ |
— |
✓ |
Publish outside the enterprise¶
|
User |
Contributor |
Creator |
Publisher |
Content manager |
Security administrator |
Administrator |
| Publish a layer |
— |
— |
— |
✓ |
✓ |
— |
✓ |
| Publish a data item as a service |
— |
— |
— |
✓ |
✓ |
— |
✓ |
| Share a published service by link |
— |
— |
— |
✓ |
✓ |
— |
✓ |
| Publish a map to the public |
— |
— |
— |
✓ |
✓ |
— |
✓ |
Administer the enterprise¶
|
User |
Contributor |
Creator |
Publisher |
Content manager |
Security administrator |
Administrator |
| Create API applications and keys |
— |
— |
— |
— |
— |
— |
✓ |
| Delete the enterprise's content |
— |
— |
— |
— |
✓ |
— |
✓ |
| Transfer ownership to someone else |
— |
— |
— |
— |
✓ |
— |
✓ |
| Invite, suspend and remove members |
— |
— |
— |
— |
— |
✓ |
✓ |
| Assign roles and write custom ones |
— |
— |
— |
— |
— |
✓ |
✓ |
| Configure sign-in, SSO and directory sync |
— |
— |
— |
— |
— |
✓ |
✓ |
| Read the audit log |
— |
— |
— |
— |
— |
✓ |
✓ |
Seats¶
Every paid user type takes a seat of its own type; a User takes none. On Haiyz Cloud your enterprise has a seat limit; on a self-hosted installation the licence says how many people of each paid type you may have. When none of a type is left, giving someone that type is refused.
|
User |
Contributor |
Creator |
Publisher |
Content manager |
Security administrator |
Administrator |
| Takes a seat |
— |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
The enterprise's owner takes an Administrator's seat, and a custom role a Creator's.
Adding people¶
An administrator adds people from the Console's Members page.
- Invite by e-mail, one or many at once, with the user type they will hold.
- Single sign-on and directory sync — people arrive from your identity provider or directory with the type their group maps to.
- Create account (self-hosted installations only) — e-mail, name and user type. The seat is checked first; the person is sent a welcome e-mail and signs in with a one-time code, and may set a password later.
Connects to what you already run¶
None of these is a separate purchase.
- Single sign-on (SAML and OpenID Connect) — Your identity provider issues the session. Active Directory, Entra ID, Okta or anything speaking SAML 2.0 or OIDC.
- Directory sync (SCIM) — Members and groups arrive from your directory, and a person removed there loses access here.
- Linked services — Read an Esri REST or OGC service you already publish as a live layer — no copy, no scheduled export.
- Open standards out — What you publish is readable by any desktop or web client that speaks WMS, WFS, OGC API Features, or vector tiles — no adapter of ours in between.
- Power BI connector — Pull a published Hyz service into a Power BI report as a refreshing table and map. (coming soon)
Where it runs¶
The same products, the same tiers and the same user types. Where it runs decides where the data sits and who sets the tier.
- Haiyz Cloud — We run it, with the data in the Kingdom. Haiyz gives your enterprise its tier and seat limit; upgrades arrive when they ship.
- Haiyz Enclave — You run it, on your own servers, with no outbound connection required. Your licence names the tier everyone holds and how many people of each paid type you may have. Available on a quarterly release channel; installs are scheduled with us.
How to read this page¶
Every tick is read from the platform's authorization model when the documentation is built, and the build fails if the two disagree. If a row here says a user type may do something, the product will let them; if it is blank, the product returns a refusal.