Exporting Audit and Version Records

Opening audit and version records from control pages

In Atloria, you can start this work from two places: a project control page inside a specific project, or the enterprise control page in the admin area. Use the project control page when you want records for one project only. Use the enterprise control page when you need a broader view across teams, projects, or organization-wide activity.

On each control page, look for two separate record areas:

• an audit activity area for action history
• a version records area for documentation version history

These two lists serve different purposes. Audit records show who did something, when they did it, and what item was affected. This is the right place when you need an activity trail, such as reviewing changes, approvals, access-related actions, or other tracked events. Version records focus on documentation history. Open this list when you need to report on version changes, track revision activity, or review how documentation evolved over time.

Before you export anything, make sure you opened the correct list. If you need a timeline of user actions, open the audit activity list. If you need documentation change history, open the version records list.

Access also depends on your role. In most teams, a Project Administrator can open project-level control pages and review records for that project. A Documentation Manager may also work from project pages when preparing documentation history or version-related exports. For broader oversight from the enterprise control page, your account needs access to the admin workspace and its record screens.

If you need help reaching the admin workspace first, see Using the Admin Workspace.

Reviewing audit activity before exporting

Before you click Export, spend a moment checking the audit activity list on the control page you opened. This helps you avoid downloading the wrong date range, the wrong project scope, or a list that still has old filters applied.

Start by reviewing the visible columns in the audit list. In Atloria, the most important details to verify are:

• the user who performed the action
• the timestamp or action date
• the affected item
• the action itself

These details tell you whether the list matches the audit trail you want to share or archive. For example, if you are preparing a project review, confirm that the affected items belong to the correct project. If you are checking organization-wide oversight, confirm that the list is not limited to one project only.

Use the list controls to narrow the results before export. Depending on what is available on the page, this may include sorting, filters, or a date-range selector. Sorting helps you bring the newest or oldest actions to the top. Filters help you focus on a person, item, or action type. A date range is especially useful when you only need activity for a release window, approval period, or monthly report.

A quick review like this can prevent incomplete exports. If the list is filtered to one user or one short date range, the export will likely reflect that limited view. If the page shows enterprise-wide activity, the export may include records from multiple projects.

Use this table as a simple check before exporting:

Exporting audit records from a project or enterprise view

Once the audit activity list shows the records you need, start the export directly from that list. Stay on the same control page where you reviewed the records, then use the Export action available on the audit records screen.

1. Open the audit activity list from either the project control page or the enterprise control page.
2. Review the current scope shown on the page so you know whether you are exporting a single project view or an enterprise-wide view.
3. Apply any filters, sorting, or date-range settings you want included.
4. Click Export from the audit records area.
5. If Atloria shows export choices, select whether to export the current filtered results or the full record set.
6. Complete the download.

The most important decision here is scope. If you start from a project control page, the export should reflect that project-level view. If you start from the enterprise control page, the export should reflect the broader oversight view. Always confirm this before downloading, especially if you plan to share the file with leadership, compliance reviewers, or project owners.

If export options appear before download, choose carefully. Exporting the current filtered results is useful when you already narrowed the list to a release period, a team member, or a specific action type. Exporting the full record set is better when you need a complete activity history from the current page scope.

After the file downloads, expect it to match the records shown on screen at the time of export. That means the file should reflect:

• the control page you used
• the current filters
• the selected date range
• the visible audit scope

For broader admin context around oversight screens, see Reviewing Security and Audit Controls.

Exporting version records for documentation history

When you need documentation change history rather than action tracking, move from the audit activity area to the version records area on the same control page. In Atloria, this is the better choice for release notes, revision reporting, and documentation history reviews.

1. Open the project control page or enterprise control page.
2. Switch from audit activity to version records.
3. Review the version list before exporting.
4. Click Export from the version records area.
5. Download the file after confirming any export options shown.

Before exporting, check the version-specific details in the list. The most useful fields to review are:

This export is different from an audit export because it focuses on documentation revisions rather than general activity. An audit export answers questions like “who performed this action?” A version export answers questions like “what changed in this documentation version, and when?”

Documentation Managers will usually prefer version records when preparing change-history reports, reviewing release readiness, or keeping a record of documentation updates over time. Project Administrators may also use version exports when they need a clean revision history without unrelated activity events.

If both lists are available on the same page, pause and confirm which one you are in before clicking Export. It is easy to export the wrong record type if you switch between tabs or sections quickly.

If your work also includes version review and release decisions, see Managing Documentation Versions Across the Release Cycle.

Choosing the right export for project reporting or enterprise oversight

