With the upcoming Baserow 2.4 release, the Application Builder external-user limit will become a hard limit.
The limit is 500 external application users:
For Baserow Cloud: The limit applies per workspace, across all published applications in that workspace.
For self-hosted Baserow: The limit applies per instance, across all published applications in that instance.
This means external users are counted collectively across the relevant workspace or instance—not separately for each application.
As a workspace or instance approaches and reaches the limit:
At 80% of the limit, you’ll receive an in-app notification.
At 100% of the limit, you’ll receive a second in-app notification.
You’ll then have a 7-day grace period to upgrade your plan.
After the grace period, external users will no longer be able to sign in—with either a password or SSO—to any application in the affected workspace or instance until the limit is increased.
Existing external users and their accounts will not be removed from your applications.
If your applications require more than 500 external users, please contact our Sales team to discuss a custom plan that fits your needs.
This change will be introduced as part of Baserow 2.4, which is currently expected to be released around September 30.
For more information about how application users are counted and the limits for each plan, see our Workspace usage documentation.
This change has locked us out, and I think we hit a bug rather than the limit described here.
We are a small Belgian non-profit on self-hosted Baserow 2.4.0 with an Enterprise license (10 seats). Since the upgrade, every login to our published applications fails with “Login is temporarily unavailable. Please contact the website owner or try again later.”
The in-app notification also says we reached “the application user limit of 10”. The announcement and the Workspace usage docs both say 500 for Enterprise, and the docs describe the lower number as a legacy limit shown for information only. On our instance that legacy number is the one being enforced.
I looked at the 2.4.0 source to understand why. The limit is the sum of application_users across active licenses, and the 500 default only applies when no license has that field. Our license has it set to 10. So a paid Enterprise license gets 10 external users while an instance with no license gets 500.
Is this a known issue? And how do we get the license value updated? Our portal has been closed to the 61 groups we host for about four days, so anything that works today would help, even a temporary fix.
The application user limit calculation should be correct, we believe you might have an incorrect limit on your license, however. Would you mind sharing with me over a private message (you can do so by visiting my profile) your workspace name, and the email address you use in that workspace?