CMS
Tables of content your sites and apps read.
CMS is where you keep your own structured data. You define a table, give it the fields you need, then fill it in like a sheet. A table can hold products, bookings, posts, a team list, or anything else you need to keep and look up.
Everyone in the workspace sees its tables. The records live in the workspace's own database, and each table is also an ordinary Xuda Studio table.
Make a table
Open CMS
Go to the CMS page. With nothing there yet you see two ways to start and four tables to start from.
Press New table
Press New table. The New table window opens.
Name it and give it fields
Write a name, then add fields. Each field has a name and a type: text, number, yes or no, date, list or JSON. Switch on Must for a field that has to be filled. A drawing beside the form shows the table as it will look.
Choose who can read it
By default only the workspace reads it. Choose Anyone to let visitors read its records on a public workspace. They can never change them.
Create it
Press Create table. The table opens as a page, ready for its first record.
You can also start from a template, from a CSV file (its first row becomes the fields and the rest the records), or by dropping a CSV anywhere on the CMS page.
Common jobs
- Add records. Open a table and press Add record, or import a CSV. The live line at the foot says what is being saved.
- Change the fields. Press Edit fields in an open table, or in a card's menu. A saved field keeps its name, so its values stay with it. A field you remove leaves its values on the records, unread.
- Relate tables. In the New table window, choose a type under Relate to: Contacts, Tickets, Deliveries, Orders, Products, Finance documents or another table. You can also drag one table's card onto another, or drop one of those modules on a card. Nothing is saved until you save the table.
- See related records where you work. Once a table is related to tickets, deliveries, orders, products, finance documents or contacts, it shows as a Tables card on each one of them, to fill in place.
- Use a table from code. Press API and JSON on a card. The window shows the five calls, the table's JSON, and a place to try each one with a key.
- Archive a table. Archive table in a card's menu takes it off the Active view and frees one of your plan's tables. Its records are kept, and Restore table brings it back from Archived.
What the page tells you
The big figure at the top is every record in the tables of the view you are on. Under it each table is a card drawn as a small sheet: its first four fields and records, then its name, how many records it holds and when it last changed.
The foot line shows your plan, a row of dots lit for the share of your records in use, and what is in use, for example 5 of 25 tables. Open the plans window from the card icon in the header.
If CMS is switched off, your tables and records are kept and can be read, but nothing new is made until you switch it on. The page says so, with a way to do it.