The best export depends on two choices: where you start and what history you need. In Atloria, the starting page controls the scope, and the record type controls the meaning of the export.

Use the project control page when you are preparing a report for one project. This is the right place for project leads, Project Administrators, and Documentation Managers who need records tied to a single workspace. Use the enterprise control page when you need cross-project oversight, broader audit review, or an organization-level activity picture.

Then choose the record type:

• Use an audit export for action tracking
• Use a version export for documentation revision history

An audit export is better when you need to show who did what and when. This is useful for oversight, approvals, tracked actions, and activity reviews. A version export is better when you need to show how documentation changed over time, which version entries were updated, and who made those changes.

Filtered views also matter. If you filter the list before exporting, the file may only include that narrowed set of records. This is helpful when you want a focused report, but it can create problems if someone expects a complete history. Before sharing a file, verify:

• whether the page is project-level or enterprise-level
• whether filters are active
• whether the date range is limited
• whether you exported audit activity or version records

A few review habits can help avoid incomplete or duplicate exports:

• check the page title and section name before exporting
• clear old filters if you need a full history
• confirm the date range every time
• avoid exporting from both project and enterprise views unless you truly need both

If you are deciding between export types for release work, Controlling Version Visibility and Export Options can help with related decisions.

Fixing missing records, incorrect scope, and export problems

If your export does not look right, the cause is usually the current page scope, the selected list, or filters left on from an earlier review. In Atloria, it is worth checking the on-screen list carefully before exporting again.

If audit records are missing, start with the visible controls on the page:

• check whether a filter is active
• review the selected date range
• confirm whether you are on the project control page or the enterprise control page

A project page will only show project-level activity, so it will not include organization-wide records. If you expected a broader result, move to the enterprise control page and review the audit list there.

If the wrong records were exported, confirm that you started the export from the correct area. This is a common mistake when both audit activity and version records are available on the same control page. Audit exports and version exports are not interchangeable, so reopen the correct list and export again.

If you cannot see the Export action, the issue is usually access. Project Administrators commonly have project-level access, while broader export access may depend on admin workspace permissions. Documentation Managers may have access to version-related exports but not every enterprise-level record view. If the button is missing, compare your role with the page you are trying to use.

If the downloaded file does not match the on-screen list, refresh the control page first. Then reapply the intended filters, sorting, and date range. After that, review the visible records once more and run the export again. This is especially helpful if you switched between projects, tabs, or admin pages during the same session.

For related admin visibility and access topics, see Managing User Access and Administrative Permissions.

Overview

This guide focuses on exporting two types of records in Atloria: audit activity and version records. You can begin from either a project control page or the enterprise control page, depending on how broad your report needs to be.

The core idea is simple:

• open the correct control page
• choose the correct record list
• review the visible records
• export the results you actually need

Use audit activity when you want a history of actions. This is helpful for oversight, operational reviews, and checking who performed a tracked action. Use version records when you want documentation history. This is better for revision reporting, release support, and documenting how content changed over time.

This guide also explains how scope affects your export. A project control page gives you a project-specific view. The enterprise control page gives you a broader administrative view. If filters or date ranges are active, they may affect what appears in the downloaded file, so checking the list before export is an important part of the workflow.

You will also find troubleshooting help for common problems, including:

• missing records
• exporting from the wrong list
• access to export actions
• downloaded files that do not match the screen

If you are already comfortable reaching these work areas and just need help with the export process itself, the sections above give the quickest path. In the next document, continue with Managing Audit Exports and Activity Records to work more closely with exported audit files and ongoing record review.

Prerequisites

Before you export audit or version records in Atloria, make sure a few basics are in place. This will help you avoid access issues and prevent incomplete exports.

You should have:

• access to the project control page for the project you want to review, or access to the enterprise control page in the admin workspace
• a role that allows you to view record lists and use the Export action
• a clear idea of whether you need audit activity or version records
• the project name, reporting period, or review window you want to export

It also helps to know your reporting goal before you begin. For example:

• choose audit activity for action tracking and oversight
• choose version records for documentation change history
• choose the project control page for one project
• choose the enterprise control page for broader oversight

If you are not sure whether your account can reach the necessary pages, review:

• Accessing and Registering Your Atloria Account
• Signing In to Atloria and Solving Access Problems
• Using the Admin Workspace

Before exporting, it is also useful to confirm that the records you need are already visible on screen. If the list is empty, too short, or clearly limited to the wrong date range, fix that first rather than exporting and checking later.

After these basics are in place, you can move through the export steps in this guide and then continue to Managing Audit Exports and Activity Records for the next stage of audit export work.