> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/account-intelligence/opportunities.md). # Opportunities Track opportunities and their account context, organize views, and connect CRM records. Opportunities track potential business with an account. Create them directly in Pylon or work with opportunities connected to your [CRM](/pylon-docs/integrations/crm.md). Each opportunity has a name, an associated account, and custom fields for the details your team tracks. {% hint style="info" %} Opportunities are available on select plans — contact your account team for availability. {% endhint %} ## Create and edit opportunities Open [Opportunities](https://app.usepylon.com/customers/opportunities) under **Customers**, then click **Add Opportunity**. Enter a name, select an account, and fill in the required custom fields shown in the form. Click **Add opportunity** to create it. Click an opportunity to open its sidebar. You can edit its name, change its **Account**, and update its custom field values. The account's **Opportunities** page also shows opportunities associated with that account. Creating or updating an opportunity requires permission to edit Accounts and access to edit the associated account. Sharing a view doesn't grant permission to edit its underlying accounts or records. ## Fields and account context Use **Customize columns** in the **Layout** menu to choose and reorder columns. You can show opportunity fields alongside account information such as **Account owner**, **Account tags**, **Primary domain**, **Account type**, and **Slack channel**. Opportunity custom fields let you track your own stages, amounts, dates, owners, or other details. The available fields depend on your workspace's configuration. See [Custom Fields](/pylon-docs/platform/custom-fields.md). ## Search, filter, and group Use the search box and filters to narrow the list. Filters can include opportunity properties, account properties, and custom fields. Use advanced filter groups when you need to combine conditions. The **Layout** menu includes: * **Sort by**: choose a field and ascending or descending order. * **Group by**: group by **Account**, **Account owner**, **Account tags**, or a supported opportunity custom field. Choose **No grouping** to return to a flat list. * **Show empty groups**: choose whether groups without matching opportunities appear. * **Row height**: choose **Compact** or **Comfortable**. * **Format by value**: apply conditional formatting to make matching values stand out. ## Saved views Use **Create View** to save your filters and layout with a name and icon. Choose who can view and edit it, and optionally add it to a folder or star it. Use **Save to View** to update a view you can edit. When saving a shared view, Pylon asks whether to save changes for everyone or use **Duplicate View** to create a separate view. A teammate who can only view it can make temporary changes or create a separate view, but can't overwrite the shared view. ## CRM records Connect your [CRM integration](/pylon-docs/integrations/crm.md) to sync opportunity data. In the integration's opportunity mapping, link a Pylon opportunity to its CRM record. Use **Search by name** to find a record when needed. Configure the fields you want synced under **Field syncs**; the mapping and field configuration determine which records and values are connected. For a linked opportunity, the sidebar shows **Open in** followed by your CRM's name. Use it to open the original CRM record. An opportunity's account association is separate from its link to a CRM opportunity: check both when matching records. ## Export to CSV Click **Export to CSV** to download the opportunities matching your current filters and search, in the selected sort order. The export includes **Opportunity ID**, **Name**, and the selected columns, including account fields when you've included them. The export fetches all matching pages, rather than only the rows currently displayed. Keep the page open while it prepares the download. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.usepylon.com/pylon-docs/account-intelligence/opportunities.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.