Features
The part that does not change when you add an application
Applications come and go as a business grows. The organization underneath them — who works here, where, and what they may do — stays. That foundation is what CleverHive is.
Business management
One structure, shared by everything you switch on
This is what an application joins when you add it. It is set up once, by you, and never again per tool.
Organization
One account for the business. Every application reads it.
Branches
Each location you operate from. Applications switch on per branch.
People
Everyone who works for you — most of whom never sign in.
Roles and permissions
What each person may do, decided once and honoured everywhere.
One organization
Your business is one account. Every application reads the same organization rather than keeping its own copy of your staff list.
Branches
Every location you operate from. Applications are switched on branch by branch, and people can be scoped to the ones they work at.
People, separate from logins
A person is someone who works for you. A login is an account they may or may not have. Most staff never sign in, and the directory holds them anyway.
Applications
Added when the business needs them, from one approved catalogue. Each declares what it would ask of your organization before you install it.
Security and access control
Permission is checked on the server, on every request
Not once at sign-in, and never in the browser. Each of these is working today and covered by tests — nothing on this list is a plan.
Roles and permissions
One role per person for their place in the business, plus job roles layered on top. Every action is checked against them on the server.
A ceiling nobody can exceed
Nobody can grant access they do not hold themselves. The check runs inside the same database transaction as the change.
Access recalculated every request
Membership, role, branch scope and entitlement are re-read on every call. Nothing about permission is stored in the session token.
Audit
Every change records who made it and when, written in the same transaction as the change itself.
Tenant isolation
One organization can never read another’s data. It is enforced in the database itself, not only in application code.
Notifications
Things that happen in the platform — a branch added, someone invited — reach the people permitted to see them.
In detail
Every part of the platform, on its own page
Three of these describe software that is running today. Four describe intentions, and are marked so you never have to guess which is which.
- Platform featuresThe structure an application joins when you add it. Set up once, by you, and never again per tool.
- Business managementCleverHive does not manage your business for you. It holds the facts every application needs about your business, so none of them has to ask you again.
- Security and access controlNot once at sign-in, and never in the browser. Each of these is working today and covered by tests — nothing on this page is a plan.
- AI and automationRules that act when something happens, and assistance inside the work rather than beside it.
- Reporting and analyticsThe advantage of one organization is that a report can cross applications without an integration project. That advantage is not built yet.
- IntegrationsA business platform that cannot talk to anything else is another silo. Integrations are planned and none is built.
- Developer capabilitiesThere is no public API, no SDK, no sandbox and no partner programme. This page says so rather than leaving the question open.
Get started
The foundation is ready. Set yours up today.
Organization, branches, people, roles and permissions all work now. The applications join them as they ship.