Permissions

Roles grant permissions resource by resource and action by action, denied by default, with six starter roles for facility management running from local manager to compliance officer. Scopes then decide where those permissions apply: a tree over the estate with country nodes, regional nodes and building leaves, where a grant on any node covers everything beneath it.

Multi-site operators need a local manager to see their own site and a country manager to see their country, without somebody maintaining that by hand every time a building is added. Because scoping follows the estate tree, adding a building to a region grants the right people access to it as a side effect. Denying by default matters when tenant and contractor data sits in the same system as your own records.

In practice

A new country manager for France starts on Monday.

  1. She is given the Country Manager role, scoped to the France node of the estate tree.
  2. That single grant covers every building beneath it. Lyon Sud today, and any French site added later, without anybody revisiting her access.
  3. She sees French work orders, French compliance and French spend. Berlin Nord is not hidden from her by a filter; it is not hers to see.
  4. A contractor working at Lyon Sud is scoped to that one building. He sees the jobs assigned to him. He does not see the compliance matrix or anybody’s costs.
  5. A Belgian site is added under a new Benelux node. Nothing she holds changes, and nobody has to check whether it should have.
  6. A newly created role starts with nothing at all, because permission is denied by default and granted deliberately.

Access follows the shape of the estate rather than a list somebody maintains by hand. That is what stops a growing estate quietly becoming a system where everyone can see everything because it was easier.

Illustrative walkthrough. Not a customer record.

Other Features

Contractors

Contractors and suppliers sit in one central register with their service agreements, their insurance policies and the expiry dates attached to both. When a contractor’s insurance policy expires, Prova stops…
Read more

Cost Management

Costs attach to the work order as lines: invoices, labour and materials, approved, posted, and rolled up by building and by trade. Labour is valued at the rate in force…
Read more

Evidence

Photos attach at the exact place they belong: the finding, the job, the asset. They are captioned, tagged, and stripped of EXIF metadata on upload. Documents are typed and anchored…
Read more

Reliability

When a job closes on a breakdown, Prova captures the closure in a standard shape: problem, cause, remedy, severity and downtime. The vocabulary comes from a failure code catalogue your…
Read more

Estate

Prova organises your estate as a tree. Buildings sit under portfolios you group by owner, fund or region, and each building holds its own units: floors, suites and rooms. Segments…
Read more

Assets

Every piece of critical equipment gets a record: chillers, lifts, alarms, pumps. Each asset carries its category, its warranty, its runtime meter and its complete service history. The asset sits…
Read more

Work Orders

The work order is the unit of work in Prova. A request becomes a job, the job is assigned to a person or a contractor, it is approved, and it…
Read more

Maintenance

A maintenance plan defines a cadence, such as quarterly or the first Monday of the month, and Prova materialises it into dated occurrences across a rolling eighteen-month horizon. When an…
Read more

Next step

See how to optimise your workflow and save money.

Thirty minutes on your own estate: your buildings, your obligations and your numbers. We will show you where the time and the money are going.

Book a demo