# Engagement Console

**Example URL**: <https://pentest.ws/e/{engagement.id}/console>

## Pro Tier Console

<figure><img src="/files/5NLwohtPJHgJeHFyK9sw" alt=""><figcaption></figcaption></figure>

The **Engagement Console** is the central view for managing an individual engagement. From here, you can update engagement details, track notes, and control access.

### Engagement Details

At the top of the console you can edit the core details of the engagement:

* **Engagement Name** – The display name of the engagement.
* **Client** – The client associated with the engagement.
* **Status** – Current state (e.g., In Progress, Client Delay, Planned).
* **Starts At / Ends At** – Engagement timeline dates.
* **Summary** – A short description of the engagement.

Additional controls allow you to **Print**, **Export**, or **Delete** the engagement.

### Engagement Notes

Below the summary is a rich text editor for **Engagement Notes**. These notes can capture methodologies, progress updates, or other details relevant to the engagement. Notes support rich formatting, links, and images.

### Access Control

The Access Control section defines who can see and manage the engagement.

* **Restricted / Unrestricted** – Restricted engagements are visible only to the users listed. Unrestricted engagements are visible to all users.
* **No Access** – Users with no visibility into the engagement.
* **Read Access** – Users who can view the engagement but cannot make changes.
* **Full Access** – Users with full administrative control over the engagement.

In the example shown:

* *Charlie* and *David* have **No Access**.
* *Bob* has **Read Access**.
* *Admin* has **Full Access**.

This structure makes it easy to control visibility and collaboration across your team.

## Free Tier & Hobby Tier Console

![Free Tier & Hobby Tier Console](/files/i0ZbTQGQlXRAeZbed84h)

On Free & Hobby Tier the Engagement Console displays a bar graph showing the distribution of Host Type and Operating System Types.

## Tier Availability

**Console** is available on all tiers.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pentest.ws/getting-started/engagement-console.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.