Choose Your Atloria Role

Atloria provides different documentation workflows for administrators, writers, engineers, managers, and readers. Understanding your role helps you focus on the screens and actions that are relevant to your work while respecting your organization’s access controls.

Overview

Your Atloria role determines which areas of the documentation hub you can use and what you can do there. Access is governed through 👤 Role-Based Access Control (RBAC), so the options available to you may differ from those available to coworkers.

Most users begin from an Overview screen or 📊 Overview area, where they can orient themselves within the available documentation and project information. Depending on your permissions, you may also see items such as 1. Dashboard Overview, Atloria Stack, Infrastructure Overview, or Architecture Overview.

Roles support different stages of the documentation lifecycle:

• Administrators control access and organization-level setup.
• Writers create and maintain documentation content.
• Engineers contribute technical context and validate documentation against the product.
• Managers review documentation coverage, quality, and progress.
• Readers consume published documentation for guidance and reference.

Your assigned role may include more than one responsibility. For example, an engineering lead may have both engineering and management access, while a technical writer may also be able to review and publish content.

📷 Screenshot pending: An Atloria Overview screen showing the documentation hub and role-relevant navigation options.

Prerequisites

Before you begin using role-specific workflows, make sure you have:

• An active Atloria account.
• Access to your organization’s Atloria documentation hub.
• An assigned role or permission set from your Atloria administrator.
• A completed sign-in process, including any organization-required authorization steps.
• Permission to view the relevant project, audience, or documentation area.
• A clear understanding of whether you are expected to create, review, manage, or only read documentation.

If you have been asked to connect or authorize a service, look for the Authorize Atloria option. Only complete authorization when instructed by your organization or administrator.

Step-by-Step Instructions

1. Open the documentation hub.

   After signing in, open the available Overview or 📊 Overview area. This is your starting point for understanding what documentation and operational information you can access.

   You may see a welcome message such as Welcome to your Documentation Hub. Use this area to locate the project or content that applies to your work.

2. Review the areas available to your account.

   Look at the navigation and page titles you can open. Your available screens reflect the permissions assigned through 👤 Role-Based Access Control (RBAC).

   For example, you may be able to access:

   • 1. Dashboard Overview for a summary of available information.
   • Atloria Stack for platform-oriented context.
   • Infrastructure Overview or Architecture Overview for technical reference material.
   • Atloria Platform for broader product information.

   If a screen is not visible, your current role may not include access to it.

3. Identify your primary workflow.

   Choose the workflow that best matches your responsibilities:

   • Administrator: Focus on user access, authorization, and governance. You may need to ensure that colleagues receive the right level of access and can enter the appropriate documentation areas.
   • Writer: Focus on preparing clear, accurate documentation for the intended audience. Use the documentation hub to locate existing material, identify gaps, and maintain content.
   • Engineer: Focus on technical accuracy. Review technical subjects such as Architecture Overview, Infrastructure Overview, and Atloria Stack when confirming that documentation reflects the product.
   • Manager: Focus on visibility and coverage. Use overview and dashboard information to understand progress, identify documentation gaps, and coordinate review work.
   • Reader: Focus on finding and using published guidance. Start with the overview content, then open the documentation topic that answers your question.

4. Use role-appropriate information before taking action.

   If you are an administrator, verify access requirements before asking users to begin work. If you are a writer or engineer, review available context before changing or validating documentation. If you are a manager, use overview information to prioritize the work that needs attention.

   Technical and operational reference topics may include titles such as Atloria agent-core: What We Build On Top of @openai/agents or Atloria = SDK Loop + 4 Custom Layers. These topics can be useful for technical reviewers, but readers should use them only when they need deeper platform context.

5. Ask for access when your workflow is blocked.

   If you cannot find the screen, project, or document needed for your role, do not assume it has been removed. Contact your Atloria administrator and explain what you need to do—for example, review architecture content, manage access, or read a specific document.

📷 Screenshot pending: A permissions or access view showing how Role-Based Access Control determines the areas a user can open.

Tips and Best Practices

• Use the overview before searching for details. Starting from Overview or 📊 Overview helps you understand the available documentation context before opening individual topics.

• Treat permissions as intentional. If you cannot see a feature or page, it may be restricted to another role. Request access rather than sharing accounts or attempting to work around the restriction.

• Match your review depth to your role. Readers usually need task-focused documentation. Writers need content and audience context. Engineers may need architecture and infrastructure references. Managers should focus on coverage and status signals.

• Use technical reference pages carefully. Topics such as Architecture Overview and Infrastructure Overview support technical validation, but they may not be necessary for every documentation task.

• Keep role responsibilities clear. Writers can draft and improve explanations, engineers can verify technical correctness, managers can prioritize and approve work, and administrators can ensure that the right people have access.

Related Pages

• Overview
• 1. Dashboard Overview
• 👤 Role-Based Access Control (RBAC)
• Architecture Overview
• Infrastructure Overview
• Welcome to your Documentation Hub

Troubleshooting

I cannot see the page or documentation area I need

Your role may not include permission to view that area. Confirm that you are signed in with the correct account, then contact your Atloria administrator with the name of the screen or documentation area you need.

I see an overview, but I cannot find the expected workflow

Start with Overview or 📊 Overview and review the available navigation. Some workflows may be represented by project-specific content rather than a separate role label. If the required area is still unavailable, ask an administrator to verify your RBAC assignment.

I was asked to connect Atloria, but I do not see the option

The Authorize Atloria option may only be available to users with the appropriate authorization permissions. Contact your administrator or the person who asked you to complete the connection before proceeding.