How Studio works
Updated November 14, 2026 · Applies to Platform ONE 1.53
Studio is where your organization adapts Platform ONE to the way it works, without code: your own fields on records, the wording of the messages the app sends, workflows that run by themselves, and, in products where customers book, the booking forms. Nothing reaches your users until it's reviewed and published.
Studio is in the menu under Extend. It's available in the Professional and Enterprise editions, and needs the Admin or Designer role.
What you can change
| Item | What it holds | More information |
|---|---|---|
| Data | Your own fields on records, such as customers, services, resources, companies and leads. | Add your own fields |
| Messages | The wording of emails and notifications. | Change the wording of messages |
| Labels | Your own words for what Platform ONE names, such as customers or projects, and your own names for menu items. | Rename words and menu items |
| Workflows | What happens by itself when a record changes or at a set time. | Automate work with workflows |
| Booking form and Booking details form | Extra questions on the public booking page, and what staff record on a booking. | In the guides of products where customers book |
| Email templates | Ready-made wording for emails staff write to a contact. | Write email templates |
| Sales rules | Rolodex ONE's pipelines and their stages, and how leads are disqualified and kept. | Set up sales pipelines |
| Booking rules | How bookings work: notice and limits, approval, and reminders. | Set booking rules |
| Time off rules | The types of time off, which need approval, and their allowances. | Set up time off types |
| Resource types | The kinds of things people book or plan, such as rooms or bays. | Set up staff and resources |
Studio shows only the items your products use.
From draft to live
Each item has one live version, and at most one change in progress.
| Status | Meaning |
|---|---|
| Draft | Being edited. Only people in Studio see it. |
| In review | Submitted with a change note, and waiting for approval. |
| Approved | Ready to publish. |
| Live | What everyone uses now. |
| Superseded | An earlier live version, kept in the version history. |
- A designer or an administrator edits a draft, saves it, and selects Submit for review with a change note.
- An administrator approves it, or requests changes and sends it back.
- An administrator publishes it, at once or at a set time.
If you turn off approval, a submitted change is approved at once and can be published. See Review and publish Studio changes.
Who does what
| Role | Can |
|---|---|
| Designer | Edit drafts and submit them. Can't approve or publish. |
| Admin | Everything a designer can, plus approve, publish, roll back and set how approval works. |