Base44 app works for me but not for other users

What it means in plain English

You open the app and it loads. You send the same link to someone else, or you paste it into another browser, and it does not. Base44's troubleshooting page titles this "App link does not open in other browsers" and says it is usually publishing, the domain, or app visibility.

That is separate from a person who can open the app and then cannot see rows. Base44 documents that second case under data permissions.

Likely causes

• The app is not published. Dashboard, Publish, then Publish app. If it is not published, the invite dialog says "Your app isn't published yet". Invites can still be sent. Invitees cannot open the app until you publish.
• App Visibility is Private. Only email addresses you explicitly invite can open the link. Private apps are on paid plans only. People who are not invited, and not admitted through SSO, see an error. Sharing a link with someone who does not have permission shows a request-access pop-up after they verify their email.
• Visibility is Workspace. Everyone in the Base44 workspace can open it, and they must sign in. People outside the workspace are not in that group. Workspace members do not need individual invites.
• Visibility is Public. Anyone on the internet can open it, and sign-in is not required. Public is the setting Base44 names when anyone with the link should get in.
• You sent a custom domain that is not connected and verified. The default Base44 URL can still load. See Base44 custom domain or SSL stuck pending.
• They can open the app and sign in, then data is missing or a members-only feature fails. That is the security scan path below, not the visibility path. An invalid login on a Private app is Base44 login not working.

Admin and User are the two default roles, and they apply to the live app only. They do not open the editor or the dashboard. Collaborators and the owner open the editor. Adding a collaborator assigns Admin in App Users by default.

How to fix it, step by step

1. Open the app's dashboard. Click Publish in the top right. Select Publish app if it is not already published.
2. Click Overview. Under App Visibility, choose the level Base44 defines: Public (anyone on the internet, sign-in not required), Private (only invited people, sign-in required), or Workspace (everyone in the Base44 workspace, sign-in required). To let anyone with the link in, select Public.
3. On a Private app, invite them: Dashboard, Overview, Invite Users, Send Invites, enter the email, choose the role, Send Invitation. Skip the individual invite only when the app is private, SSO is the only sign-in method, and auto-admit is on. Only admins can invite on a Private app.
4. If you shared the link and they see a request-access pop-up, Base44 emails them a verification code first. You get a notification after they verify, and they get an email if you approve.
5. If you use a custom domain, confirm it is connected and verified, then try the default Base44 URL. If that URL loads and the custom domain does not, fix the domain before changing visibility again.
6. If they can open the app but cannot see or edit data, go to Dashboard, Security, Run Security Scan. Review the data permission issues and click Fix All, or adjust each table, then sign in with different roles. Admin can manage admin-only areas on the live app. User can view and use the app with no special permissions. You can ask the AI to create extra roles. The docs' example is a role named Staff Manager.
7. If the link still does not open, Base44 says to contact support with the exact app URL, whether the app is published, and whether you are using a custom domain.
8. Paste this to the Base44 chat:

The app opens for me and not for other people. Do not change the data model yet. Confirm the app is published. If anyone with the link should get in, set App Visibility to Public. If it is Private, I will invite their email from Dashboard → Overview → Invite Users. If they can open the app but cannot see rows, I will run Dashboard → Security → Run Security Scan.

How to check it worked

• In a browser where you are not already signed in as the owner, the published link opens when visibility is Public.
• On a Private app, an invited email can open it, and an address you never invited still cannot.
• A person who could not see rows can see the tables their role allows after the security scan, and a different role still cannot.

A person who can open the app and then cannot pay is the Stripe setup. See Base44 Stripe payments not working.

Sources

• https://docs.base44.com/Community-and-support/Troubleshooting (opens in a new tab)
• https://docs.base44.com/Setting-up-your-app/Managing-access (opens in a new tab)