# Understand Source Analysis Processing

Source analysis processing helps Atloria interpret the source material connected to your project so it can organize findings into useful documentation context. Understanding this process helps you choose the right project, review the available source information, and locate the documents produced from that analysis.

## Overview

Atloria source analysis works with the source material associated with your project and makes that information available for documentation work. As an administrator, you typically use this process when you need to confirm that a project’s source is available, review the project’s technology context, or find documents that were created from the analyzed source.

The analysis process supports source-driven documentation rather than requiring you to manually describe every application area. When source analysis is available for a project, you can use the **Source** and **Atloria Stack** actions to review the source-oriented context that Atloria has identified.

After analysis results are available, related output is managed through **Documents**. The documents area lets you select a project, search for generated or existing documentation, and manage documents when they are no longer needed.

> 📷 _Screenshot pending: Source analysis entry area showing the View Source, Atloria Stack, Source, and Documents actions._

## Prerequisites

Before you begin, make sure you have the following:

- Access to the Atloria project you want to review.
- A project with source material available to Atloria.
- Permission to view project source and documents.
- A supported browser session signed in to Atloria.
- A clear understanding of which project you want to inspect, especially if your organization manages multiple projects.

## Step-by-Step Instructions

1. Open the Atloria project that contains the source material you want to understand.

2. Click **Source** to open the project’s source-focused view.

3. Review the source information displayed for the selected project.

4. Click **View Source** when you need to inspect the available source material more directly.

5. Use the displayed source information to confirm that you are reviewing the intended project and application area.

6. Click **Atloria Stack** to review the technology and application context identified for the project.

7. Review the stack information to understand the types of application elements Atloria may use when organizing analysis findings.

8. Click **Documents** to move from source context to the project’s documentation output.

9. Select the project when the page displays **Select a project to view documents**.

10. Enter a keyword in **Search documents...** to find documentation within the selected project.

11. Enter a broader term in **Search documents, categories, projects...** when you need to search across document names, categories, or projects.

12. Select a document from the results list to review documentation created from or related to the analyzed source.

> 📷 _Screenshot pending: Documents area showing the “Select a project to view documents” message and the “Search documents...” field._

## Tips and Best Practices

- Start with **Source** before reviewing documents. This helps you verify that you are working with the correct project context before interpreting document output.

- Use **Atloria Stack** to orient yourself to the application’s overall structure. Stack information is especially useful when similar projects use different technologies or when you need to distinguish frontend, service, and data-related areas.

- Select a project before searching for documents. If the documents page shows **Select a project to view documents**, Atloria cannot display project-specific documentation until you choose one.

- Use specific terms in **Search documents...**. For example, search using a feature name, business area, or document title rather than a broad term such as “app.”

- Use **Search documents, categories, projects...** when you do not know which project contains the document. This broader search is useful for administrators who oversee multiple projects or documentation categories.

- Treat document deletion as permanent. The **Delete Documents** action is accompanied by the confirmation text **I understand, delete**, indicating that you should verify your selection before completing the action.

- Keep source review and document management separate. Use **View Source**, **Source**, and **Atloria Stack** to understand analysis context; use **Documents** to locate, review, or manage the resulting documentation.

## Related Pages

- [Manage Project Documents](#)
- [Search Documents and Categories](#)
- [Delete Documents](#)
- [Review Atloria Stack Information](#)
- [Authorize Atloria Access](#)

## Troubleshooting

### You see “Select a project to view documents”

You have opened **Documents**, but no project is currently selected.

1. Select the project you want to review.
2. Return to the documents list.
3. Use **Search documents...** after the project’s documents are displayed.

### You cannot find an expected document

The document may belong to another project, may use a different title, or may be categorized differently.

1. Clear the value in **Search documents...**.
2. Search again using a shorter or more specific keyword.
3. Use **Search documents, categories, projects...** to search across projects and categories.
4. Confirm the project source by returning to **Source** or **View Source**.

### You are considering deleting documents

Deleting documents can remove information that other users rely on.

1. Click **Delete Documents** only after reviewing the selected documents.
2. Confirm that the correct project and documents are selected.
3. Use **I understand, delete** only when you are certain the documents should be removed.