The tools teams build and maintain themselves
Not every need is a question to answer once. Some things a team needs to build, write down, and keep current — a small internal app, a policy page, a map of how a process actually runs. These give teams that, without turning every request into a ticket for someone else.
The internal app your team keeps asking for
Build a small internal app — a register, a tracker, a log — in a space that can't touch anything real. When it's ready, an administrator reviews exactly what it would change in your database before it goes live. Eight ready-made starting points cover the usual shapes: asset register, approval tracker, inspection log, vendor onboarding, equipment maintenance, CRM, risk register, support ticket.
- Nothing reaches real data while it's being built. Teams can get it wrong safely.
- Every change is shown before it happens, checked against your actual database.
- Nothing to deploy or maintain — runs inside Essential Deck, each screen limited to the right roles.
One place for the pages that used to live in someone's head
Spaces for every department, project, and topic — Company, Departments & Teams, Projects, Products, Policies & Procedures, Technical, HR & People. Pages nest under each other, link directly to one another, and keep their full version history. Viewing is closed by default: a Space is only visible to people explicitly granted access, and an owner can hand off just the job of managing who's allowed to view — without also handing over edit rights.
- Organised the way people actually look — by Space, and by page type: Policy, Procedure, Guide, Reference, FAQ, Announcement.
- Nothing gets lost. Every edit is kept, with one-click restore to an earlier version.
- Closed by default — view access is granted deliberately, never open to anyone signed in.
Map how work actually happens
Document a process as an interactive flowchart — an ordered sequence of Task and Decision steps, branching the way the real process does. Each step can record who performs it, which system it runs in, how long it takes, what it costs, and whether it's value-add, necessary overhead, or waste — so what's worth automating stops being a matter of opinion.
- A flowchart, not a slide — branches where the real process branches.
- Waste and automation potential scored per step, rolling up into where to focus first.
- A lifecycle, not a one-off diagram — Planned, Active, Retired, with newer versions superseding old ones.
Built by the team, reviewed before it's shared
Ownership stays close to the work. Visibility beyond that team is a deliberate choice, not a default.
Findable without being exposed
Apps, Wiki pages, and Processes show up in the home feed, search, and My Work — but only for people already cleared to view them, so discovery never becomes a leak.
An access role of its own
Who can view an app, a Space, or a Process is a role an owner can hand to someone else — separate from who can build or edit it, and reviewable at any time.
See these built around how your teams already work
Much easier to judge against a process or a policy you already have than to describe in the abstract.