On this page
Control Dataset Access and Cross-Site Sharing
Dataset access is configured separately from Site Access. Use it to keep data with its source app, share read access with selected MiniUp apps, or intentionally publish a public data link.
Choose a dataset access mode
| UI choice | Outcome |
|---|---|
| Private to this app | Keeps dataset use within its source app’s permitted access |
| Share with selected MiniUp apps | Adds explicit read access for selected target Sites |
| Public link | Makes the dataset publicly readable under its current availability and key requirements |
A Table may also require a read key or enforce action-specific permissions. Inspect both dataset access and Table API settings. A public frontend should not contain a credential intended to bypass private dataset access.
Share a dataset with another Site
- Open Dashboard → source Site → API for a Table, or Parquet for a data file.
- Open the dataset’s Access settings or dataset access panel.
- Choose Share with selected MiniUp apps.
- Select the intended target Site and add the read grant.
- Open the target app and verify that data loads for the intended visitor.
- Remove or disable a grant when the target app should no longer use the dataset.
Example: reuse a reference dataset
A reference Table can remain in its original Site while two approved MiniUp apps read it. Select those target apps explicitly. If you instead choose Public link, anyone with access to that public URL may read the data; Gallery visibility is irrelevant.
Troubleshoot denied dataset access
Check the source Site, target Site, dataset access mode, enabled grant, and read-key requirement. A bundle may report a dataset as ineligible if it is owner-only, requires a private read key, is unavailable, or is incompatible with the target. Fix the dataset policy intentionally rather than embedding credentials in the app.