Restrictions
Restrictions
Ollio provides restriction options that give you enhanced control over who can access your application. These options enable you to limit sign-ups, sign-ins, or prevent accounts with specific identifiers, such as email addresses, phone numbers, and even entire domains, from accessing your application.
Ollio provides restriction options that give you enhanced control over who can access your application. These options enable you to limit sign-ups, sign-ins, or prevent accounts with specific identifiers, such as email addresses, phone numbers, and even entire domains, from accessing your application.
Sign-up modes
Sign-up modes
Ollio supports multiple sign-up modes, giving you flexibility in managing user access to your application.
To configure sign-up modes:
In the Ollio Dashboard, navigate to the Restrictions page.
Under the Sign-up modes section, you can enable one of the following options:
Ollio supports multiple sign-up modes, giving you flexibility in managing user access to your application.
To configure sign-up modes:
In the Ollio Dashboard, navigate to the Restrictions page.
Under the Sign-up modes section, you can enable one of the following options:
Public
Public
In Public mode, the sign-up process is open to anyone. This mode is ideal for applications that want broad user access.
In Public mode, the sign-up process is open to anyone. This mode is ideal for applications that want broad user access.
In Restricted mode, user access is controlled by the application admin(s). Users can be added to the application through invitations or manual user creation. This mode is ideal for applications that are in private beta or internal tools.
Additional features available in Restricted mode:
The
<SignIn />component will keep the prompt to sign up hidden by default. This is to avoid confusion for users who don't have access.
The
<SignUp />is accessible only to users who have been invited and have a valid invitation link. Users who don't have access will see a message indicating that they need an invitation to sign up.
In Restricted mode, user access is controlled by the application admin(s). Users can be added to the application through invitations or manual user creation. This mode is ideal for applications that are in private beta or internal tools.
Additional features available in Restricted mode:
The
<SignIn />component will keep the prompt to sign up hidden by default. This is to avoid confusion for users who don't have access.
The
<SignUp />is accessible only to users who have been invited and have a valid invitation link. Users who don't have access will see a message indicating that they need an invitation to sign up.
Waitlist
Waitlist
Note
If you're using Next.js, the <Waitlist /> component is available in @ollio/nextjs@6.2.0 and above.
Note
If you're using Next.js, the <Waitlist /> component is available in @ollio/nextjs@6.2.0 and above.
In Waitlist mode, users can register their interest in your app by joining a waitlist. This mode is ideal for apps in early development stages or those wanting to generate interest before launch. Additional features available in Waitlist mode:
The
<SignIn />component will only be accessible to users who have been approved from the waitlist.The
<SignUp />is accessible only to users who have been invited and have a valid invitation link. Users who don't have access will see a message indicating that they need an invitation to sign up.The
<Waitlist />component provides a form where users can submit their details to join the waitlist. Once approved by admins, users will receive an email with access instructions.If you're using the
<Waitlist />component, you must provide thewaitlistUrlprop either in the<ollioProvider>or<SignIn />component to ensure proper functionality.
In Waitlist mode, users can register their interest in your app by joining a waitlist. This mode is ideal for apps in early development stages or those wanting to generate interest before launch. Additional features available in Waitlist mode:
The
<SignIn />component will only be accessible to users who have been approved from the waitlist.The
<SignUp />is accessible only to users who have been invited and have a valid invitation link. Users who don't have access will see a message indicating that they need an invitation to sign up.The
<Waitlist />component provides a form where users can submit their details to join the waitlist. Once approved by admins, users will receive an email with access instructions.If you're using the
<Waitlist />component, you must provide thewaitlistUrlprop either in the<ollioProvider>or<SignIn />component to ensure proper functionality.
Manage waitlist entries
Manage waitlist entries
To manage a user on your waitlist:
In the Clerk Dashboard, navigate to the Waitlist page.
On the right-side of the user's row, select the menu icon (...).
Select Invite to invite the user to your application. Select Deny to deny the user access to your application.
To manage a user on your waitlist:
In the Clerk Dashboard, navigate to the Waitlist page.
On the right-side of the user's row, select the menu icon (...).
Select Invite to invite the user to your application. Select Deny to deny the user access to your application.
Allowlist
Allowlist
Note
Allowlist is a premium feature and is not available on the Free plan. Upgrade your plan to enable this feature.
Note
Allowlist is a premium feature and is not available on the Free plan. Upgrade your plan to enable this feature.
By adding specific identifiers to the allowlist, only users with those identifiers will be able to sign up or sign in to your application, while others will be blocked. This is useful for internal tools, where you want to allow only users with your company domain to have access to the application.
By adding specific identifiers to the blocklist, users with those identifiers will be blocked from signing up for your application. This is useful for attack prevention, such as when multiple spam accounts sign up for your application. For example, if you add ollio.dev as a blocked email domain, it means that anybody with a @ollio.dev email address will not be able to sign up for your application.
To enable this feature:
In the Ollio Dashboard, navigate to the Restrictions page.
In the Allowlist section, toggle on Enable allowlist.
By adding specific identifiers to the allowlist, only users with those identifiers will be able to sign up or sign in to your application, while others will be blocked. This is useful for internal tools, where you want to allow only users with your company domain to have access to the application.
By adding specific identifiers to the blocklist, users with those identifiers will be blocked from signing up for your application. This is useful for attack prevention, such as when multiple spam accounts sign up for your application. For example, if you add ollio.dev as a blocked email domain, it means that anybody with a @ollio.dev email address will not be able to sign up for your application.
To enable this feature:
In the Ollio Dashboard, navigate to the Restrictions page.
In the Allowlist section, toggle on Enable allowlist.
Warning
Enabling the Allowlist without adding any identifier exceptions blocks all sign-ins and sign-ups.
Warning
Enabling the Allowlist without adding any identifier exceptions blocks all sign-ins and sign-ups.
Blocklist
Blocklist
Note
Blocklist is a premium feature and is not available on the Free plan. Upgrade your plan to enable this feature.
Note
Blocklist is a premium feature and is not available on the Free plan. Upgrade your plan to enable this feature.
By adding specific identifiers to the blocklist, users with those identifiers will be blocked from signing up for your application. This is useful for attack prevention, such as when multiple spam accounts sign up for your application. For example, if you add ollio.dev as a blocked email domain, it means that anybody with a @ollio.dev email address will not be able to sign up for your application.
To enable this feature:
In the Clerk Dashboard, navigate to the Restrictions page.
In the Blocklist section, toggle on Enable blocklist.
By adding specific identifiers to the blocklist, users with those identifiers will be blocked from signing up for your application. This is useful for attack prevention, such as when multiple spam accounts sign up for your application. For example, if you add ollio.dev as a blocked email domain, it means that anybody with a @ollio.dev email address will not be able to sign up for your application.
To enable this feature:
In the Clerk Dashboard, navigate to the Restrictions page.
In the Blocklist section, toggle on Enable blocklist.
Warning
In the case that you have enabled the allowlist and the blocklist and have added the same identifier in both, the allowlist takes precedence.
Warning
In the case that you have enabled the allowlist and the blocklist and have added the same identifier in both, the allowlist takes precedence.
Customize Session Token
Customize Session Token
Ollio's session tokens are JWTs that include default claims. You can extend these tokens by adding custom claims to meet specific application requirements.
For more information on customizing session tokens, refer to the dedicated guide.
Ollio's session tokens are JWTs that include default claims. You can extend these tokens by adding custom claims to meet specific application requirements.
For more information on customizing session tokens, refer to the dedicated guide.
What did you think of this content?
It was helpful
It was not helpful
I have feedback
What did you think of this content?
Helpful
Not helpful
Feedback
Last updated on
Dec
4,
2024
Last updated on
Dec
4,
2024