Where one piece of work lives: the data, maps, dashboards and field campaigns that belong together, and the people working on them.
Open ProjectsA project is where one piece of work lives. It gathers the data items, data rooms, maps, dashboards, field campaigns and workspaces that belong together — and the people working on them.
The thing to understand first, because everything else follows from it:
A project references work. It never owns it, moves it, or copies it.
Adding a map to a project does not take it out of Hyz Maps. Removing it puts nothing back, because nothing was taken. Deleting a whole project deletes the project and nothing else.
That is also why the same map can be in several projects at once. A boundary layer used by three jobs is one layer, filed three times.
From Projects → New project. A project needs a name and a URL; both can be changed later, and the description is filled in on the project's own page.
How many projects you can have is a plan allowance, alongside your data items, maps and dashboards. You can see where you stand on the allowances panel at the top of any of those lists.
Open the project and use Add. Pick the kind first, then the thing.
The picker only offers what you can already open yourself. If something you expect is missing, you do not have access to it — ask whoever owns it to share it with you first, then file it.
Items are grouped by kind, so a project reads as four maps, six data items, two dashboards rather than as one long list.
A shared project usually references more than you personally have access to. The index shows what you can open and then says, plainly:
3 more items you do not have access to.
Their names are not shown. That is deliberate — a project must not become a way to read the titles of documents you were never given.
So the item count on a project is the true total, not the length of the list you can see. The two differing is normal.
Two ways, and they do different things.
Groups — the normal way. Attach a group and everyone in it is on the project. Only the group is recorded, so membership stays in the group: remove someone there and they are off every project the group is on, immediately. There is nothing else to update.
Direct invites — for the one person a group would be overkill for. An invitation goes to an email address and is claimed the first time that account opens the project, so you can invite someone before they have an account.
Both carry a role:
| Role | Can |
|---|---|
| Manager | Everything: rename, archive, delete, add and remove items, manage people, and share items |
| Collaborator | Add and remove items |
| Viewer | Read the project and its index |
The owner is always a manager. On a project owned by an organization, anyone who can share for that organization is a manager.
By default, being on a project gives you nothing inside it. Each item is still governed by its own permissions.
A manager can change that one item at a time, with the Shared switch on the item's row. Switch it on and everyone on the project can view that item — view only, never edit, and never manage.
Three things about this are worth knowing:
Switching it off takes the access away again, but it cannot un-see what has already been read. That is why the default is off.
Every object on the platform can tell you what depends on it — including which projects hold it, and how:
You will see this on a data item, a data room, a map, a dashboard, a field campaign, a workspace and a group, and in the confirmation before you delete anything. It is the answer to "what breaks if this goes away".
Archive takes a finished project out of the default list without losing it. It stays readable, and an archived project stops sharing: anything shared through it goes back to its own permissions.
Delete removes the project and its references. Everything it pointed at — every data item, map, dashboard and campaign — stays exactly where it was, owned by whoever owned it. The confirmation says so, because a row reading "12 items" invites the opposite assumption.
A project created by a Hyz AI project session carries an "AI project" chip in the list (filter the list to AI projects) and a note on its page with Open in Hyz AI, which reopens the session that made it — the plan, every step's settings and results — and lets you replay it. It is otherwise an ordinary project: the same references, people and sharing rules, and deleting the session never touches what it filed here.