# Project changes and audit

Use this page to inspect proposed documentation changes, review their details, and read
project activity in the audit trail.

## Project changes and audit

A project change request is a proposed documentation change that you inspect before it
is closed or merged. The project audit trail is the event list for project activity. Use
the change request when you need to review proposed content; use the audit trail when you
need to inspect recorded project events.

| If you need to… | Go to |
|---|---|
| Review a proposed documentation change | [Review a documentation change](#review-a-documentation-change) |
| Inspect conflicts, statuses, or messages | [Handle statuses, conflicts, and messages](#handle-statuses-conflicts-and-messages) |
| Read project events or export them | [Review project audit events](#review-project-audit-events) |
| Continue after a merged change | [Know what happens next](#know-what-happens-next) |
| Review versions | [Project versions](doc:project-versions) |
| Review audit information elsewhere | Audit reference |

## Before you start

You need access to a project and a reachable project-specific route before you can inspect
its changes or audit trail. The changes list uses the signed-in session, and the audit
page loads events for the selected project.

These surfaces do not include form fields or required markers. Use the action filter on
the project audit page; use the Audit reference page for broader audit guidance.

## Find a project change or audit trail

Use the project list to open the project whose documentation changes or activity you need
to inspect. The project-specific changes route redirects to the project dashboard's
Changes tab. An existing change row opens its detail route.

**Prerequisites**

- You have access to a project.
- You know whether you are looking for a proposed documentation change or an audit event.

**Steps**

1. Open the project list.
2. Choose the project surface that matches your task:

   | If you need to… | Open |
   |---|---|
   | Review a proposed documentation change | The project Changes surface |
   | Inspect project activity | The project Audit Trail |

3. In the Changes surface, select a **Change row** to open its detail route.
4. On the detail route, select **Back to Changes** to return to the Changes surface.

![Project list with project rows and their open and delete actions](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/e35d92785acbd1589eb9f85ac91e2936.png)

**Result:** The selected project Changes surface, change detail route, or Audit Trail is
on screen.

## Review a documentation change

Use the change request's summary to identify the proposal and its activity entries to
follow its history. A diff is the file-by-file view of additions, deletions, sections,
hunks, and lines; use it to inspect the affected documentation.

A conflict section places the current text beside the proposed text so you can choose
which text to keep.

**Prerequisites**

- You have opened a change request from the Changes surface.

**Steps**

1. Read the change title, kind, status, commit range, file count, and conflict count in
   the detail header.
2. Read the activity entries for Created, Conflicts detected, and Merged when they are
   present.
3. Review each affected file in the diff.
4. Compare the current and proposed text in each conflict section when conflicts are
   present.
5. Choose one resolution for each conflict section.

   | If you want to… | Select |
   |---|---|
   | Keep the current page text | **Keep mine** |
   | Use the proposed page text | **Use proposed** |
   | Change the proposed text before applying it | **Edit inline** |

6. Select **Apply resolution** after choosing a resolution for every section.
7. Choose the action that matches the proposal:

   | If… | Select |
   |---|---|
   | The proposal is open and has no conflicts, and you need to inspect the rendered preview | **Open preview** |
   | The proposal should not be merged | **Close** |
   | The proposal is open and has no conflicts, and it is ready to merge | **Approve & merge** |

**Result:** The change detail remains on screen with its summary, activity, affected files,
diff, and the review controls available for its current status.

## Review project audit events

The project audit trail is a chronological event list for project activity. Use it to
read the time, actor, action, entity, and details associated with each returned event.

**Prerequisites**

- You have opened the project Audit Trail.

**Steps**

1. Select an action in **All Actions** to filter the event list.
2. Read the Time, Actor, Action, Entity, and Details columns.
3. Select an audit event row to expand its metadata.
4. Move through the event pages when the event list has more than one page:

   | If you need to… | Select |
   |---|---|
   | Return to the previous page | **Previous** |
   | Open the next page | **Next** |

5. Select **Export CSV** to request a CSV export of the project audit trail.

**Result:** The project audit trail shows the selected event view, expanded metadata, page
range, or export control.

## Handle statuses, conflicts, and messages

The Changes surface groups requests by status, and the detail surface changes its actions
when a request is open, conflicted, preparing, merging, merged, or failed. Match the
status on screen to its available path.

| When the screen shows… | The available path is… |
|---|---|
| Open | **Open preview**, **Close**, and **Approve & merge** are available when there are no conflicts. |
| Merged | **View on Versions** is available to continue to the project versions. |
| Closed | Review these requests in the Closed filter. |
| A conflict | **Close**, **Refresh diff**, and conflict-resolution cards are available. |
| Preparing | Wait while the branch is being prepared. |
| Merging | Wait while the merge is in progress; the Merging control is disabled. |
| Failed | **Retry merge** is available only when the failure is retryable. |

Match each message to the situation that produces it.

| Situation | Message |
|---|---|
| Change-list error | `Failed to load change requests` |
| Change-list loading | `Loading change requests...` |
| Change-list empty state | `When your docs are edited, regenerated, or updated by an agent, the proposed changes appear here for review before they land.` |
| Detail loading | `Loading change request…` |
| Detail loading error | `Failed to load change request` |
| Preview cannot be shared | `Publish this project to share a rendered preview of the change.` |
| Preview-link error | `Failed to create preview link` |
| Conflict banner | `Conflicts to resolve — your docs changed since this was proposed. Resolve each section below, then merge.` |
| Conflict choice required | `Choose a resolution for every section` |
| File has no line changes | `No line-level changes in this file.` |
| Change has no diff | `No diff available for this change request.` |
| Audit export error | `Export failed` |
| Audit loading | `Loading...` |
| Audit has no events | `No audit events` |

## Know what happens next

After you finish reviewing a change request, the next destination depends on the action
you select. A merged request offers **View on Versions**. The audit trail remains the place
to inspect project events, while the Audit reference page covers audit information more broadly.

| After you… | Continue to… |
|---|---|
| Review a merged change | [Project versions](doc:project-versions) |
| Need broader audit guidance | Audit reference |
| Need the project list again | [Projects overview](doc:projects-overview) |
| Encounter a general application error | General error messages |

**Result:** You know which follow-on page to open for version review, audit reference
information, project navigation, or general error guidance.