Monitoring Administrative Analytics and Activity

Opening analytics from the admin area

To reach Atloria’s administrative monitoring screens, start from the signed-in workspace and open the Admin area. This area is intended for people who manage Atloria beyond a single project, such as organization administrators, Project Administrators, and Documentation Managers with admin-level access. On the main Admin screen, look for the card labeled Analytics. The card includes the description Usage statistics and insights, which helps confirm you are opening the correct section rather than a project-specific dashboard or a document workspace.

1. Sign in to Atloria with an account that can open the Admin area.
2. Open Admin from the main navigation.
3. On the Admin screen, find the Analytics card.
4. Click Analytics to open Analytics & Insights.

At the top of the page, you will see the heading Analytics & Insights with the subtitle Usage statistics and performance metrics. This is the admin-level monitoring area for reviewing activity across Atloria, not just within one project. Depending on what is available in your environment, this screen is where you would expect to review date controls, summary cards, charts, and activity listings that help you monitor usage patterns and recent changes.

If you usually work inside project pages such as documents, versions, or project settings, this screen will feel different. Project screens focus on one workspace at a time. The Analytics & Insights area is meant for broader monitoring, so administrators can look across teams and projects instead of checking each project separately. If you need help finding the Admin workspace first, see Using the Admin Workspace.

Reading platform activity at a glance

When you open Analytics & Insights, begin with the top section of the page. In Atloria, this area is designed to give administrators a quick read on overall usage and performance trends before they drill into details. The most important items to look for are the summary cards and any chart area tied to the selected time period. These top-level visuals help you answer simple questions quickly: Is usage active? Has activity increased recently? Are there any obvious drops or spikes?

1. Open Admin > Analytics.
2. Look first at the summary area near the top of Analytics & Insights.
3. Check the current date range or reporting window if one is shown.
4. Review the totals and any visible trend direction before opening detailed views.
5. Compare the chart pattern with the summary totals to judge whether the change is brief or sustained.

Use the totals and trend signals together rather than reading one item in isolation. For example, a high total paired with a short spike can mean a burst of activity during a release or review period. A steady chart with consistent totals usually points to regular adoption. A flat or low-activity period may suggest that teams are inactive, between releases, or not using a feature as often as expected.

High-level signals that are especially useful include:

• Noticeable increases in usage over a recent period
• Long flat periods with little or no activity
• Sudden spikes that stand out from earlier dates
• Totals that remain high across multiple periods instead of one short burst

If your team reports on Atloria usage regularly, keep the same date window each time you review the page. That makes it easier to spot meaningful changes instead of reacting to normal daily variation.

Analyzing usage patterns across Atloria

After the top-level review, narrow your focus to understand where activity is coming from. In Atloria, the admin analytics area is intended to support broader usage analysis, so look for filters, grouped chart segments, legends, or tables that break activity into smaller parts. These controls help you move from “What is happening overall?” to “Which area is driving the change?”

1. Open Admin > Analytics.
2. Set the date range you want to review.
3. Apply any available filters, such as project-related scope or other admin-level groupings.
4. Read the chart segments or grouped totals to see which areas account for the most activity.
5. Use any table or legend below the chart to compare high-usage and low-usage areas side by side.

When you compare segments, focus on relative weight rather than just raw totals. A large section in a chart or a repeated high count in a table usually points to the busiest area of work. Smaller segments may show underused areas, newer teams, or parts of Atloria that only a few users visit. If the page includes grouped metrics, read them in the context of the selected date range so you do not compare one short period with a longer one by mistake.

Different admin roles often use the same analytics view for different questions:

• Documentation Managers often look for patterns tied to documentation work, such as whether teams are actively using document-related areas.
• Project Administrators often focus on broader operational usage across multiple projects or workspaces.
• Organization administrators may use the same charts to identify adoption differences between teams.

If you need project-level context after spotting a pattern here, continue in the relevant project workspace rather than trying to answer every question from the admin view alone.

Investigating recent administrative activity

Analytics totals are useful for spotting patterns, but activity listings are what help you investigate what actually happened. In Atloria, use the activity-focused area of the admin workspace to review recent actions and narrow down a specific time window or event type. This is especially helpful when you need to understand whether a spike in usage reflects normal work, a release cycle, a burst of document updates, or a cluster of administrative changes.

1. Open Admin and go to the analytics or activity-focused view available to you.
2. Find the recent activity list, event table, or similar activity panel.
3. Set the date range to the period you want to investigate.
4. Apply any available filters or search options to narrow the list.
5. Scan the newest entries first to identify the most recent actions.
6. Open an individual entry if Atloria lets you view more detail.

As you review the list, pay attention to three things: when the action happened, what kind of action it was, and whether it appears to match the trend you saw in the charts. If a chart shows a sudden increase, the activity list may reveal a cluster of related actions during the same period. If a table looks unexpectedly quiet, the activity list can confirm whether there was truly little activity or whether your filters are too narrow.

Useful ways to narrow the list include:

