headline
accounts / team
Team members, with roles that match the job
An account used to be one login. It is now a team, and each member gets a
role built around a real function rather than a generic level of access. A back-office person handles invoices
without touching vendor configuration, and a technician configures vendors without setting prices.
Sales roles own the chain, price books and margins.
Back-office roles own invoices, month-close and the order lifecycle.
Technical roles own vendor connections, provisioning and services.
Viewer roles read everything and change nothing.
Only the Admin role manages the team. Ownership of the
account is separate from any role, so transferring it is a deliberate act rather than a permission someone
can be handed by accident.
onboarding
accounts / invitations
Invite someone, and let them set their own password
Adding a colleague is an invitation, not an account handover. They receive a
link, choose their own password and land straight in the product.
No password ever travels by email. New members set theirs
through a single-use link that stops working the moment it is used.
An optional mobile number lets a member sign in with a
one-time code from their very first login.
Seat allowance is visible before you invite, so you see how
much room the account has instead of finding out when it refuses.
Invitations expire on their own and free the seat they were
holding. A lapsed one can be re-sent.
security
accounts / access
Access changes take effect immediately
When someone leaves a team or moves to a different role, the change applies
at once rather than whenever their session happens to end.
Deactivating a member ends their active sessions across every
device they were signed in on.
Changing a role does the same, so a narrowed permission set
cannot be worked around by staying signed in.
Account admins can review their own team's activity from a
dedicated tab, scoped to their organisation and nobody else's.
integration
integrations / crm
Sales orders can arrive from a CRM
Partners who run their sales process in a CRM no longer have to re-enter
orders. The platform accepts them from the CRM and keeps the two sides reconciled, so the order, its items and
the customer record stay in step.
Orders, line items, products and accounts all map across.
The platform reads the authoritative record rather than
trusting a partial notification.
Reconciliation converges on the intended total instead of
applying differences blindly.
Groundwork for wider ERP work already on the roadmap.
reporting
private cloud / usage
Private cloud usage, by period and by peak
The private cloud view now reads as a time series rather than a single frozen
month, and a reseller sees the slice of the estate assigned to them.
Billing periods replace the one-off snapshot.
Peak tracking alongside averages, so spikes are visible.
Per-customer breakdown with export.
Assignment to a reseller controls who sees which customers.
