> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/sales-portal/sales-portal-overview.md). # Sales Portal Overview The Sales portal is the workspace for **sales reps** — a portal of its own, signed into with the **Sales** role, where a rep works their assigned **book of business**: the accounts an administrator has put in front of them. It is deliberately separate from the customer success portal. Sales and support start from similar capabilities, but they are different jobs, so each role gets its own portal, its own pages an admin can tailor, and its own permission profiles — access and screens can evolve for one team without touching the other. ## What sales reps can do * **Work an accounts list scoped to their book** — signing in lands on **Accounts**, a list containing exactly the accounts assigned to the rep. When the billing system behind the list is having trouble, the portal says so honestly — a banner names the system and suggests whether to retry or contact an administrator — rather than showing an empty list that reads as "you have no accounts." * **Open a full account workspace** — the account detail page mirrors the customer success workspace in depth: the account header and key financial metrics, a churn risk panel, and tabbed sections for **subscriptions**, **billing & invoices**, the **Timeline**, **Subaccounts**, and the **Audit Trail**. Rather than duplicate that documentation here: the workspace mirrors [Working with an Account](/product/customer-success-portal/working-with-an-account.md), and the Timeline is covered in [The Account Timeline](/product/customer-success-portal/account-timeline.md). * **Act on a customer's behalf** — launch self-service [journeys](/product/journeys-and-pages/journey-basics/journeys-overview.md) (plan changes, cancellations and saves) from within the account workspace. * **Leave notes the sales team can keep to itself** — see [Team-only notes](#team-only-notes-stay-with-the-sales-team) below. * **Build and send quotes** — once an administrator grants quote access on the Sales profile; see [Quotes](/product/sales-portal/quotes-overview.md) and [the access note](#quotes-in-the-sales-portal) below. ## Granting access Three things put an account list in front of a rep: 1. **The Sales role.** On the user record (**Settings → Users**), set **Role** to **Sales**. Sales users sign in to the Sales portal — not the customer success portal, and not the admin console. 2. **A Sales-role profile.** Every workspace ships with a seeded **Sales Default** profile that gives a new sales team similar coverage to support staff out of the box. It is managed independently — an admin can create additional Sales profiles (a senior/junior split, for example) exactly as for other roles. See [Profiles & Permissions](/product/using-peakcommerce/profiles-and-permissions.md) and [User Roles](/product/using-peakcommerce/users-and-user-roles/user-roles.md). 3. **A book of business.** Admins define which accounts each rep sees two ways, which combine: **territory rules** — condition-based rules evaluated against the billing system (for example, accounts above a balance or MRR threshold) — and **direct assignment** of individual accounts. An account outside the rep's book is not reachable: opening one shows *"This account isn't part of your assigned book of business. Ask an admin to assign it to you, or return to your accounts list."* If an admin removes an assignment while a rep has the account open, the workspace says so and returns them to the list — access changes take effect live, not at next sign-in. System administrators can also open the Sales portal directly, which is useful for verifying what a rep will see. ## Team-only notes stay with the sales team Notes written on the account Timeline carry a visibility choice: **All staff** or **your own team only**. In the Sales portal, "team only" means the **Sales team** — a sales-team note is not visible to CSR staff or partner users, and a CSR-team note is likewise not visible to sales reps. Two deliberate exceptions apply everywhere: the note's author always sees their own note, and system administrators see everything. So a rep can record deal context ("pushing for the annual plan, revisit in March") without it surfacing in a support interaction — and support can do the same in reverse. The full note feature set — categories, pinning, CRM logging — is documented in [The Account Timeline](/product/customer-success-portal/account-timeline.md). ## Tailoring the Sales portal's pages Sales is a first-class **portal type** in the page editor, so what reps see is buildable, not fixed: * The **Pages** list in the admin console has a **Sales Portal** filter alongside Customer, CSR, and Partner. * Three Sales pages are seeded for every workspace — **Sales Dashboard** (metrics, the assigned-accounts list, and a journey launcher), **Sales Search**, and **Sales Account Detail** — and an admin can edit them or add new ones. * The editor offers a dedicated **Sales component set** (account list, account header, churn-risk panel, subscription list, tabbed sections, and more), so a tailored Sales page composes from the same building blocks as the stock ones. ## Quotes in the Sales portal The quote screens — the list, the editor, and the send-for-approval flow — are wired into the Sales portal, but the stock **Sales Default** profile does not grant the **Quotes** resource, so a new rep won't see them until an administrator grants it (open the Sales profile's **Resource Permissions** and enable **Quotes**). That's a setup step, not a defect — it lets each organization decide whether reps quote directly. See [Quotes](/product/sales-portal/quotes-overview.md) for where quotes live and how the permission behaves. ## Current limits, honestly * **The navigation bar shows one tab today: Accounts.** The other Sales pages — search, analytics, the escalation queue, quotes — exist and work, but are reached from within flows and links (or from a link an admin adds to a tailored Sales page) rather than from the portal's navigation. * **The in-portal chat assistant is the billing assistant** — the same billing-focused agent the support portal uses. A Sales-specific assistant, once one is configured for the workspace, is picked up automatically. --- # 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.peakcommerce.com/product/sales-portal/sales-portal-overview.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.