ClideyOperational data for care teams, with access kept tight.
Bed capacity, supplies, staffing and scheduling sit in separate systems. WhoDB connects them in place, models the operational picture once and scopes every view to the person looking at it.
In placesource systems stay where they are
Per personaccess on every view and query
Every grantlisted by person or resource
Privatedeployment inside your own cloud
IN THE PRODUCT
Every access grant, in one place.
Pick a point on the left to see where it lives on the screen. Every screen shown here comes from the Clidey ERP demo project.
APP.WHODB.COM / APPS / CAPACITY-BOARDDARK
HOW IT WORKS
From separate systems to one operational picture.
01
Connect the systemsConnect scheduling, supplies and staffing databases in place.02
Model operationsDefine wards, beds, shifts and supplies as shared entities.03
Scope the accessGive each team access to exactly the records it needs.04
Build the viewsOperations teams work in apps that read the shared model.ACCESS
Access you can show to anyone who asks.
Every direct grant is listed by person or by resource, and the AI agent follows the same rules as the person asking.
✓Grants by person or by resource✓Project and team scopes✓Confirmation before consequential actions
Access by resourceOPERATIONS
RESOURCETYPESCOPEPEOPLE
Bed capacityappTeam18 people
WardentityProject9 people
Supply levelsappTeam6 people
staffing.xlsxfileProject2 people
OPERATIONS
Capacity and supplies on one model.
Beds, shifts and stock are related in the model, so planning starts from one current picture.
✓Ward, bed and shift entities✓Supply and stock entities✓Apps on the shared model
Operations model5 NODES
ENTITY
ENTITY
ENTITY
ENTITY
APP
What it changes for each team
OPERATIONSOne current picture.Capacity, staffing and supplies on the same screen.
SUPPLY CHAINStock where it is needed.Supply levels connected to the wards that use them.
IT AND SECURITYAccess you control.Data stays in place, and every grant is visible.
THE DETAILS
For the people who will ask.
The specifics your architects and security reviewers will want before a rollout.
SOURCESScheduling, staffing, supplies and files
ACCESSPer person, per team and per resource
AI AGENTBound by the asking person's permissions
CHANGESDraft, review and promote
DATA MOVEMENTNone required to explore
DEPLOYMENTManaged Private inside your own cloud
EXAMPLE WORKFLOWOne
Operational view across capacity, staff and supplies.Operations teams plan from one model instead of three exports, with access set per person.
Common questions
WhoDB connects to the systems you choose. Many teams start with operational data such as capacity, staffing and supplies.
Keep exploring Industries
Industries overview →01Manufacturing→Testable pricing logic and quote records.02Retail→Allocation plans from your own rules.03Warehousing and distribution→Receiving, put away, picking and stock.04Banking→Customer, account and risk data in one model.05Accounting and finance→Close faster with reconciled, traceable numbers.06Insurance→Policies, claims and pricing on one model.07Logistics and transport→Shipments, fleet and capacity in one place.08Wholesale and trade→Orders from every channel in one model.09Energy and utilities→Assets, readings and work orders connected.