For the studio manager
Equipment that shows where it is.
Max books camera kit A for project P-118. The Equipment table shows it as booked until Friday, and the calendar view shows when it comes back, before anyone plans the Brasserie Lune shoot.
Data models
Checking availabilityComing soonTrack the things only your business tracks.
Build tables for equipment, domains, venues or suppliers, with the fields they need. They get the same views, filters and dashboards as everything else in Squario.
Your own record types, next to the built-in ones
Every business keeps a list nobody planned for: hired equipment, client domains, venues, retainers. Give it a name, an icon, a colour and the fields it needs. Its records get every view type and saved views, plus files, comments and activity if you switch them on.
A table for whatever your team keeps track of
Name the record type, pick an icon and a colour, and choose the field that titles each record. Switch on files, comments and activity where they help. The schema diagram shows how your tables link to companies, projects and each other.
Name, icon and colour
Each table gets its own name, icon and colour, so it reads clearly in menus and lists.
Files, comments and activity
Switch on per-record files, comments and an activity history when the table needs them.
Every view, saved views too
List, board, table, calendar, gallery, tree or diagram, and saved views to reuse.
A schema diagram of the links
See how your tables connect to companies, projects and each other, on one diagram.
Fields for the details your work depends on
Add custom fields to your tables or to built-in records like deals and projects. Link records with references, compute values with formulas, mark a site on a map. Then filter, group and report on them like native fields.
From text to maps
Text, number, date, select, checkbox, currency, file, image, drawing and map fields.
References and formulas
Link a record to another one, and let a formula compute a value from its fields.
Conditional and required-when
Show a field only when it applies, and make it required when another field says so.
Field-level permissions
Choose which roles can see or edit each field, and the rule holds everywhere, Squaria included.
The lists that used to live in spreadsheets
Three moments where a table built in Squario replaces a spreadsheet, a notebook or a shared doc.
On site, TuesdayEvery sign location, marked on the map.
For the Kessler Logistik signage project, Jonas walks the depot and drops each sign on a map field, with a photo in an image field. Back at the studio, the Signs table shows them all.
End of the monthDomain renewals, before they lapse.
Sofia opens a saved view of the Domains table: renewals due in the next 30 days. Each domain links to its client, and a formula field shows the yearly cost, ready to review.
Tables that match the way your team works.
In a 30-minute demo, bring the spreadsheet your team keeps on the side and see it rebuilt in Squario as a table, with its fields, views and links.
Questions about data models
Do I need a developer to build a table?
No. Data models and custom fields are built in the app, without code.
Which plans include data models and custom fields?
They are included on paid plans. The Free plan doesn’t include them.
Can I add custom fields to deals and projects too?
Yes. Custom fields can be added to any record type, and you can filter, sort, group and report on them like native fields.
Can different roles see different fields?
Yes. Field-level permissions decide who can read or edit each field, and they apply everywhere, including in Squaria and over MCP.