# Types

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

The **Types** tab in the CRM module allows network admins to manage the different types of opportunities tracked within the system. Opportunity types help categorize deals for better reporting and organization.

<img src="/files/1n9noY8rwyjzRr9HTfOT" alt="" width="563">

From the **Types** tab, admins can:

* View and manage all opportunity types configured on the domain.
* Reorder types to suit the team's workflow.
* Edit or delete pre-shipped (default) opportunity types.
* Create and add new custom opportunity types.

***

### Opportunity Types List

This list shows all current opportunity types on the domain.

**Reorder:** Drag-and-drop the listed types to rearrange their order as needed. This order is reflected in the User Portal.

**Edit Pre-shipped Types:** Click **Edit** to rename an existing type.

***

### Type Actions

Each opportunity type in the list includes the following actions:

* **Edit:** Modify the label of the type to match your team's naming conventions.
* **Remove:** Delete the type from the domain.

{% hint style="success" %}
Deleting a type **only removes the association** of that type from the opportunities in the User Portal. The opportunities themselves remain unaffected.
{% endhint %}

***

### Adding a New Opportunity Type

To create a new opportunity type:

1. Click the **+ Add a new Opportunity Type** link at the bottom of the type list.
2. Enter a name in the **Type Name** text box. (e.g., "Startup", "Enterprise", or "Partner Deal")
3. Click **Add** to create the new type.
4. Optionally, use drag-and-drop to reorder the new type within the list.


---

# 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://guides.mangoapps.com/admin-guide/module-settings/crm/types.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.