One organization, shared by everything you switch on

The structure an application joins when you add it. Set up once, by you, and never again per tool.

What it does

What this does today

Each of these is working and covered by tests.

Your business is one account. Every application reads the same organization rather than keeping its own copy of your staff list.

Adding an application does not mean re-entering who works for you, or discovering later that two tools disagree about it.

Every location you operate from. Applications are switched on branch by branch, and people can be scoped to the ones they work at.

A second outlet is a branch, not a second subscription. Someone who runs one location sees that location.

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.

A kitchen porter belongs on the staff list without being given a dashboard, and paying per user should not mean paying for people who never open it.

Added when the business needs them, from one approved catalogue. Each declares what it would ask of your organization before you install it.

Owning an application, installing it, making it available at a branch and permitting a person to use it are four separate decisions.

Things that happen in the platform — a branch added, someone invited — reach the people permitted to see them.

Each notification is filtered by the same permission rules as the page it points at.

Every change records who made it and when, written in the same transaction as the change itself.

The trail cannot disagree with what happened, because a change that rolled back leaves no entry.

The rest

Available and planned, kept visibly apart.

Get started

Organization, branches, people, roles and permissions all work now. The applications join them as they ship.