Starting from Public Pages and Choosing an Account Entry Point
Before you enter your workspace in Atloria, you begin on a public page. From there, the main account entry points are the Sign in screen and the Create account screen. If you already have access, choose Sign in. If you are new to Atloria and need your own login, choose Create account. The registration screen asks for Name, Email, and Password, while the sign-in screen asks for Email and Password.
Atloria separates pages into two groups:
- Public pages, which you can open without signing in
- Account-only pages, which require an active session
If you try to open an account-only area without being signed in, Atloria sends you to the Sign in screen first. After you sign in successfully, Atloria takes you into the account area. In the current flow shown here, a successful sign-in sends you to the main authenticated area at /app, which is the starting point for the dashboard-style workspace.
Choose Create account when you do not yet have login details and Atloria allows self-registration. After registration, Atloria signs you in automatically and opens the account area. Choose Sign in when your account already exists, including cases where an administrator has already created access for you or invited you to join. In those cases, you do not need to register again unless you have been specifically told to create a new account.
If you need help with the basics of reaching these screens or creating your first login, see Accessing and Registering Your Atloria Account.
Signing In and Establishing an Authenticated Session
On the Sign in screen, enter your Email and Password, then select the Sign in button. While Atloria is checking your details, the page enters a loading state so you know your request is being processed. If your details are correct, Atloria signs you in and opens the main account area.
The sign-in screen in this flow includes these user-facing elements:
- Email field
- Password field
- Sign in button
- An error message area when sign-in fails
If the email and password do not match an account, Atloria shows the message Invalid email or password. If something goes wrong during the sign-in process for another reason, Atloria shows An error occurred. Please try again. No separate Forgot password option or single sign-on option is shown in the available screen details here, so users should expect a standard email-and-password sign-in flow.
After a successful sign-in, Atloria creates your active session and changes what you can open. Account-only pages under the authenticated workspace become available, and Atloria redirects you into the main account area at /app. That redirect is immediate, so you do not need to select another button after sign-in succeeds.
If you are registering instead of signing in, the Create account screen collects Name, Email, and Password. When registration succeeds, Atloria attempts to sign you in automatically using the same email and password. If the account is created but the automatic sign-in does not complete, Atloria shows this message: Registration successful, but login failed. Please try logging in.
For help with sign-in errors, use Signing In to Atloria and Solving Access Problems.
Arriving in the Account Area After Access Is Granted
Once Atloria accepts your sign-in, you are taken into the authenticated workspace at /app. This is the point where the interface changes from public access to account access. Instead of public entry screens, you now see the dashboard-style layout used for signed-in pages.
The exact first page depends on where you were sent after authentication, but the shared layout for signed-in users is consistent. In this authenticated area, Atloria wraps pages in a dashboard layout, which means you should expect account navigation and workspace structure that are not available before login.
From the available screens in this context, one clear destination inside the account area is the Admin workspace. The Admin page includes cards linking to:
- Users & Permissions
- Organizations
- Documents
- Projects
- Analytics
Each card includes a short description and a small stat, such as Total Users, Organizations, Total Docs, or Active Projects. This tells you that once you are signed in, Atloria can present role-based work areas rather than a single flat menu.
Some pages also have clear signed-in headers, such as:
- Analytics & Insights
- Security & Audit
These headings confirm that you are inside protected account areas rather than public pages. In practice, what you see first may depend on your role, your organization access, or the link you used to enter Atloria. A standard user may land in a general workspace or project area, while an administrator may move directly into broader management screens such as Users & Permissions, Organizations, or Security & Audit.
If you want a fuller tour of the administrative workspace after you arrive, see Using the Admin Workspace.
Moving Between Account Screens Without Losing Context
Inside the authenticated workspace, you move between pages using account navigation rather than public links. Based on the available screens, Atloria supports movement between major areas such as Admin, Projects, Documents, Organizations, Analytics, and project-specific pages like Analytics and Webhooks inside an individual project.
A few navigation patterns are visible in the current flow:
- Top-level account areas open inside the signed-in dashboard layout
- Admin cards act as shortcuts to management screens
- Project-specific pages open within the context of a selected project
That project context matters. For example, project pages such as Analytics and Webhooks are tied to a specific project, so when you open those pages, Atloria keeps you inside that project’s workspace instead of sending you back to a general home page. This helps you move between related pages without losing track of which project you are working in.
If you open a bookmarked account page while you already have an active session, Atloria should take you straight to that page instead of asking you to sign in again. If the page belongs to a specific project, organization, or admin area, your access still depends on whether your current account can open that area.
When moving around, use the navigation that appears inside the signed-in layout whenever possible. That keeps you in the correct workspace and reduces the chance of landing on a page that does not match your current role or project. For a deeper look at project-level movement, see Understanding Project Navigation and Linked Workspaces.
Handling Redirects, Access Checks, and Session Boundaries
Atloria makes a few important decisions each time you open an account-only page. The outcome depends on two things: whether you are signed in, and whether your account is allowed to open that specific area.
The main routing outcomes are:
- You have a valid session and the right access: Atloria opens the page
- You are not signed in: Atloria sends you to Sign in
- You are signed in but do not have permission: Atloria prevents access to that page
This is the difference between sign-in status and page permission. Sign-in status answers, “Are you logged in?” Permission answers, “Are you allowed to open this screen?” For example, you may be able to sign in successfully but still be unable to open Users & Permissions, Organizations, Analytics, or Security & Audit if those areas are limited to administrators or specific members.
When your session ends, Atloria treats you like a signed-out user again. Common session boundary events include:
- Manual sign-out
- An expired session
- Access being removed
- Opening a protected link from outside Atloria without an active session
In those cases, Atloria routes you back through the sign-in flow before allowing access to protected pages. If the page is available after you sign in and your account still has permission, you can continue into the workspace. If not, you may be redirected to a safer destination such as the main account area instead of the page you originally tried to open.
Some protected pages are also role-sensitive. A direct link may work for one user and fail for another, even if both can sign in. For more on permission-based access after login, see Managing User Access and Administrative Permissions.
Fixing Common Problems When Users Cannot Reach the Right Account Screen
If Atloria does not take you to the page you expect, start by matching the problem to what you see on screen. Most access issues fall into a small number of patterns.
If Atloria sends you back to Sign in after you just logged in, check these points:
- Make sure you saw a successful sign-in rather than an error such as Invalid email or password
- Try opening the main account area again after sign-in
- If the page keeps returning to Sign in, your session may not be staying active in the browser
If you land on the wrong page after authentication, compare what happened with the normal post-login behavior in this flow:
- Successful sign-in sends you to the main authenticated area at /app
- Successful registration also signs you in and then opens /app
- If you expected a different destination, the page may require a different role, project membership, or a specific saved link
If you can sign in but cannot open a specific account page, the most likely cause is access level. Check whether the page belongs to an admin-only area such as:
- Users & Permissions
- Organizations
- Analytics
- Security & Audit
If a bookmarked account page opens as an error or blank state, test whether the problem is tied to the link itself or to your session:
- Open the same page after signing in fresh
- Try entering through the main account area first
- Confirm that the page still exists and belongs to a workspace you can access
When the problem is specifically related to sign-in behavior, use Signing In to Atloria and Solving Access Problems. If the issue is about admin-only pages, continue with Reviewing Security and Audit Controls or Monitoring Administrative Analytics and Activity, depending on the screen you are trying to reach.
Overview
Atloria has a clear split between public pages and authenticated account areas. Public pages are where you begin, using Sign in if you already have access or Create account if you need to register. Once Atloria confirms your details, it opens the signed-in workspace and makes account-only navigation available.
The key points to remember are:
- Sign in uses Email and Password
- Create account uses Name, Email, and Password
- Successful sign-in redirects you to the main account area at /app
- Successful registration also signs you in automatically and then opens /app
- Protected pages require both an active session and the right permission level
Inside the account area, Atloria uses a dashboard-style layout for signed-in pages. From there, users can move into workspace areas such as Projects, Documents, and, where allowed, admin pages like Users & Permissions, Organizations, Analytics, and Security & Audit. Project-specific pages such as Analytics and Webhooks keep you inside the selected project context.
This document focuses on how Atloria moves you between entry points, sign-in, redirects, and protected pages. For the first part of the account access journey, including reaching the login and registration screens, return to Accessing and Registering Your Atloria Account.
Prerequisites
Before the navigation patterns in this guide will make sense in your own Atloria workspace, you should already have a basic account entry path available to you. That usually means one of these situations:
- You already have an Atloria account and can use the Sign in screen
- You can use the Create account screen to register
- An administrator or team owner has already arranged your access
You should also be familiar with the basic account access screens covered in Accessing and Registering Your Atloria Account, especially:
- How to reach the Sign in page
- When to use Create account
- Which fields appear during registration
- What a successful account setup looks like
To follow the account navigation examples in this guide, it helps if you can already do the following:
- Enter your Email and Password on the sign-in screen
- Recognize common sign-in messages such as Invalid email or password
- Open the main signed-in workspace after login
- Identify whether a page belongs to a general workspace, a project area, or an admin area
If your next task is to work inside the signed-in workspace rather than just reach it, the best follow-on guide is Using the Admin Workspace for administrative navigation or Working with Project Lists and Dashboards for day-to-day project access.
Was this page helpful?