Multi-tenant & permissions
Every customer in its own branch.
Resellers, clients and sub-clients live in one tree. Each sees its own branch and what is below it, with permissions set page by page and action by action.
Permissions
Exactly the access each person needs.
Scope by branch
An organisation sees its branch of the tree. Widening one customer’s view never widens anyone else’s.
Page by page, action by action
Roles come from permission templates that set each page and each action.
Admin, member, demo
Admins run the organisation, members work in the pages granted to them, demo users can only read.
No escalation
Nobody can grant more than they hold themselves.
Always an admin
Every organisation keeps at least one admin, so access never hangs on one account.
Suspend in one switch
Suspending a customer stops its users, its charging authorisations and its stations at once.
View as customer
Help your customers from their own screen.
Your team can open the console exactly as a customer sees it. Every change made that way is recorded as made on the customer’s behalf.
- The customer’s own viewThe same pages, data and permissions the customer has.
- Recorded as helpThe audit trail shows who acted, and on whose behalf.
- Every page has a ruleEach page and action in the console has an explicit permission rule.
View as customer
Open the console as the customer sees it.
Audit trail
Changes recorded as made on their behalf.
Who uses it
Built for businesses with customers.
Questions
Multi-tenant and permissions, answered.
How deep can the tree go?
Clients can have sub-clients, and resellers can have their own customers below them. Each level sees its own branch.
Can I create my own roles?
Roles come from permission templates, which set access page by page and action by action.
What happens when my team helps a customer?
They use view as customer, and every change is recorded as made on the customer’s behalf.
Give every customer its own space.
Tell us how your customers are organised and we’ll show you the tree.
Book a demo