Do your users need an Overskill account?

Yes, built-in sign-in uses a shared Overskill account. Creating it is free; app access, paid features and creator plans are separate.

Yes, if your app uses Overskill's built-in sign-in. Your users create or reuse a shared Overskill account. Creating an account and signing in are free; they do not need a paid creator plan just to sign in to your app.

That shared identity does not automatically give them access to every app, private record or paid feature.

One account, separate access for each app

Someone who already has an Overskill account can reuse it. They do not need a new password for each app using built-in sign-in.

Each app records its own relationship with that person, including app-specific roles and access. Being a customer of your app does not make someone a member of your builder workspace. Likewise, an account that can open one app may not be allowed into another.

For example, a person could use the same account for a booking app and a client portal. Their booking-app access should not give them permission to read another customer's portal records. The portal still needs its own access rules and tests.

Free sign-in does not mean every app feature is free

Keep these three things separate when explaining your app:

What the person is doing What to explain
Creating an account or signing in Built-in sign-in is free. A paid creator plan is not required for this step.
Using your app Your configured access rules apply. The app may offer paid access, purchases or metered AI features with their own charges or credits.
Building their own app Creator plans, build credits and current availability are separate; see pricing.

Show any price or usage requirement before a paid action. Check the payment and feature setup for your particular app before describing what is included.

What happens at sign-in?

Users follow the methods available on your app's sign-in screen. A new account may need email confirmation. Depending on the entry path, consent may be included in signup or shown on a separate permission screen.

Sessions can expire, and someone may need to sign in again. For account recovery, direct them to the option offered by the sign-in flow and have them return with the same account.

The signup walkthrough explains how to request the flow and test confirmation, returning users and private records.

What can you manage as the app owner?

With the required workspace permissions, you can manage a person's roles and access to your app. Revoking that access is different from deleting their shared Overskill account or resetting its password.

Tell users what information your app collects and how to contact you about it. A shared sign-in does not grant ownership of their identity or settle your responsibilities for their information. Review the data access and export controls available for your app when answering a user's request.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Letting users sign in

Adding social login (Google, Apple, GitHub)

Let users sign in with their existing accounts. One click, no password to remember.

Restricting access to paid users

Gate parts of your app — or the whole thing — behind a subscription or one-time purchase.

How your app's users sign up

Add a clear signup journey with built-in sign-in. Understand shared accounts, app-specific access and checks to run before inviting users.

Still need help?

If this didn't answer your question, our team is one click away.