Skip to content
Charming Docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Build an app multiple people use

How to share one app with the people who'll use it, whether they share data or each need their own.

Two people, one shared dataset

For an app you and one other person both use and both see the same data in, invite them with a role: collaborator if they’ll help build it, end-user if they should only use it. Either role sees and writes the same dataset you do: sharing an app doesn’t split its storage, it adds people who can reach the one copy that already exists. See Privacy and sharing for the full role list, including read-only viewers, and how to change or revoke access later.

Many people, each with their own data

Sharing a role only works when everyone should see the same data. For a group who each need their own separate copy, turn the App into a Template. Existing readers of the source App can copy it. If people should copy without access to the source App or its data, publish it as Listed so anyone can discover and copy it. A flashcard deck ten people each want to fill in their own way, or a habit tracker a few friends each want to run for themselves, both fit here.

A Template carries source forward, not data: each copy starts empty and stays independent from the Template and every other copy. See Templates for how to enable it, prepare the listing, and publish it in the public Template directory.

For an App anyone should read with no sign-in, such as a public dashboard, event schedule, menu, or status page, make it Public. The Public link opens the live App Viewer but stays read-only. If visitors need to submit or change data, invite them as end users or choose the general access level that lets signed-in visitors edit. See Privacy and sharing for the full access model.

Which shape fits

Start from who uses the App and whether their data should mix. Trusted people who work from the same information share one dataset. If each person needs separate data, give them a copy of a Template. If strangers should copy without seeing the source App, publish it as Listed. If anyone with the URL should only read the live App, make it Public.

Copy this prompt for your agent

Help me set up sharing for my Charming app. Read
https://charm.ing/docs/guides/build-an-app-multiple-people-use.md first,
then ask me who's using the app and whether their data should be shared
or separate before setting it up.

Was this page helpful?