App template · Internal ops
Asset Register
Add to workspaceEvery laptop, monitor and desk the company owns: who has it, where it is, and what it has cost since.
What arrives
One click puts all of it in your workspace, wired together. Rename anything afterwards — the pages, boards and Flows read the columns, not a copy of them.
- 2
- Tables
- 3
- Pages
- 1
- Form
- 5
- Sidebar entries
Asset Register
Asset Board
Every asset by where it is in its life. Drag a card to move it.
The tables
Assets
One row per physical thing the company owns and someone is responsible for.
- Custodianlinks
- Repair Spendadds itself up
- Category
- State
- Asset Tag
- Name
- and 6 more
Maintenance Log
One row per thing that happened to an asset — a repair, a reassignment, a note.
- Assetlinks
- Kind
- Status
- What happened
- Logged
- Cost
What people open
- Record page{{$row.name}}
- BoardAsset BoardEvery asset by where it is in its life. Drag a card to move it.
- DashboardAsset Dashboard
What runs
Each of these is a Form and the Flow behind it. Steps wait for a person; Rules decide which person, on what the row says.
Repair Approval
Someone submits the formReport a fault on an asset. Anything quoted above the delegated limit waits for IT Ops to decide repair or replace; everything else goes straight into the asset's history.
1 Step · 1 Rule · ends on Repair Approved and Replace Instead
Before you add it
This app shares your workspace's Employees table rather than making a second copy of it. If you have one with name and email, it is used; if you do not, it is created for you.
What it is
A body of records a team works inside, rather than a request that gets routed. There is no form to submit and nothing waiting for approval: someone adds an asset, someone else drags it from In stock to In service, and a third person logs the repair it needed in March.
What you get
- An Assets table with the columns an asset register actually needs — tag, serial, custodian, warranty, purchase value — and a Repair Spend column that adds itself up from the maintenance log.
- A board grouped by state. The lanes are the state column's own options, so changing the options changes the board.
- A dashboard with what it cost, what it is, and where it all is.
- A record page per asset: the details, a stepper for its state, and a history you can write into.
- A Report a Fault form, and one approval behind it: anything quoted at $400 or above waits for IT Ops to decide repair or replace, everything under goes straight into the asset's history with its cost.
Where the Flow goes
Not around the asset — behind one number on it.
The state of an asset is a column on the row, not a step somebody is sitting on, so an asset can go backwards, skip a state, or come out of retirement without anyone re-authoring anything. Nothing about owning a laptop is an approval.
Spending money on one is. So the single Flow in this app sits behind the quoted cost of a repair: above the delegated limit it waits for a person, below it, it does not wait at all. Either way the answer lands as a row in the maintenance log, and the log is what Repair Spend adds up. That is the shape to copy when you attach your own — one Step, behind one column, writing back onto the record it was about.
What it expects from your workspace
A shared Employees table, so the custodian of a laptop is the same person the rest of your apps already know about. If your workspace has one, this app uses it. If it does not, it is created for you.
Arrives with its tables, pages and Flows, running in your workspace.
Add to workspace