Build apps for your team
A screen built in a conversation, running on live data
Not everything should be a chat. When a job repeats — pick a customer, see their open orders, record something — a small purpose-built screen beats typing the same request every day.
The App Builder creates those screens from a description. You say what you need, it builds, you look at it and correct it.
What an app can be
- A form your colleagues fill in instead of sending emails.
- A list with search and filters over live instance data.
- A dashboard of numbers that refresh themselves.
- A phone-sized tool for people who are not at a desk.
- A small tool that calls another system and shows the result.
Apps read and write your ERP.net data through the same secured path agents use, so they respect the same permissions.
Who can open an app
Each app has an access mode:
- ERP.net internal user — anyone signed into the connected instance. This is the default when an instance is connected.
- Operator user — people with an Operator account you shared it with.
- Public — anyone with the link, no login. See Publish to the outside world.
You can also share individual apps with named people and control whether they may only run it, design it, or own it — see Sharing Apps.
Where an app runs
Inside Operator, full-screen on its own address, installed on a phone as a home-screen app, or embedded in the ERP.net Web Client. Same app, no rebuild.
What Pro adds
Free apps are screens over your existing data. Pro apps get a managed backend of their own:
| Service | What it gives you |
|---|---|
| File storage | Templates, configuration, generated reports the app can read and write. |
| Table storage | The app's own records — drafts, settings, favourites — when they don't belong in ERP. |
| Secrets | API keys the app uses without ever exposing them in the app itself. |
| Web requests | Calls to other systems, defined and tested in the Builder. |
| Pages | Several destinations in one app, each with its own access mode. |
Apps can also use AI directly — see AI in Apps — so a screen can summarise, classify or draft, not just display.
What it takes
| You want | You need |
|---|---|
| An internal tool over your data | App Builder access (Power User or above, or Power User in the instance) |
| Its own storage, secrets or outside calls | A Pro app |
| A phone app | Nothing extra — install any app to the home screen |