Use Atoms Cloud to add authentication to your app, protect pages and actions, test access, and view registered app users in the Users module.

Authentication on this page uses Atoms Cloud. If the project is not connected, ask the Agent to connect Atoms Cloud or follow Atoms Cloud before continuing.

How authentication works in Atoms Cloud

Atoms Cloud manages your app’s user accounts and sessions. The Agent builds the sign-up and sign-in experience and connects it to Atoms Cloud.

You can ask the Agent to protect specific pages or actions and create different roles or access levels. For example, all signed-in users might be able to view a dashboard, while only administrators can access an admin page.

App users are different from project collaborators. Atoms Cloud → Users lists people who have registered for your app. It does not show the teammates building the project in Atoms. For help with your own Atoms account, see Managing Your Account.

Set up authentication with the Agent

In the project chat, describe how you want the complete authentication journey to work. Include:

• How users should create an account and sign in.
• Every sign-in method you want to offer.
• Which pages or actions should require users to sign in.
• Whether your app needs different roles or access levels.

Atoms Cloud supports account creation, sign-in, permissions, and user sessions. You can use email and password authentication. If you need Google sign-in, request it explicitly and test the completed flow.

The Agent designs the authentication interface to match your app, so its appearance may vary. Focus on checking that the requested sign-in methods, protected pages, roles, and access rules work correctly.

When the Agent finishes:

1. Test the complete journey in the App Viewer.
2. Create a test account and confirm that sign-in works.
3. Check that protected pages and actions have the correct access rules.
4. Open Atoms Cloud → Users and confirm that the new account appears.

Test Atoms Cloud authentication

For routine testing, use the Development environment in the App Viewer. Use Production only when you intentionally test the live flow. Before creating an account, confirm the selected environment and URL. Use dedicated test accounts; never use real customer information or reuse a personal password. If your app has multiple roles, create at least one account for each role.

Use the checks below to test the complete authentication journey:

Test	What to do	Expected result
Access while signed out	Sign out, then try to visit a page or use a feature that should require authentication. Test both the normal user journey and the page’s direct URL.	The app asks the user to sign in and does not display any protected content.
Account creation	Create a new test account using each sign-up method available in the app.	The account is created successfully and appears in Atoms Cloud → Users.
Sign-in	Sign out of the test account, then sign in again using each available method.	The user is signed in and taken to the correct page.
Loading state	Submit the sign-up or sign-in form and observe the app while the request is being processed.	The app shows that the request is in progress and prevents repeated submissions without revealing protected content.
Incorrect details	Try to sign in using an incorrect email address or password.	The app displays a clear error, keeps protected content hidden, and allows the user to try again.
Active session	Sign in, use the app, and then reload or reopen it.	The user remains signed in for as long as the session is intended to remain active.
Roles and permissions	Sign in with an account for each role. Try to access both permitted and restricted pages and actions.	Each account can access only the content and actions allowed for its role.
Sign-out and session expiry	Sign out, then try to return to protected areas. Repeat the check after allowing a session to expire, if applicable.	The app returns to a safe signed-out state and no longer displays protected content.

If a check fails. Confirm the environment and sign-in method, then retry with a dedicated test account. If the check still fails or the account is missing, ask the Agent or your approved Support channel to investigate. Include the project or Chat link, URL, environment, sign-in method, role, exact error, and failing test. Never share passwords, verification codes, or tokens.

If your app includes Google sign-in, test it on each Development and Production URL your users will access. Test Development first for routine checks; test Production only when you intentionally verify the live flow. Success with one URL does not confirm that sign-in works with another.

Development and Production users are stored separately. If the project has a Production database, the Users panel displays Production users. Otherwise, it displays Development users. You cannot currently switch environments manually from this panel. If an account appears to be missing, check which environment it was created in. To learn more about the two database environments, see Database.

View registered users in Atoms Cloud

1. Open the project on a desktop device.
2. In the same workspace toolbar where the App Viewer is, select Atoms Cloud.
3. Select Users in the Atoms Cloud sidebar.
4. Under User Management, review the list or use Search by name, email or UID to find a specific test user.

For projects using Atoms Cloud authentication, the Users table shows UID, Email, User Information, Role, Created, and Last Updated. Use the search field to find a user by name, email, or UID.

The Users module lets you view and search the accounts registered for your app. It does not manage authentication settings or user access. You cannot use it to:

• Configure sign-in methods or access rules.
• Invite, delete, disable, or sign out users.
• Reset passwords or change user roles.

To make changes to authentication, tell the Agent what you want to change, then test the updated experience in your app.