## Orienting Yourself on the Project Home Page When you open a project in **Atloria**, start by checking the parts of the screen that stay consistent as you move around. These elements help you confirm that you are still working inside the same project and not in a different workspace or a broader admin area. Look for these **project context markers** on the page: - **Project name** in the page header - **Breadcrumb trail** showing where you are inside the project - **Workspace switcher** if your project connects to other workspaces - **Primary navigation tabs or links** for areas such as **Documents**, **Versions**, **Analytics**, **Technical Documentation**, **Onboarding**, and **Settings** These project-level navigation links are important because they keep you inside the current project. When you open **Documents** or **Versions** from the project navigation, Atloria carries the same project context forward instead of sending you back to a general dashboard. The project home page also acts as a hub for related work. Depending on your project setup, you may see links or cards that take you to: - **Documents** for writing and organizing content - **Versions** for release and review work - **Analytics** for project performance and usage information - **Technical Documentation** for reference-style content tied to the project - **Onboarding** for setup tasks and guided project preparation - **Settings** for project-specific configuration If Atloria shows a **linked workspace** indicator, treat it as a sign that the next screen may belong to a connected area rather than the exact page group you are currently browsing. This matters when you want to review related content without accidentally editing in the wrong place. A useful rule is simple: - **Project-scoped navigation** affects the current project only - **Global navigation** can take you out of the current project context [SCREENSHOT: Project home page showing the project name, breadcrumb trail, workspace switcher, and navigation links for Documents, Versions, Analytics, Technical Documentation, Onboarding, and Settings] For broader project-home behavior, see [Managing Project Operations Across Project Home Tabs](doc:managing-project-operations-across-project-home-tabs). ## Moving Between Documents, Versions, and Analytics Without Losing Project Context A common navigation path in Atloria is moving from **Documents** to **Versions** to **Analytics** while staying inside the same project. The key is to use the project’s own navigation links instead of returning to a global dashboard each time. From the project home page, open **Documents** using the project navigation. Once the page loads, confirm the active project by checking: - The **project title** in the header - The **breadcrumb trail** - Any visible **workspace label** - The fact that you arrived there from the project navigation rather than a general list When you switch from **Documents** to **Versions**, use the project tab, sidebar link, or project navigation menu that appears within the same project area. This keeps version history tied to the active project. You should still see the same project name and a breadcrumb path that shows you are inside that project’s version area, not in a separate unrelated workspace. Next, open **Analytics** from the same project navigation. Atloria keeps the project context visible through shared markers such as: - The same **project title** - The selected **workspace** - A breadcrumb path that still points back to the current project On the **Analytics & Insights** page, you may see a page header and a notice that the area is not yet fully available. Even so, the page remains part of the same project journey if you opened it from project navigation. To return to the project overview without losing your place, use: - The **breadcrumb** link for the project - The project’s own **navigation tabs** - Your browser’s **Back** button if you just moved from one project section to another Avoid using a top-level global menu when you only want to move between project sections. That can take you out of the current project and force you to reselect it. [SCREENSHOT: Documents page with project title and breadcrumb visible, followed by the same project context on Versions and Analytics] ## Opening Technical Documentation and Onboarding from a Project From the project page, you can also open **Technical Documentation** and **Onboarding** without breaking the connection to the current project. These areas may feel different from **Documents** or **Versions**, so it helps to watch the page title, breadcrumb, and workspace label closely. When you open **Technical Documentation** from a project, Atloria presents it as a project-linked documentation area. It is still connected to the project you came from, but it may look more like a dedicated reference workspace than a general project overview page. To confirm you are in the right place, check for: - A **page title** that clearly indicates technical or reference content - A **breadcrumb** that still traces back to the project - A visible **workspace label** if the technical content is shown in a linked workspace This is especially useful when you are moving between project planning and reference material. If you already reviewed the technical content structure in [Exploring Technical Documentation Inside a Project](doc:exploring-technical-documentation-inside-a-project), use that guide for the content itself and use this page to stay oriented while moving between areas. Opening **Onboarding** from the same project keeps setup work tied to that project as well. In Atloria, onboarding is where guided setup tasks and project preparation steps remain associated with the active project rather than becoming a separate unrelated task list. Watch for these cues: - The **project name** still appears in the header or breadcrumb - The **Onboarding** page title makes it clear you are in setup-related work - The navigation path still gives you a way back to the project home page The main difference between **Technical Documentation** and **Onboarding** is usually the purpose shown in the page title and navigation labels: - **Technical Documentation** focuses on project-linked reference content - **Onboarding** focuses on setup tasks and guided preparation To return, use the **breadcrumb**, the **workspace switcher**, or the project navigation menu. These options are safer than jumping out through a global menu. [SCREENSHOT: Technical Documentation page opened from a project, with breadcrumb back to the project] [SCREENSHOT: Onboarding page showing project-linked setup flow and return path] ## Using Linked Workspaces to Reach Related Content In Atloria, a **linked workspace** is a connected area that belongs to related work but is not always the same as simply opening another page inside the current project section. Understanding that difference helps you avoid editing or reviewing content in the wrong place. A normal project navigation move might take you from **Documents** to **Versions** while keeping everything in the same project workspace. A linked workspace move usually means Atloria is taking you to a connected area with its own page structure, while still preserving the relationship to the project you started from. You may encounter linked workspace entry points in places such as: - A **workspace switcher** - A **linked resource** card on the project page - A contextual link to **Technical Documentation** - A related area such as **Onboarding**, **Analytics**, or another connected workspace view - Cross-project or cross-workspace references shown in navigation Before you continue working, look for signs that you crossed into a linked workspace: - A changed **workspace label** - A breadcrumb that includes the source project - A visible relationship label showing the page is connected to the project - A page title that reflects a specialized workspace rather than the main project home Atloria helps preserve context by keeping the project relationship visible. Even when the page layout changes, you should still be able to tell which project the workspace belongs to and how to return. Stay in the **current project workspace** when you want to: - Write or organize project content - Review project versions - Move between standard project tabs Open a **linked workspace** when you need to: - Review related technical reference material - Complete setup tasks in **Onboarding** - View connected analytics or supporting content that lives in its own workspace structure If you are unsure, pause before editing and confirm the **project name**, **workspace label**, and **breadcrumb** first. ## Managing Project Settings Without Breaking Navigation Flow Open **Settings** from the project navigation when you need to change options for the current project. Using the project’s own **Settings** link is the easiest way to avoid changing something at the wrong level. Inside project settings, Atloria may group project-specific controls into panels related to areas such as: - **Access** - **Integrations** - **Documentation preferences** - **Linked workspace configuration** These settings belong to the active project, so always verify the page context before making changes. The most reliable checks are: - The **project name** in the header - The **breadcrumb** path - The selected **workspace** - The fact that you entered **Settings** from the current project navigation This matters most for teams that work across several projects. If two projects have similar names or connected workspaces, the header and breadcrumb are your quickest confirmation that you are editing the correct one. After updating a setting, you do not need to restart from a dashboard. Move back to operational pages by using the same project navigation links for **Documents**, **Versions**, or **Analytics**. This keeps your project context intact and saves time. Keep in mind that some settings areas may be **permission-sensitive**. In practice, that means: - **Project Administrators** may be able to open and change more settings - **Documentation Managers** or **Technical Writers** may only be able to view some settings or may not see certain options at all If a settings panel is missing, it may be hidden based on your role rather than removed from the project. For broader setup details, see [Managing Project Administration from the Project Home](doc:managing-project-administration-from-the-project-home) and [Managing Project Settings and Website Options](doc:managing-project-settings-and-website-options). [SCREENSHOT: Project Settings page with project name, breadcrumb, and links back to Documents and Analytics] ## Fixing Common Navigation Problems Across Projects and Workspaces Most navigation mistakes in Atloria come from moving too quickly between project pages, linked workspaces, and top-level navigation. When something looks wrong, check the visible context before you make edits. If you open a page and the project context seems wrong, verify these items first: - The **project name** in the header - The **breadcrumb** path - The selected **workspace** - The page title, such as **Documents**, **Versions**, **Analytics & Insights**, **Technical Documentation**, **Onboarding**, or **Settings** If a linked page opens in an unexpected workspace, look for a **workspace switcher** or a **linked workspace** label. That usually tells you whether you are still in the current project workspace or viewing a connected area. If the workspace name changed, use the breadcrumb or switcher to return before editing anything. If you cannot find **Documents**, **Versions**, **Analytics**, **Technical Documentation**, **Onboarding**, or **Settings**, the cause is often one of these: - You are in the wrong project - You are in a linked workspace with a different menu - Your role does not include access to that area - The navigation item is hidden for your current permissions When returning to the project overview causes you to lose your place, use navigation that preserves context: - Click the **breadcrumb** back to the project - Use the project’s own **tabs** or navigation links - Use the browser **Back** button if you just moved from one project section to another Try not to jump out through a global menu unless you truly want to leave the project. Global navigation is useful for switching to another major area, but it is the most common reason users lose the active project selection. If you need a broader view of project-level oversight after you are comfortable moving between these areas, continue with [Managing Project Portfolio and Operational Oversight](doc:managing-project-portfolio-and-operational-oversight). ## Overview This guide focuses on one practical skill: staying oriented while moving through a project in **Atloria**. Instead of treating **Documents**, **Versions**, **Analytics**, **Technical Documentation**, **Onboarding**, and **Settings** as isolated destinations, Atloria presents them as connected parts of the same project workspace. The most important idea is to rely on the screen elements that preserve context: - **Project name** - **Breadcrumb trail** - **Workspace switcher** - **Project navigation links** - **Page titles** that show which project area you are in You use these cues to answer simple but important questions before taking action: - Am I still in the same project? - Am I in the main project workspace or a linked workspace? - Will this change affect only this project? - Can I return to the project home page without starting over? This guide does not repeat the detailed behavior of each project tab. For that, use [Managing Project Operations Across Project Home Tabs](doc:managing-project-operations-across-project-home-tabs). Instead, the focus here is how those tabs and linked workspaces connect so you can move confidently between them. You also saw that some pages, such as **Analytics & Insights** or **Security & Audit**, may appear as dedicated screens with their own headers. Even when a page has a different visual emphasis, the breadcrumb, project title, and workspace label help you confirm whether it still belongs to the same project journey. Use this guide whenever you need to move between project work areas without losing track of scope, permissions, or the path back to your project home page. ## Prerequisites Before the navigation patterns in this guide will make sense, you should already be comfortable opening a project and recognizing the main project workspace in **Atloria**. You will get the most value from this guide if the following are already true: - You can sign in to Atloria and reach your main workspace - You can open a project from the project list or dashboard - You have access to at least some project sections such as **Documents**, **Versions**, or **Settings** - You understand the basic project home layout from earlier project management guides Helpful background reading includes: - [Working with Project Lists and Dashboards](doc:working-with-project-lists-and-dashboards) - [Managing Project Workspaces and Recent Activity](doc:managing-project-workspaces-and-recent-activity) - [Managing Project Operations Across Project Home Tabs](doc:managing-project-operations-across-project-home-tabs) You do **not** need access to every project area mentioned in this guide. Some teams will not see every navigation item, and some roles may have view-only access in places like **Settings** or **Analytics**. That is normal in Atloria. Before you begin, make sure you can identify these on screen: - The **project name** - The **breadcrumb** - The **workspace switcher**, if your project uses linked workspaces - The project navigation links for the sections available to your role If one of those items is missing, you may be in the wrong workspace or using a role with limited access. In that case, it is best to confirm your current project and visible navigation before following the workflows in this guide.