On this page
Build an Authenticated MiniUp App
An authenticated MiniUp app combines a Site frontend with Site Access and a Site Members Function. MiniUp provides trusted member identity; your Function decides which application operations each member may perform.
Understand the application pieces
| Piece | Responsibility |
|---|---|
| MiniUp Site | HTML, CSS, JavaScript, and static assets |
| Site Access | Login requirements, members, and roles |
| Site Members Function | Trusted backend logic and authorization |
| MiniUp Tables / APIs | Application records and data |
| Function Secrets | Private credentials used by Function code |
Browser
↓
MiniUp Site
↓
/api/functions/my-api/...
↓
Site Members Function
↓
private data / external APIsBuild the app step by step
- Publish frontend files in a MiniUp Site.
- Choose Invite-only or Private Site Access if the frontend itself should be protected.
- Invite members and assign roles.
- Create a Site Members Function linked to that Site.
- Use env.MINIUP_USER for trusted identity and check permissions inside every protected backend operation.
- Add private credentials through Function Secrets, then publish the Function.
- Optionally implement a bootstrap endpoint to tell the frontend which features to display.
- Test the complete app as Owner, as Viewer, and while signed out.
Example: a staff reports portal
Everyone in the Site can see a dashboard. Editors can view reports. Owners and Admins can perform administrative actions. The frontend uses feature flags to show appropriate navigation, while each corresponding backend route enforces the same permission before returning data or making changes.
Frontend controls what users SEE. Backend controls what users MAY DO. Hiding an Admin button is a convenience for users, not API protection.