Studio
Change the system without changing the code
Every business has a field nobody else has, a report only the owner reads, and a rule everybody forgets. Studio adds all three from the workspace — and the apps you installed keep updating underneath them.
Included on Business and Enterprise
What Studio gives you
Four tools, each scoped to one company and audited like everything else in the kernel.
Custom fields
Add the fields your business keeps on paper to any record — customers, products, invoices, equipment, anything the kernel or an app owns.
- Ten types: text, long text, number, date, select, multi-select, checkbox, email, phone and URL
- An Arabic label beside every English one, so the field reads right in both workspaces
- Required, default value, help text, and a column in the list view when you want it there
- Values live in their own table with the record; nothing is bolted onto the app schema
Saved views
The filter you rebuild every morning, saved once — columns, sort and all — and shared with the team or kept to yourself.
- Per entity: choose the filters, the columns and the sort order
- Shared with the company or private to you
- One view can be the default, so the page opens the way the team works
Automations
When this happens, and these conditions hold, do that. Built from events the apps already emit — no polling, no glue code.
- Triggers: any app event, a schedule (hourly, daily, weekly) or a manual run
- Conditions on any field in the event: equals, not, greater, less, contains, exists
- Actions: raise an alert, send an email, post to a Discuss channel, or call a webhook
- Dry-run before it goes live, and a run log with every fire, skip and failure
Report designer
Pick a source, a dimension and a measure, and get a chart you can pin to the dashboard. No SQL, and no way to reach another company’s data.
- Sources: invoices, quotations, sales orders, expenses, customers and products
- Dimensions including month and quarter buckets and labelled references
- Money measures rounded on the server, never in the browser
- Bar, line, pie or table — and a dashboard widget from the same definition
What an automation looks like
Trigger, conditions, actions — built by picking from lists, not by writing a script.
Trigger
When an invoice is issued
Conditions
- total is greater than 50,000
- customer.category equals Government
Actions
- Notify the finance channel in Discuss
- Email the account manager
- Call the treasury webhook, signed
Dry-run it first. Every fire, skip and failure lands in the run log.
What keeps it safe
A system anyone can reshape is only useful if nobody can break it.
- Everything you build is scoped to one company: fields, views, automations and reports never cross the tenant line.
- Webhooks are signed with HMAC so the receiving system can prove the call came from your workspace.
- Automations run on a five-minute cycle with a full log; a failing one is disabled, not retried forever.
- Designing is an owner and admin permission; running a saved report is not.
- The copilot can draft an automation for you — it is created inactive, for you to read and switch on.
The copilot builds with you
Ask for “alert me when a government invoice goes over fifty thousand” and the copilot drafts the automation, inactive, for you to read and switch on. Ask for a report by month and it builds the definition, not a screenshot.
Try Studio on your own data
Start free, install Studio from the Marketplace, and build your first automation in an afternoon.