Skip to main content
Use visibility settings to decide who can open your app and whether they need to sign in. Then use roles to control what each person can see and do inside the app, such as viewing data or managing orders. Finally, add collaborators to work with you in the app editor to design, configure, and maintain the app. Only collaborators and the app owner can access the app editor and your app’s dashboard. Roles such as Admin and User control what people can do in the live app, but they do not give access to the app editor or dashboard.
Users 1

Managing your app users and their roles


Setting your app visibility

App visibility decides who can open your app and whether they need to sign in. Pick the level that fits your app. Visibility is only about who can get in. How people sign in, such as with email and password or Google, is a separate setting on the Authentication page. Learn more about managing login and registration. Base44 uses smart app visibility to suggest a starting point for you. Apps that act like public sites, such as landing pages or portfolios, are automatically set to Public without requiring login. You can change this setting at any time.
Appvis 1

Choosing your app visibility from your app's dashboard

To set your app visibility:
  1. Go to your app’s Dashboard.
  2. Click Overview.
  3. Click the App Visibility drop-down.
  4. Select a visibility level.
Important:
  • Private apps are available on paid plans only.
  • If you set your app to Private, you need to invite people so they can log in and use your app, unless you turn on auto-admit. Click Send Invites to send invitations or share your app link. People who are not invited or admitted through SSO see an error message.
Good to know about app visibility:
  • If your app does not require login, it cannot identify who each visitor is. Features that depend on user identity, such as user profiles or saved per-user data, will not work.
  • If your workspace enforces SSO, people sign in to public apps through your identity provider. On an app that offers both public options, select Public (login required) so sign in matches the rest of your workspace, because Public (no login) is unavailable while enforcement is on. Learn more about Enterprise SSO and app visibility.

Inviting users to your app

Invite people to use your app by sending them an email invitation from your dashboard or from inside your app. Inviting someone as a user or admin controls what they can do in the live app. It does not give them access to the app editor or your app’s dashboard.
How invites work:
  • If your app is set to Workspace visibility, all workspace members automatically have access and do not need individual invites.
  • If your app is private, SSO is its only sign-in method, and auto-admit is on, people are added automatically when they sign in and do not need individual invites.
  • If your app is not published yet, the invitation dialog shows Your app isn’t published yet. You can still send the invitations, but invitees cannot access the app until you publish it.
  • Invite permissions depend on your app’s visibility:
    • Private app: Only admins can invite people and can choose whether the role is user or admin.
    • Public app: Admins can invite people and choose roles. People with the user role can invite other users.

From your dashboard

Send invitations from your app’s dashboard and choose the role for each person. To invite people from your dashboard:
  1. Click Dashboard in your app editor.
  2. Click Overview.
  3. In the Invite Users section, click Send Invites.
  4. Enter the email address for each person you want to invite.
  5. Click the Access level drop-down and choose a role.
  6. Click Send Invitation.
Sendinvites 1

Inviting people to your app from your dashboard

From your app

You can also invite people directly from inside your app by asking the AI chat to set up in-app invites. Use the invite option it adds to enter each person’s email address and, if prompted, choose the role you want to give them. Example prompt: Add the option to invite users to the app from inside the app
Asking the AI chat to add the ability to invite users from inside your app

Asking the AI chat to add the ability to invite users from inside your app


Share a link to your app so people can access it directly. To share your app link:
  1. Click Dashboard in your app editor.
  2. Click Overview.
  3. In the Invite Users section, click Copy Link.
  4. Share the link wherever you want people to access your app.
Copylink 1

Sharing a link to your app

If you share a link with someone but they do not have permissions to access your app, they see a pop-up asking them to request access.

Choosing your users’ roles

Roles control what each person can do on your live app. By default, every app includes 2 roles:
  • Admin: Can manage areas that are restricted to admins on the live app.
  • User: Can view and use the app with no special permissions.
Being an Admin or User does not give anyone access to the app editor or your app’s dashboard. To work there, someone must be a collaborator or the app owner.
For example, in a store app you might give your shop manager the Admin role so they can update stock levels and process orders in the live app, while giving your sales staff the User role so they can view products, check order status, and use the app without changing settings.
You can create extra roles and fields if you need more control. For example, you can ask the AI chat to:
  • Create a role called Staff Manager that can update staff shifts and schedules on the live app.
  • Add a field called app_role to the Users entity with values Admin, Staff, and Viewer.
To update a user’s role:
  1. Click Dashboard in your app editor.
  2. Click Users.
  3. Select the user whose role you want to change.
  4. Click the Role drop-down and choose Admin or User.
  5. Click Submit.

