> For the complete documentation index, see [llms.txt](https://docs.pentest.ws/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentest.ws/collaboration/access-control-list.md).

# Access Control List

**Example URL:** <http://localhost:7897/e/{engagement.id}/console>

In a Pro Tier's Shared Engagement, the owner of an Engagement (the user who created the Engagement) can grant Read Only or Full Access to teammates on an individual basis.

![Shared Engagement's Access Control](/files/evwY2ge5oQL21KMFmxsC)

Alternatively, you can choose to make an Engagement Public, granting full access to all teammates. Engagements default to Restricted Access with all teammates in the No Access bucket.&#x20;

An Engagement’s Access Control is available in the Console tab.

## Team Missions

Shared Engagements appear on the remote user’s [Dashboard](/getting-started/dashboard.md) under the Team Missions section.

![Team Missions](/files/RZSOCDSWjuWi4LutwYPA)

* In the example above, we are logged into the "alice" account.&#x20;
* The user "demo" has given "alice" Full Access to the "Demo" engagement.
* The user "bob" has made his "ABC Widgets" engagement Public

{% hint style="info" %}
**Team Missions** only appear if you have access to another user's Shared Engagement.
{% endhint %}

## Tier Availability

**Access Control** is available on **Pro Tier.**