> For the complete documentation index, see [llms.txt](https://guides.mangoapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.mangoapps.com/admin-guide/module-settings/crm/opportunities-access.md).

# Opportunities Access

### Overview <a href="#overview" id="overview"></a>

The **Opportunities Access** tab allows network admins to manage **who can view all opportunities** across the domain—regardless of their direct involvement. This is useful for giving visibility to executives, managers, or other key stakeholders without granting edit rights.

<img src="/files/8jJigzeFkezGMSUCwEMm" alt="" width="563">

From this tab, admins can:

* Grant **view-only** access to specific network users.
* Review the list of users who already have access.
* Revoke access at any time.

{% hint style="warning" %}
Users granted access through this tab can **only view** opportunities. They cannot **edit** opportunity details unless they are explicitly added to that opportunity.
{% endhint %}

***

### List of Users with View Access

This section displays all users who currently have domain-wide view access to opportunities.

* **Name:** The name of the user with access.
* **Email:** The user’s email address.
* **Action – Remove Access:** Click **Remove Access** to revoke a user's view permission. Once removed, the user will no longer see any opportunities unless they are assigned to them.

***

### Add Users

To grant view access to a new user:

1. Click the **Add Users** button.
2. Select one or more network users from the list.
3. Confirm to add them to the access list.

Once added, these users will be able to view **all opportunities** in the User Portal, but **cannot edit** them unless they are a participant on the specific opportunity.

***

### Best Practices

* Grant access **only** to users who need a holistic view of the sales pipeline.
* Periodically review and update the access list to maintain data privacy and security.
* Combine this setting with role-based permissions for a well-controlled CRM access strategy.