Giving a group access to your app

Instead of adding people one at a time, you can give a whole workspace group access to your app at once. Everyone in the group gets access with the role you choose, and access stays in sync automatically as people join or leave the group.
Sharing your app with a group is an Enterprise feature. To share with identity-provider (IdP) groups, you also need SSO configured for your workspace. Learn more about workspace groups.
Before you invite a group:
  • Groups are created and managed in your workspace settings, not in your app, so you can only share groups that already exist there.
  • On a private app, all members of the invited groups get access to your app and receive an email letting them know.
  • On a workspace app, everyone already has access, so inviting a group only sets the role for its members.

Adding a group

Invite a workspace group from your app’s Groups tab and choose the role its members get. To give a group access to your app:
  1. Click Dashboard in your app editor.
  2. Click Users.
  3. Click the Groups tab.
  4. Click Invite group.
  5. In the Search for a group box, find the group you want to add and select its checkbox.
  6. Click the Assign role to group drop-down and choose the role you want everyone in the group to have.
  7. Click Invite group.
Invite group to app

Inviting a group to your app

Managing group access

The Groups tab lists every group that has access, along with its type, member count, and role. From there, you can change a group’s role or remove its access at any time. To manage group access:
  1. Click Dashboard in your app editor.
  2. Click Users.
  3. Click the Groups tab.
  4. Do one of the following:
On the group’s row, click the Role drop-down and choose a new role.
Change group role

Changing a group's role in your app

  1. On the group’s row, click the remove icon.
  2. In the confirmation window, click Remove group.
Remove group access

Removing a group from your app

Everyone who had access only through that group loses it, and any of those members who already signed in have their account in the app removed. This cannot be undone.

Working with collaborators

Collaborators are people who help you build your app in your app editor. Add collaborators when you want someone to design, configure, or maintain the app with you.
What is the difference between collaborators and admins?
  • Collaborators
    • Can open the app editor and your app’s dashboard.
    • Help you design pages, change logic, connect data, and configure settings.
    • Are invited from the Invite collaborators icon in the app editor.
  • Admins
    • Sign in to the live app.
    • Access admin-only areas on the live app, such as protected reports or management tools.
    • Cannot open the app editor or your app’s dashboard unless they are also collaborators.
Collaborators are separate from user roles. When you add someone as a collaborator, they are added to your app as an Admin in Users by default so they can manage content, data, and settings in the live app while they build. You can later change their app role on the Users page without affecting their access to the app editor.

Inviting collaborators

Invite collaborators directly from your app editor.
To invite someone as a collaborator, they must be a member of the workspace that owns the app. If they are not yet a member, invite them to the workspace first from your workspace settings.
To invite collaborators to build your app:
  1. Go to your app editor.
  2. Click the Add collaborator icon at the top.
  3. Enter the email addresses of the people you want to invite, separated by commas.
  4. Click the Send invite icon .
Addcollab

Inviting collaborators to your app in Base44

Managing collaborators

Remove a collaborator when they no longer need access to the app editor. To manage collaborators:
  1. Go to your app editor.
  2. Click the Add collaborator icon at the top.
  3. Find the relevant collaborator and click the More Actions icon.
  4. Click Remove Collaborator.
  5. In the confirmation window, select an option:
    • Remove collaborator access only: Immediately revoke their access to the app editor and prevent them from making changes, but keep them in the Users list with their existing role so they can still use the live app.
    • Remove from app entirely: Revoke their collaborator access and remove them from the Users list so they can no longer sign in or use the app.
When teammates are working on the same app, you see their avatars in the top bar so you always know who is currently editing. Hover over an avatar to see their name and coordinate changes in real time.
Collab

Restricting external collaborator invites

By default, any workspace member can invite people from outside the workspace as app collaborators. You can restrict this so that only workspace owners and admins can send these invitations. To configure who can invite external collaborators:
  1. Click your workspace name at the bottom left of your account.
  2. Click Settings.
  3. Click Governance.
  4. Click the External Collaborators toggle:
    • Enabled: Only workspace owners and admins can invite people from outside the workspace as app collaborators.
    • Disabled: Any workspace member can invite people from outside the workspace as app collaborators.
External Collaborators setting in Base44

External Collaborators setting in Base44

Enterprise workspaces have this setting on by default. All other workspaces have it off by default.

Testing your app as a user

View and interact with your app as any user or role to check permissions, troubleshoot issues, or test user flows.
Changes you make while testing as a user are saved to that person’s data. To avoid affecting real data, test with sample or dummy users whenever possible.

