> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cyberopsource.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Navigating Compliance OS

> Learn the basic navigation model across the Client Portal and Compliance OS applications.

# Navigating Compliance OS

Compliance OS is a suite of coordinated applications rather than one large monolithic screen.

## Start from the Client Portal

Use the Client Portal to confirm:

* your client context,
* your authorized applications,
* current tasks,
* recent activity,
* useful summary metrics.

Then open the application that owns the work you need to perform.

## Use the right application for the task

| Goal                                             | Application           |
| ------------------------------------------------ | --------------------- |
| Complete an assigned stakeholder interview       | Interview Application |
| Review a published finding                       | Remediation Workspace |
| Work on a treatment or client action             | Remediation Workspace |
| Provide remediation evidence                     | Remediation Workspace |
| Review a risk or leadership decision             | Security Program Hub  |
| Review roadmap or program governance information | Security Program Hub  |

## Deep links and bookmarks

A deep link can be convenient, but your client-specific Client Portal remains the safest general bookmark because it establishes the correct context before you move into an application.

## Status indicators

Status names should be interpreted within the workflow that owns them. For example, an interview completion state is different from a treatment work state or a governance decision state.

When a status is unclear:

1. open the item,
2. review its details and activity,
3. confirm what action is expected,
4. contact the engagement lead if the workflow still appears inconsistent.

## Search and documentation

The documentation site is intended to answer common product questions without exposing private engagement data. Search for the workflow name, application, or task you are working on.

For engagement-specific conclusions—such as why a finding was rated a certain way—use the authorized application and your Cyber Op Source engagement team rather than relying only on generic documentation.