> For the complete documentation index, see [llms.txt](https://docs.claret.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claret.app/sell/sales-collaboration/quick-start.md). # Quick Start: Sales Collaboration ## What You'll Learn Sales Collaboration is a planning tool that allows people across your organization to participate in creating a sales plan at any level in the Item and Customer Group hierarchies. After this guide, you'll be able to navigate to Sales Collaboration, select a view, understand the grid layout, and enter or update sales plan data. ## Before You Begin Your admin should have already: * Set up Items, Customer Groups, and Item @ Customer Groups * Configured at least one Sale Type (e.g., Budget, Forecast) * Created a workspace view for you to use If the module page is empty or you can't see any data, check with your admin that the setup is complete. See [Setting Up Sales Collaboration](/using-claret/getting-started/setting-up-modules/setting-up-sales-collaboration.md) for what's required. ## Step 1: Access Sales Collaboration Navigate to **Sell > Sales Collaboration** in the left navigation menu. ## Step 2: Select a View 1. Click the **view name** in the top-right of the header bar 2. Select a **workspace view** from the dropdown or stick with the current selection — this is a view your admin has set up for the team 3. The grid will load with the data configured for that view

A grid will load based on the view configuration

{% hint style="info" %} If no workspace views are available, you can create a personal view. See [Using Sales Collaboration](/sell/sales-collaboration/using-sales-collaboration.md) for detailed view configuration instructions. {% endhint %} ## Step 3: Navigate the Grid The Sales Collaboration grid shows your sales data organized by hierarchy: * **Left column** — shows either Items or Customer Groups, depending on the view's hierarchy layout. Click the arrows to expand and see sub-levels. * **Top header** — shows the alternative hierarchy. Use the dropdown at the top to select which level you want to view data at. * **Data columns** — show monthly values for each row type configured in the view (e.g., Budget, History, Forecast). To drill into more detail: * **Expand hierarchy rows** — click the arrow next to a row to see its children * **Change the hierarchy level** — use the dropdown picker at the top to view data at a different aggregation level (e.g., from "All" down to a specific region)

Sales Collaboration with the Item hierarchy expanded

## Step 4: Enter or Update Sales Data If a row is configured as editable (set by your admin in the view configuration): 1. Click on a **cell** in an editable row for the month you want to update 2. Enter the new value 3. The value is saved automatically

Editable cells are highlighted so you can see where data can be entered

{% hint style="warning" %} Be careful when editing values. Any changes you make will replace existing data for that cell. If you're unsure which rows are editable, check with your admin or look at the view configuration. {% endhint %} ## Step 5: Understand Reconciliation When data is entered at a higher hierarchy level (e.g., "All Domestic" rather than individual customer groups), Claret automatically **reconciles** the data down to the lowest Item @ Customer Group level. This means: * You can plan at whatever level makes sense for your role * The detailed data that supply chain teams need is generated automatically * Reconciliation runs when you save data at a higher level

How reconciliation flows higher-level data down to the Item @ Customer Group detail level

For more on how reconciliation works, see [Collaborating on Sales Data](/sell/sales-collaboration/collaborating-on-sales-data.md). ## Understanding the Data | Row Type | What It Shows | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | **Sale Type** (e.g., Budget) | A single sale type's data for a chosen calendar | | **Hist/Fcst** | History for past months, forecast for future months — switches at the configured forecast start date (in Application Settings) | | **Equation** | A calculated row (e.g., the difference between Budget and Hist/Fcst) | Trend charts may also appear as a column if enabled in the view, showing a sparkline of each row's data over time. ## Common Questions ### Can I edit any cell in the grid? Only cells in rows marked as "can edit" in the view configuration are editable. Your admin controls which rows are editable in workspace views. If you create a personal view, you can set this yourself. Your admin may have also constrained your permissions to only be able to edit certain items and customer groups. If you are not able to edit data you are expecting to, contact your admin. ### What happens when I enter data at a higher hierarchy level? The value is reconciled down to the lowest Item @ Customer Group level proportionally. This means downstream modules like Make Planning receive the detail they need. ### How do I see data for a different time period? Time periods are tied to the calendar configured in each view row. To see a different fiscal year, your admin can add another row with a different calendar, or you can create a personal view with the calendar you need. --- # 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.claret.app/sell/sales-collaboration/quick-start.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.