Security
Every action stays within its role.
Control who can access data and which actions people and assistants can take.
Permissions: prices
Assistant tried to edit prices: blocked.
Where general tools stop
Vibe coding
A vibe-coded app usually starts with one login and full access. Rights added later are easy to get wrong, and each new app has to get them right again.
ChatGPT or Claude
ChatGPT or Claude have admin settings for the tool itself. They do not know that your sales team may see prices but not change them.
The problem
The moment AI works with real data, the question is no longer what it can do, but what it may do. A price list, a salary or a customer file should not be open to whoever happens to ask.
The solution
Nova applies one set of roles and permissions to people and assistants. Actions outside a role are refused, and everything that happens is written down.
Try it yourself
See it on screen.
Interactive example with sample data
Roles
Who may do what with prices
What is happening
What you get
- Roles and groups, with rights per type of record: view, edit, approve.
- Assistants never have more rights than the person they work for.
- An audit trail with who, on whose behalf, what changed and which approval.
Per project we specify which parts already exist, which are configured, which are integrated and which are newly built.
Use cases
See what this looks like in practice.
Food manufacturing
Truck tours planned from the day's orders
Large public events
One platform for every volunteer and crew member
Events and sponsorship
From raw survey data to a verified report
Building technology
A sales workspace from first call to order
Construction and fire protection
From building model to a reviewed quote list
Insurance
Product benchmarks that stay up to date
Insurance
Every new lead answered with a first analysis
Insurance
Claims-history certificates without the spreadsheet