# 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](https://1013683115-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHecEAvxd6Z8cSug6DhWr%2Fuploads%2F9JHlye8j7Gdywk1JdjP2%2Fimage.png?alt=media\&token=260790ec-e94c-4126-9caa-27ad22a27349)

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](https://docs.pentest.ws/getting-started/dashboard) under the Team Missions section.

![Team Missions](https://1013683115-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHecEAvxd6Z8cSug6DhWr%2Fuploads%2F9kXsqF3DwsUGqsXNZbGk%2Fimage.png?alt=media\&token=1013fb94-d266-45cc-a3df-0828fcf9e6c6)

* 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.**