Build a custom app
You will assemble a small custom app: a single screen with a few blocks over the data you have been building. By the end you have a focused tool that shows just what a job needs. This uses the category you built and, if you did it, the purchasing from Automate with a wire.
Add a few blocks
The builder isn't in the main nav, so this is the door:
- Open Configuration → Apps, in the Build section, and hit New app.
- Add a page, then drop in blocks that answer one question well:
- Stat: a count or a sum (how many parts are low).
- View: embeds a saved view, like the "what's low" list from the first tutorial.
- Form: creates a record showing only a few fields, so intake is three boxes instead of twenty.
- Action: a button that runs an action, with your label on it.
- Preview as you go. That is a working dashboard-and-intake screen over your data.
Why apps are pages of blocks
A custom app is a set of pages, and a page is a stack of blocks. Blocks stay structured, which is what keeps a built app safe to render, and the editor previews them live as you compose. You are not writing a layout from scratch. You are picking pieces and stacking them.
Hand it to someone (optional)
Pair the app with People & permissions and a member lands straight in the app with only the abilities you granted. An app only sees the fields you give it, so you can hand a helper a tool over part of your workspace without exposing the rest.
Describe it instead
Ask the AI builder to generate an app from a description ("a picking screen: the low-stock list and a button to reorder"), and the kernel validates it before you apply it. You do not have to place every block by hand: build one way, then adjust it the other.
You now have
A custom app over your data. Last step: put a view on a screen anyone can see, no login.