Manage your appCloud
Database
Collections, records, who may see what, and importing or exporting data.
Everything the app has saved, in collections: the bookings, the orders, the notes people wrote.
- Pick a collection to see its records, 200 at a time, with Load more, and with who saved each one.
- Search looks through the 5,000 most recent records.
- Add record, and on each row a pencil to change it and a bin to delete it. Adding, changing and deleting need someone who can edit the app.
- Export CSV downloads up to the 10,000 most recent records of the collection, not only the page on screen.
Import a catalogue, at the top, takes a CSV or Excel file of products, prices or anything else the app lists. The file is read in your browser and is never uploaded just to look at it. Put it into the app's own file, which is instant and right for up to about a thousand rows, or into the database, which handles a full catalogue. You match the file's columns to the app's before anything is written.
Importing a catalogue: the details
- The window offers the database by itself when the file has more than 800 rows.
- Into the app's own file, the addition cannot be more than about 1.5 MB.
- Into the database, rows go up in groups of 500. If the upload stops, rows already sent stay and Continue resumes it.
- The whole file is checked against the plan's room for records before anything is written. If the app already has a list of that name you can choose to replace it.
- Afterwards the window offers a request for the chat to make the screens read a page at a time, and Let visitors read the list.
- A list kept in the app's own file can be edited item by item below the import, exported, or emptied, and the change shows in the preview at once and on the live site after the next publish.
- To start a whole new app from a spreadsheet, use the Import dialog instead. See Import an app.
Who may see what
Under Access rules, on the Cloud page, each collection says who can read it and who can change it. By default a record is read and changed only by the person who saved it, plus your team if you have marked some accounts as team. Anyone signed in to the app can create records, and owns what they create.
| Button | What it does |
|---|---|
| Make readable by anyone | Visitors read the collection without an account. Right for a menu, a catalogue, published posts. |
| Require sign-in | Back to accounts. Anyone with an account reads every row, if the app's screens show the collection whole. A screen that shows the collection to visitors stays empty for them until they sign in. |
| Only your team | Only the accounts you marked as your team read all of it. Shown once you have team members and the collection is read by everyone. |
A change takes effect at once, on the published app too. A collection the app deliberately shows to everyone is opened by itself when the app is published, and you can close it here.
Was this page helpful?