Modules
Studio: change modules and build your own
Describe a change to any module, or build a custom module, in Studio. Learn the top bar, the Projects page and its Create action, who can use Studio, and what each plan allows.
Studio is where a workspace changes how its modules look and behave, and where it builds modules of its own. You describe what you want in plain words, Studio proposes the change, and you review it in a live preview before anything reaches your team.
Open Studio in the Develop group of the sidebar.
Who can use Studio
Studio is for a Super Admin or a Manager, in a workspace that has the Studio module. An access group can also take Studio away from chosen people.
The plan decides what you can build:
| You want to | Plan |
|---|---|
| Change a built in module, such as Contacts, Leads, or Invoices | Every plan |
| Build a custom module of your own | Scale and Enterprise |
On a plan without custom modules, Studio still opens and still changes built in modules. See Plans, add ons, and pricing.
The Studio home
Studio opens on a start screen with one field: Describe a change, for example: open Contacts as a board grouped by status.
- Choose the module the change is for with the Module picker next to the field. New module is the first choice. The installed modules you can open in Studio follow, then the custom modules your workspace has built.
- Describe the change and send it.
- Studio opens the module with the conversation on one side and a preview of the real page on the other.
The start screen says it plainly: nothing changes for your team until you apply it. You can also change a module without chatting. Click a field on the real form to open its properties, or drag it to move it. See Field conditions in Studio for the properties that show, require, or lock a field based on another field.
Review, apply, and undo
Studio is AI and can make mistakes, so every change is a proposal first. The preview reads Preview of this proposal. Nothing is saved until you apply it. Select Apply to publish it or Discard to drop it. Applying publishes a new version for everyone in the workspace, and Undo on the applied change brings the previous layout back.
The How Studio acts control sets how much Studio asks:
- One choice makes Apply ask you to confirm every change first.
- The other makes Apply publish at once. Removals and warnings still ask.
The top bar
Every Studio page has the same top bar as App Builder, so moving between the two feels the same. From the start:
- Back to app returns to the Agaro page you opened Studio from, or to the dashboard when there is none.
- Studio home is the Studio mark. It opens the start screen.
- Projects opens the list of everything you are building. The button is marked while you are on that page.
When a module is open, its name and icon follow the Projects button, and its actions sit at the end of the bar.
There is no New module button in the top bar. To start a new module, select Create on the Projects page, or choose New module in the Module picker on the Studio home.
The Projects page
Projects, at /studio/projects, lists every module you are building or customizing in Studio, so you can open each one where you left off. Search it, filter it by status, module type, or editor, and switch between Table, Grid, and Kanban.
Each project shows a status:
| Status | Meaning |
|---|---|
| Draft | Nothing is customized yet |
| Published | The module is live in your workspace |
| Changes waiting | One or more proposals wait for your review |
A project is one of three types: Agaro module (a built in module you changed), Custom module (one your team built), or New module draft.
Two actions sit in the page header:
- Create is the one way to start a project from this page. It opens Studio, where you choose a module or New module and describe what you want.
- Recently deleted lists the custom modules your workspace deleted and restores them. See Delete and restore a custom module.
The project menu
Open the actions menu on a project, named Project actions for followed by the project name.
| Item | What it does |
|---|---|
| Open project | Opens the module in Studio |
| Change cover | Picks the image shown on the project card |
| Delete project | Deletes the Studio chats and unpublished drafts, and keeps the module |
| Delete module | Deletes a custom module you built, for everyone. Shown only on a custom module you may delete |
Delete project never changes what your team sees. Its Studio chats and unpublished drafts are deleted, and whatever the module published stays live. Working on the module in Studio again brings the project back. Delete module is a different action that takes the module itself away, and it is explained in Delete and restore a custom module.
Troubleshooting
Studio is missing from the sidebar
Studio needs the Studio module, the Super Admin or Manager role, and no access group that removes it. Ask a Super Admin to check Apps catalog and modules and Access Rights.
I can change Contacts but not build a new module
Building a custom module needs Scale or Enterprise. Built in modules can be changed on every plan.
The Apply button asks me to confirm every time
That is the safer setting of How Studio acts. Switch it to the setting that publishes at once if you want fewer prompts. Removals and warnings still ask.