LoadingHow it works
CleverHive does not ask you to configure a platform before you get anything out of it. You pick what you need, and it asks only for the parts of your organization that application actually uses.
The shape of it
Each stage sets up something the next one uses. None of them is repeated when you add your second application.
Start from the problem, not from a platform. Browse the catalogue, read what each application would ask of your business, and pick the one you need. Nothing forces you to take a suite.
Every application in the catalogue is under development today, so this is the step you can read but not yet finish.
One account for the business, then the locations you operate from. Most businesses begin with a single branch and add more as they grow — a second outlet is a branch, not a second subscription.
Everyone who works for you goes on the staff list, whether or not they ever sign in. A role says where someone sits in the business; job roles layer the specifics on top.
Access is decided once and honoured by every application. It is checked on the server on every request — against membership, permission and the branch being acted on — and nobody can grant more than they hold themselves.
Access check
Re-checked on every request, never cached in the session.
The applications you switched on are live for the people who need them, at the branches that use them. The next one joins the same organization — there is nothing to set up twice and nothing to migrate.
Organization
Your business
Your applications
CRM
CCTV
Chat
eSign
Forms
Tasks
Barcode
Budgets
Courses
Four separate states
Most platforms treat these as one thing. Keeping them apart is what lets a business own an application, run it at three of its five branches, and give two people access to it.
All four are checked on the server, on every request. A browser that claims otherwise gets a different set of screens and exactly the same refusals.
Your business has a subscription to the application. That is a commercial fact and nothing more — it does not put the application in front of anybody.
You set it up for your organization. Owning something you have not installed is normal: you bought it, and you have not switched it on yet.
Switched on at the locations that use it. A business with six outlets may run point of sale at four of them, and that is a setting, not a workaround.
Whether this particular person may do this particular thing. Checked on the server every time, against their role and the branch they are acting on.
The journey
The same five stages, with nothing left out. This is what actually happens, in order.
Browse the catalogue and find the application that solves the problem in front of you.
Read what it does, what it would ask of your organization, and which industries it suits.
One account for the business. You become its owner.
Name it, set its currency and timezone. This happens once.
A location you operate from. Everything else hangs off it, and most businesses start with one.
Everyone who works there. A login is optional — most staff never need one.
Say who works with it, at which branch.
What each person may do. Decided once, honoured by every application.
The application is live for the people who need it, and nobody else.
Add the next application when the business needs it. It joins the same organization.
Free trial
Described rather than offered, because it does not exist yet.
A free trial will let you open an application and use it against demo data, without creating a business account first — so you can see what it does before deciding anything.
It opens when the first application is genuinely finished. Every one in the catalogue is still under development, and a trial of something unbuilt would be a demonstration of nothing.