Adding a login

A login is optional. Plenty of apps work best wide open — a landing page, a public directory, a contact form. But the moment you want each person to have their own private space, or you want to keep an app to just your team, you add a login.

Why you’d add one

Turn on a login when you want any of these:

• Everyone sees their own information. A task tracker where each person’s tasks are theirs alone; a portal where each client sees only their own files.
• A private or internal app. A dashboard or admin tool that only your team should reach.
• Different access for different people. Admins who can do more, members who can do less — see Roles & access.

If none of those apply, you can happily leave login off and share your app with anyone.

Turning it on

You don’t configure anything by hand — just ask:

“Add a login so each person sees only their own tasks.”

“Make this app private — people have to sign in to use it.”

Exepad adds a sign-in screen and connects it to the rest of your app. People sign in with Google or an email and password; see Sign-in options for what that looks like.

What changes when login is on

Without a login	With a login
Anyone with the link can use the app	People sign in first
Everyone shares the same view	Each person has their own private space
Saved information is shared in the app	Each person sees only their own records
No accounts to manage	You can see who’s signed up and manage them

Data and login work together

Login is what makes “your own information” possible. If your app remembers information, adding a login keeps each person’s records separate from everyone else’s — automatically.

You can add it later

You don’t have to decide up front. Build and preview your app first, then add a login when you’re ready. Ask to switch it off again just as easily.

Next steps

• Sign-in options — how people sign in.
• Roles & access — give some people more control than others.
• Adding data to your app — the information a login keeps private per person.