> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/posture.md).

# Posture

In a single pane of glass, DoControl consolidates end-user activity events and asset metadata across all your organization's SaaS applications.&#x20;

This unified view of SaaS activity covers all company departments, and allows you to discover the main risks of your assets and shadow apps, view recent alerts and remediation actions, and drill down to analyze your asset exposure in depth.

&#x20;You can display a different set of posture tiles across these SaaS apps:&#x20;

* [Google Workspace posture](/docontrol-user-guide/risk-management/posture/google-workspace-posture.md)
* [Microsoft 365 posture](/docontrol-user-guide/risk-management/posture/microsoft-app-posture.md)
* [High-level SaaS posture](/docontrol-user-guide/risk-management/posture/high-level-saas-posture.md)

{% hint style="success" %}
Generate an executive [ROI report](/docontrol-user-guide/risk-management/posture/risk-and-roi-report.md) to focus on your organization's main vulnerabilities and security risks.&#x20;
{% endhint %}

Your organizational posture highlights snapshot data, including:

* **Main vulnerabilities and security risks in your organization** - such as top exposed asset drives, top exposed private accounts, top sharing departments, and users with access to encryption keys.
* **Data provided by DoControl** - including security risk alerts, remediation actions, and workflow activity.
* **General information** - such as an overview of internal and external users, assets, and domains.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FDZdIcChhcrQPnWvNpCsa%2FGoogle%20Workspace%20posture.png?alt=media&amp;token=bc63ceb5-9463-4bf3-b12c-dc21e0355ef6" alt=""><figcaption><p>Single pane of glass displays your organizational posture in Google Workspace</p></figcaption></figure>

#### To display the posture page:

1. From the DoControl side menu, click **Posture.**
2. Click any linked data to drill-down and open the relevant view in DoControl.

{% hint style="info" %}

* Hovering over the top-right corner of each tile opens an explanation about the tile.
* These tiles are displayed by default, and cannot be removed.
* You can rearrange the tiles: select the handle ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fu4xA1fB1y2cAb69kbTy8%2Fimage.png?alt=media\&token=29f39223-3bad-4457-9c76-b95c22d607ab) on the left side of each tile and drag it to a new location. Click **Reset layout** to revert to the default tile display.
* The data in all tiles is refreshed every few hours (indicated in the top-right corner).
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docontrol.io/docontrol-user-guide/risk-management/posture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
