Atloria supports several kinds of users, from people who manage documentation behind the scenes to people who simply read published content. If you are new to Atloria, this page helps you identify the role that best matches your work and the areas of Atloria you will use most often.
Documentation Manager
A Documentation Manager is usually responsible for the overall health of documentation across one or more projects. This person keeps content organized, makes sure releases are ready to publish, and helps teams maintain a clear documentation process.
Typical responsibilities include:
- Planning documentation structure
- Overseeing drafts, reviews, and publishing
- Managing versions of documentation
- Setting audience visibility
- Monitoring performance and activity
Modules used most often:
- Project Management for project dashboards and settings
- Document Editor for organizing and reviewing pages
- Documentation Versions for tracking releases and comparing versions
- Approval Workflow for review and sign-off
- Version Access Control for deciding who can see each version
- Audiences for content targeting
- Export Center when documentation records need to be shared or archived
- Enterprise Analytics for usage and performance review
Helpful guides:
- Working with Project Lists and Dashboards
- Managing Project Administration from the Project Home
- Creating and Editing Documentation Pages
- Analyzing Project Performance and Activity
Technical Writer
A Technical Writer focuses on creating, updating, and improving documentation content. In Atloria, this role often works closely with reviewers, project owners, and subject matter experts to turn project knowledge into clear documentation.
Typical responsibilities include:
- Writing and editing pages
- Organizing content for readers
- Updating existing versions
- Preparing content for review
- Adding visuals and supporting material
Modules used most often:
- Document Editor for writing, editing, previewing, and organizing pages
- Documentation Versions for working within the right release
- Approval Workflow for submitting work for review
- Screenshot Capture for collecting images to use in documentation
- Audiences for tailoring content to different reader groups
- Support Agents when checking how documentation answers common questions
Helpful guides:
Project Administrator
A Project Administrator handles setup, access, and operational controls for documentation projects in Atloria. This role makes sure teams can get into the right projects, connect outside services, and manage project-level settings.
Typical responsibilities include:
- Creating new projects
- Choosing setup methods
- Connecting repositories and related services
- Managing project settings and website options
- Overseeing access and permissions
- Reviewing activity and controls
Modules used most often:
- Authentication for account access and entry points
- Project Onboarding for new project setup
- Project Management for dashboards and project settings
- Integrations for connecting supported Git providers
- Admin Dashboard for administrative controls
- Audit Trail for reviewing activity records
- AI Settings for provider setup, usage review, and prompt management
Helpful guides:
- Accessing and Registering Your Atloria Account
- Understanding Account Entry Points and Session Navigation
- Creating Projects and Completing Onboarding
- Choosing Between Manual and Connected Project Setup
- Managing Project Settings and Website Options
- Using the Admin Workspace
- Managing User Access and Administrative Permissions
- Reviewing Security and Audit Controls
Support Team Lead
A Support Team Lead uses Atloria to help customers find answers faster. This role often depends on published documentation and AI-powered help experiences to reduce repeated questions and improve self-service support.
Typical responsibilities include:
- Reviewing documentation for common support topics
- Using AI support agents to answer questions
- Checking whether published content is easy to find and understand
- Monitoring which content is most useful
Modules used most often:
- Support Agents for creating, managing, and chatting with AI assistants
- Public Documentation Viewer for reviewing the reader experience
- Documentation Versions for checking what is currently available
- Enterprise Analytics for understanding usage and engagement
- Audiences for confirming the right readers see the right content
Helpful guides:
Public Documentation Reader
A Public Documentation Reader is not usually part of the internal documentation team. This person visits published documentation to learn about a product, compare versions, and read content meant for a specific audience.
Typical responsibilities include:
- Browsing published documentation
- Switching between available versions
- Reading content for a specific audience
- Finding answers to product or feature questions
Modules used most often:
- Public Documentation Viewer for reading published content
- Version Access Control when version availability affects what can be viewed
- Audiences when content changes based on reader type
Public readers usually do not need the administrative or project setup areas of Atloria. Their experience is centered on the published documentation itself.
Which Role Sounds Most Like You?
If you mainly manage structure, releases, and publishing, start with the Documentation Manager guides. If you write and maintain pages, the Technical Writer path will feel most familiar. If you set up projects and control access, follow the Project Administrator guides. If your focus is customer help and self-service, look at the Support Team Lead areas. If you are here to read published content, you will spend most of your time in the public documentation experience.
Was this page helpful?