# Custom Apps

**Apps** are small applications a team builds inside Volobox: a purchase request form with an approval queue, a visitor sign-up, an equipment tracker. You build one by describing it to an agent, and it runs inside Volobox, not as a separate tool to host. Each app has its own data, roles and screens, and it is part of the workspace: the same people and groups use it, it sends cards to the same Inbox, it links to projects and tasks, and its records can be charted in dashboards.

![The Apps page: Meridian Works apps as cards (Campaign Assets, Customer Feedback, Equipment Checkout, Field Visits, Onboarding Hub, Vendor Requests), each with its color, description, the viewer’s role and publish date, Open Builder and Open draft for the apps the viewer builds, and New app.](https://volobox.io/docs/images/apps-gallery.light.webp)

*The Apps page: the workspace's apps as cards with the viewer's role, Open Builder and Open draft on the apps they build, and New app.*

## Building an app by describing it

You build an app in the **Builder** by describing what it should do to a coding agent. The agent writes:

- the app's data: typed fields, references between records, people, files and computed fields
- its own roles
- its rules
- its screens

A live preview beside the chat shows the result at phone, tablet and free widths. Each turn lists the files it changed. The agent can stop and ask you a question mid-turn, and several Builders can share a session, with **Take over** to pick it up.

Everything the agent does lands in the app's **draft**, which has its own data and is seen only by the app's Builders and Admins. People who use the app see nothing until it is published. The guide [Build an app](/docs/build-an-app) walks through it.

## Templates

A new app can start blank or from a template. A template is a complete, working app with its data, roles, rules, screens and dashboard, optionally with sample data in the draft so you can try it at once.

Templates include Asset Inventory, Employee Onboarding, Event Registration, Expense Claims, Purchase Requests, Recruiting, Room & Desk Booking, Sales Pipeline, Training & Certifications, Vendor Register, and more.

![The New app dialog over the Apps page, filled in for an Interview Scheduler app, with its Start from list open: Blank, the app templates such as Expense Claims, Purchase Requests and Asset Inventory, and Import from a file.](https://volobox.io/docs/images/apps-templates.light.webp)

*The New app dialog: a name, address and description, and the Start from list with Blank, templates and Import from a file.*

## Review and publish

The **Review** tab compares the draft with the published app and lists every change in plain words: new screens, removed fields, who gains or loses access. It marks what **needs attention**, such as anything newly opened to visitors or a change to a field's type.

The same tab lists the draft's versions since the last publish. You can undo the agent's last change, restore the draft to an earlier version, or discard every change and start again from the published version.

Publishing never deletes data, and people get the new version the next time they open a screen.

![The Field Visits app in the App Builder on its Review tab: version 6 is live and a Publish button, what the published app needs (Projects and tasks, Task closed, both ready), the data and screen changes in the draft, and the draft version made by a Builder request.](https://volobox.io/docs/images/app-publish.light.webp)

*An app's Review tab in the Builder: the live version and Publish, what the published app needs, the data and screen changes in the draft, and its versions.*

## Who can use an app

Two kinds of roles apply:

- **Member roles** decide what a person does with the app itself. A **Member** uses the published app, a **Builder** also builds and publishes it, and an **Admin** also manages its members, roles and settings. Groups can be members, and an app can be made **public** so everyone in the workspace is a member.
- The app's **own roles**, such as requester or approver, decide what a member sees and does inside it.

A screen can also be open to **anyone, signed in or not**, for people outside the workspace: a guardian filling in a consent form, a visitor registering. Each such screen is marked on review.

> **Note:** A visitor's screen never reads the app's tables directly. It can only do what the app's visitor actions allow, usually sending a form.

Screens follow each person's Volobox language when the app offers several languages.

## Part of the workspace

- **Links to Volobox items.** Records can link to projects, milestones, tasks, requests, groups, clients, repositories, pull requests, tickets, Docs pages, meetings and agents, and open them. An app **reads** Volobox items and never changes them.
- **Reacting to Volobox events.** Rules can run when a task closes, a pull request merges or a ticket arrives, wherever an app Admin binds the event.
- **Workflows.** An app can declare its own events, and those events can start Volobox workflows. That is how an app gets something changed elsewhere in Volobox. See [Workflows](/docs/workflows).
- **Inbox cards, notifications and alerts.** An app can put a card in someone's Inbox with its own buttons, which run the app's actions as the person who presses them. Rules can also send notifications, raise alerts and run on schedules.
- **Records in the workspace.** A record can be copied as a reference into a chat or a Docs page, added to an agenda, and discussed in its own discussion.
- **Agents.** Your assistant and other agents can look up, add and change records and run an app's actions, each change on an approval card unless a standing rule you set covers it, with your access in the app.

> **Note:** External agents connected over the API or MCP do not reach app records today.

## Calling other systems

Rules can call another system's REST API. A Builder or Admin of the app who was given the workspace secret's scope binds each credential to that secret and to the hosts it may be sent to, so the app's files never contain the value. An app can also receive webhooks from other systems through an endpoint it opens.

See [Call other systems from an app](/docs/call-external-systems).

## Shares between apps

One app can **share** some of its records, events and endpoints with other apps: a sales app can link each deal to a customer in a CRM app. The sharing app's Admins decide which apps get a share.

Another app's records are only read, and the only way to change them is an endpoint the share names. A share can also go to **Insights**, so dashboards chart the app's records. See [Dashboards and alerts](/docs/dashboards-and-alerts).

## What an app is made of

An app is a small set of readable files: `app.json` for the data, roles and access, JavaScript **rules**, and React **screens**. The read-only **Structure** tab draws them, so you can understand an app without reading its code. The file formats are in [App files](/docs/app-files).

An app can be exported as a zip and imported as a new app or a new version, in the same workspace or another one.

## Related

- [Workflows](/docs/workflows)
- [Dashboards and alerts](/docs/dashboards-and-alerts)
- [Agents](/docs/agents)
- [API and MCP](/docs/api-and-mcp)
- [Build an app](/docs/build-an-app)
- [Custom Apps](/product/custom-apps)