Why would you want to test your app as a user?

  • Realistic testing: Test the app exactly as a specific user or role sees it
  • Permission visibility: Quickly verify what each role or user can and cannot access
  • Faster troubleshooting: Reproduce and debug reported issues in the person’s real context
  • Flow validation: Run end to end checks, such as onboarding and key tasks, before releases
To test your app as a user:
  1. Go to your app editor.
  2. Click the More Actions icon at the top right.
  3. Select Act as a user.
    Actasuser 1

    Selecting "Act as a user" in the Base44 app editor

  4. Click the drop-down next to You’re acting as and select the relevant user.
  5. Preview and interact with the app as that user.
  6. Click Exit mode when you’re done testing as another user.
The user’s role appears in parentheses next to their email address.
Using the "Act as a user" feature in Base44

Testing your app as a user in Base44


FAQs

Click below to learn more about managing access to your app.
Yes. If your app is set to Public, anyone can create an account from your register page and sign in. On an app that still offers Public (login required), anyone with a Base44 account can sign in.
Yes. On a Public app, ask the AI chat to protect the pages you choose and send visitors who are not signed in to your login page. See how to show a public landing page but require login for other pages.
For extra protection on a public app, click Run Security Scan to check for common issues before you share it.
They list these options: Public (no login), Private, Public (login required), and Workspace. Public (login required) appears with a Deprecated label. To customize your own login and registration screens on one of these apps, see custom login for existing apps.
When someone requests access to a private app, owners and collaborators get an in-app notification, and the app owner also gets an email. To keep your inbox manageable, you receive at most one email every 15 minutes per app, even if several people request access.To review an access request:
  1. Click the notifications icon in your workspace.
  2. Click Review to open the request and decide whether to grant access.
Reviewaccess

Reviewing an access request

An app user is someone who signs in and uses your app. Their access is controlled by visibility settings and roles such as Admin or User. They can only see and use the live app (including any admin-only sections), not the app editor or dashboard.A collaborator is someone who helps you build the app in the app editor. Only collaborators and the app owner can open the app editor and your app’s dashboard. When you add someone as a collaborator, they are automatically assigned the Admin role in Users in the app by default so they can manage live data and settings while they build. You can change their app role later without changing their collaborator status.
Before February 16, 2026, making someone an admin was the only way to let them edit your app. Admins from that time keep their access and were added as collaborators automatically.
No. If you want someone to help build or edit your app, invite them as a collaborator from the app editor. This gives them access to the app editor and, by default, the Admin role in your app. Make someone an admin in Users without adding them as a collaborator only when they need admin access in the live app but do not need to work in the app editor.
You can control who can access, read, write, or delete records in your app’s data entities by setting Row Level Security (RLS) rules and permissions. Configure access for each entity to ensure data is only available to authorized people. Learn more about managing security settings.
Yes. Go to your app’s Dashboard, open Users, and click the Delete icon next to the person you want to remove. Removing them immediately revokes their access.
Base44 locks down the built-in Users list to protect sign-in data, so only collaborators and the app owner can read it. Any feature that reads from the Users entity, such as a member profile page or personalized content, works for admins but not for regular members. Reading it directly can also trigger an Authentication required to view users error.The fix is to store member data in a separate entity, such as UserProfile, and point your features at that instead of the built-in Users entity.To set this up, paste this prompt into the AI chat:Create a new entity called UserProfile. Move custom fields from the Users entity to UserProfile. Establish a 1:1 relationship between Users and UserProfile. Ensure a UserProfile is automatically created when a new user signs up. Update the app to fetch user details from UserProfile instead of Users. Set permissions so users can only edit their own profile, but anyone can read it.After the AI makes the changes, go to your app’s Dashboard, click Security, and review the RLS rules on your new UserProfile entity to make sure they match your intended access levels.
To safely test user flows without affecting real data, add a test person directly to your app. Once the test profile exists, you can use the Act as a user feature to impersonate them and preview their experience.To create a fake (test) user:
  1. Go to your app’s Dashboard.
  2. Click Users.
  3. Click Invite User to send an invitation, or register a new account using your app’s public signup page.
  4. Assign the desired role or permissions to the test profile.
You can also ask the AI chat to create a test user.
After you create your test user, open your app, click the More Actions icon at the top, and select Act as a user. Then, choose your test user from the list to interact with your app as that person. Any actions taken affect only the test user’s data, not your live accounts.Use this method to check permissions, visibility rules, and user flows before rolling out changes to everyone.