Database and content
Understand project data permissions and sign-in
Your Div-idy sign-in lets you manage your own projects and records. Published visitors can submit forms and read content you explicitly publish. The built-in generated-app runtime does not provide visitor registration, private user accounts, or cloud records that each visitor can manage independently.
Who can do what with project data?
- The project owner: manages supported records in the private preview and inspects data in the Database tool.
- A form visitor: submits a new record for the owner, without receiving permission to list or change earlier submissions.
- A content reader: browses deliberately published articles, products, or other public records.
New React and TypeScript apps use these same boundaries through the built-in runtime. A sophisticated interface does not change the permissions behind it.
Build an owner management interface
You can ask for a content dashboard with create, edit, delete, Save draft, Publish, and Unpublish actions. Use it from your private Div-idy preview while signed in as the project owner. Owner record management is unavailable on published visitor pages.
The generated page should explain where the owner can manage content if someone opens its management interface publicly. Adding a password box or hiding a button does not create a supported authentication system.
Treat publication as an explicit choice
A newly saved owner record is a private draft. Publishing it creates the visitor-readable copy. Saving edits later keeps the previous public copy until you choose Publish again. Unpublish removes the public copy; deleting removes both the owner record and public copy.
Publishing a project page and publishing its database content are separate actions. An unlisted link is also separate from sign-in: someone who has the link can open it.
Example: a private editor and public menu
Build a restaurant menu with an owner editor that works in my private Div-idy preview. Let me save dishes as drafts and explicitly publish or unpublish them. Visitors can browse published dishes and filter categories. If owner editing is unavailable, explain that management happens in the private preview. Do not ask visitors to create accounts.
Check the app as both owner and visitor
Create one draft and one published record. Confirm that only the published record appears to a visitor. Save an edit to it and verify that the visitor still sees the earlier version. Then republish and check the update.
For personal favorites or progress without visitor accounts, you can choose browser-local storage and label it “saved on this device.” For a public content workflow, follow the content management guide.