• Choosing a shorter date window
• Filtering to a specific type of activity
• Searching for a related item or area, if search is available
• Reviewing only the newest entries first

If Atloria opens a detail view for an activity entry, use it to inspect the related item, the person who performed the action, or the event details shown on screen. For broader audit review, see Reviewing Security and Audit Controls.

Using analytics to support operational decisions

Admin analytics are most useful when you turn what you see into a repeatable review habit. In Atloria, the Analytics & Insights area helps administrators move beyond one-time checking and into ongoing operational monitoring. Instead of only opening analytics when something seems wrong, use the same views on a regular schedule to track adoption, workload, and unusual changes.

1. Choose a standard review window, such as the same recent period each time you check analytics.
2. Compare current totals and charts with an earlier period using the date range control.
3. Note whether activity is growing, staying steady, or declining.
4. Check the recent activity list when a spike or drop stands out.
5. Match unusual changes with visible work in Atloria, such as project updates, documentation work, or release-related activity.
6. Share the most relevant findings with the right audience inside your team.

A practical way to use these screens is to separate monitoring by role:

Use recurring comparisons to avoid overreacting to one busy day. A short spike may line up with a release, a publishing push, or a concentrated review cycle. A longer decline across repeated date ranges may point to reduced adoption or a pause in project work. If you need to connect admin findings with project-level details, continue with Analyzing Project Performance and Activity.

Resolving missing or confusing analytics data

If cards, charts, or activity tables look empty or inconsistent, start with the visible controls on the page before assuming data is missing. In Atloria, reporting screens are usually shaped by the selected date range and any filters currently applied. A narrow date window, the wrong scope, or an inactive filter can make a healthy workspace appear empty.

Check these items first:

• The selected date range is not too narrow
• Any project or grouped filter is set to the scope you expect
• You are looking at the correct admin screen rather than a project-specific page
• Your account can access the Admin area and the Analytics section
• The page has been refreshed after recent activity

If totals seem incorrect, compare the summary cards with the chart and the activity list. When all three disagree, a filter or date mismatch is often the cause. For example, a chart may reflect one period while the activity table is narrowed further by an additional filter. Clear filters one at a time and watch which result changes. That is often the fastest way to find the setting causing confusion.

1. Recheck the date range shown on the analytics page.
2. Clear or adjust filters that limit the results.
3. Confirm you are in Admin > Analytics.
4. Refresh the page if recent work is not yet visible.
5. Reopen the view and compare the summary area with the activity list again.

At the moment, Atloria’s Analytics & Insights page is presented as a coming-soon area, so some environments may show the page header without full reporting content. If you can open the page but do not see working charts or tables yet, that can be expected in the current release rather than a problem with your account.

Overview

Atloria includes an Admin workspace for people who need visibility beyond a single project. Within that area, the Analytics section is labeled Analytics & Insights and is intended for reviewing Usage statistics and performance metrics. This is the place administrators look for cross-platform monitoring rather than project-by-project checking. It is especially relevant when you want to understand overall usage patterns, compare recent activity periods, or investigate changes that affect multiple teams.

From the current interface, you can identify the analytics area by its dedicated Analytics card in the Admin screen and the Analytics & Insights page header after opening it. The screen is positioned as an administrative reporting space, separate from project workspaces such as documents, versions, and project settings. That distinction matters because project pages answer local questions about one workspace, while the admin analytics area is meant to support broader operational review.

The current release also indicates that this area is still being introduced. If you open Analytics & Insights, you may see a coming-soon style message rather than a fully populated reporting workspace. Even so, the navigation path and page naming already establish where administrators will go to monitor usage and performance metrics as the feature becomes available.

This document focuses on how to approach that admin analytics area: how to open it, what kinds of information to expect there, how to interpret summary signals and recent activity, and what to check when results appear empty or unclear. For related admin tasks, you may also want Using the Admin Workspace and Managing Organization and Admin Settings.

Prerequisites

Before you try to monitor analytics or recent activity in Atloria, make sure the following conditions are met:

• You can sign in to Atloria successfully.
• Your account can open the Admin area.
• You can see the Analytics card inside the Admin workspace.
• You understand whether you need a cross-platform admin view or a project-specific view.
• You know the date period you want to review so you can interpret totals consistently.

A few practical checks help avoid confusion before you begin:

• If you cannot reach the Admin area at all, review your access with an administrator who manages users and permissions.
• If you only need information for one project, a project workspace may be more useful than the admin analytics area.
• If you are comparing usage over time, decide on a consistent reporting window before you start.
• If you expect to investigate recent changes, be ready to review both summary metrics and activity listings together.

Atloria’s current analytics page may appear as a placeholder in some environments. That means you can still confirm the correct navigation path and screen name, but the charts, metrics, or activity details may not yet be fully available. If that is what you see, it does not necessarily mean anything is wrong with your account.

If you need help getting into Atloria before using the admin area, start with Accessing and Registering Your Atloria Account or Signing In to Atloria and Solving Access Problems.