> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/settings/permission-groups/permission-group-crm-won-and-lost-opportunities.md).
# Permission Group - CRM - Won and Lost Opportunities
In the CRM, the option **“Won and Lost Opportunities”**, located within **Permission Group**, defines which users will have access to the **Edit, Change, or Reopen** opportunities marked as **Won** or **Lost**.
By granting this permission, the selected users will be able to view and carry out actions related to these opportunities in the CRM, according to the configured access level.
ℹ️ **Important:**\
If permissions are not assigned, **only administrators will have access to the features**, since administrator users have **full CRM visibility**.
***
## 🛠️ How to manage permissions in SprintHub
Follow these steps:
1️⃣ Access **System Settings** ⚙\
2️⃣ Click on **Permission Group**\
3️⃣ Choose one of the options:
* ➕ **New Group** – to create a permissions group from scratch
* ✏️ **Edit** – to modify an existing group
4️⃣ Check the ☑️ box to **enable the Won and Lost Opportunities feature**\
5️⃣ Finish by clicking **💾 Save Changes**
{% embed url="" %}
***
## How does it work?
When this option is **enabled**, the system allows the user to access the actions of:
* **Edit** opportunities marked as Won or Lost;
* **Change** the opportunity owner;
* **Reopen** opportunities closed as Won or Lost.
In addition, the user will be able to perform these actions even on opportunities owned by others, according to CRM permissions.
When the option is **disabled**, the user will not have access to the **Edit, Change, or Reopen** closed opportunity features, being restricted only to the system's default permissions.
***
## Use cases
**✔ Option enabled – Manage Won and Lost opportunities**
The user will be able to:
* Edit opportunities marked as **Won** or **Lost**;
* Change the opportunity owner;
* Reopen closed opportunities to continue the sales process;
* Have greater autonomy in managing the sales funnel.
This setting is recommended for users who follow or manage sales processes.
**❌ Option disabled**
The user:
* Will not be able to edit Won or Lost opportunities;
* Will not be able to change the owner of these opportunities;
* Will not have permission to reopen closed opportunities.
***
## When should you use this option?
This permission is commonly used for profiles that need to manage already closed opportunities, such as:
* Sales managers;
* System administrators;
* Team leaders;
* Sales supervisors;
* Users responsible for managing the sales funnel.
***
## Practical example
A sales manager needs to review an opportunity marked as **Lost**, change the support owner and reopen the negotiation for a new attempt at conversion.
With the option **“Won and Lost Opportunities”** enabled, they will be able to access the opportunity and perform actions such as **Edit**, **Change owner** or **Reopen** the record normally.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sprinthub.com/en/topics/settings/permission-groups/permission-group-crm-won-and-lost-opportunities.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.