Which sign-in do I need?
Before you connect a database or publish your app, check who will open it. Henosia supports two ways for people to sign in to an app you build, and they solve different jobs:
| Question | Henosia Auth | Supabase Auth |
|---|---|---|
| Who signs in | Your colleagues (with optional invited guests) | Customers or visitors who sign up inside your app |
| Included in new dashboard projects | Yes, in the default template | No - used on projects without Henosia Auth, such as a Blank project |
| How people sign in | Their work Henosia account (or a one-time email code for guests) | Email and password pages built inside your app |
| Works with Supabase Row Level Security | Yes - signed-in users link to Supabase automatically | Yes - each account has its own Supabase user ID |
| Where you manage access | Environment settings > Henosia Auth in the builder | Your app's pages and your Supabase project |
Henosia Auth
Use Henosia Auth when you're building an internal tool, team dashboard, or partner portal for your company.
Most new projects started from the dashboard already include Henosia Auth. Open Environment settings (the gear icon in the left toolbar) and choose Henosia Auth to check - if it isn't installed, the tab says Henosia Auth is currently not installed in this project.
With Henosia Auth:
- Published apps default to All members can sign in, so only members of your Henosia organization can sign in.
- You can narrow access with Only selected members can sign in, invite external partners or clients by email address or company domain as guests, or restrict sign-in to your office network addresses.
- Teammates can switch between your organization's published apps with the App switcher.
- When you connect Supabase and choose Add Supabase functionality, Henosia runs Supabase connectivity powered by Henosia Auth automatically so database Row Level Security rules apply to the signed-in teammate without a second login screen.
Supabase Auth
Use Supabase Auth when your app serves people outside your company who create and manage their own accounts directly in the app, such as a customer portal or public booking app with personal logins.
Start from a project without Henosia Auth, such as Blank project on the dashboard. When you connect a Supabase project and choose Add Supabase functionality, select Supabase login using passwords to add sign-up, sign-in, and password reset pages backed by your Supabase project.
Public pages and apps without sign-in
If you're building a public website, calculator, or prototype that holds no private records, you don't need sign-in at all.
Keep two rules in mind before you publish:
- Pages in your app that don't require sign-in, and projects built without Henosia Auth or Supabase Auth, can be opened by anyone with the published
.netlify.applink. - Image files and
favicon.icoin Public assets (public/) can always be opened without signing in, and without Henosia Auth every file inpublic/is public. Keep internal documents and sample data in Private assets instead (see Assets).
Henosia Auth
Control member access, invite external guests, and set network restrictions for published apps.
Connect Supabase
Link a Supabase project and add Henosia Auth or password sign-in connectivity.
Sign-in for your app's users
Set up password sign-up, approve your data and security plan, and test page access rules.