Skip to main content
Pipeline agents are always-on discovery jobs that hunt for pipeline while you focus on the deals in front of you. Each agent is tied to a seller profile, sources companies from one or more places you choose, evaluates them against a focus you author with ShiftUp, and surfaces graded candidates in a company-centered Agent results list. Activating a candidate creates a full Sales Strategy with a scorecard, deal outlook, and stakeholder roster ready to work.
This page documents the redesigned Pipeline agents experience shipped in September 2026. If your org has not upgraded yet, see Pipeline agents (legacy) for the earlier experience.
For a step-by-step guide, see Building a Pipeline Agent.

How pipeline agents work

  1. Configure — a wizard captures the agent’s seller profile, its focus (customer focus, starting idea, priority areas, and custom filters), the sources it will scan, and how it tops up your review queue.
  2. Discover — the agent scans the selected sources: monitored accounts, Salesforce Accounts (picked, from a list view, or matching custom criteria), uploaded CSV or XLSX company lists, and market discovery.
  3. Evaluate — each eligible company is researched and scored on a six-dimension scorecard (need and urgency, seller fit, commercial potential, stakeholder access, decision friction, evidence quality) plus any custom priority areas. Each company gets a quality grade of A+, A, B, or C and a decision brief.
  4. Review — candidates land in Agent results on the agent’s Overview. You can group, filter, and search, then activate or dismiss rows. Each run stops once your review queue is back to the size you chose.
  5. Activate — accepting a candidate creates a full opportunity strategy in ShiftUp. By default each strategy is assigned to its account’s Salesforce owner (resolved live at activation), with fallbacks and manual override available.

Create an agent

Open Pipeline agents in the left sidebar and click New pipeline agent. The create wizard has four steps:
  1. Focus — pick a seller profile. ShiftUp uses the profile you started from, or selects the first active one. Right under the profile, Who should it focus on? offers Any (selected by default), New customers, or Existing customers. Then choose what to look for:
    • Companies like your best customers — the auto mode. The focus follows the seller profile’s ideal customer profile.
    • A specific focus — ShiftUp suggests exactly four idea cards written for the customers you chose. Four placeholder cards hold their places while the ideas load. Pick a card to send it to the plan as written, or choose Something else to describe the focus in your own words. Changing who to focus on brings new ideas and clears a picked card.
  2. Plan — ShiftUp builds the plan from your Focus choices: an agent name, the focus text (in specific-focus mode), a set of priority areas the agent grades every company against, and a set of custom filters that layer on top of the built-in universal filters. While the plan is written, one line under the progress phases summarizes what ShiftUp is working on and updates as the work moves on. Refine the plan in natural language (“focus on manufacturing under 500 employees”, “drop the healthcare block”). Going Back cancels a running build or refinement, and its result is never applied. Returning to Focus and continuing rebuilds the plan with the changed choices.
  3. Sources — turn on one or more source tiles. Each tile you check opens its own setup card below:
    • Monitored accounts — the account plans the agent already watches.
    • Salesforce accounts — Salesforce Accounts you pick, a Salesforce Account list view, or custom criteria. See Choose Salesforce accounts.
    • Uploaded lists — a CSV or Excel list of companies, cleaned by the list assistant.
    • Market discovery — ShiftUp finds companies outside your CRM. Requires the Enable Pipeline Account Discovery setting.
    A configured card collapses to a one-line summary with a Change button. A card that still needs setup stays open and shows the reason. Below the cards, What this agent researches summarizes the combined scope. One shared, optional Companies to skip section applies to every source, so you can exclude current customers or partners once. Name the companies to skip with Pick accounts, List view, Custom criteria, or Upload a list. Each company and analysis scope is researched once per run. Explicit picks and uploaded targets share a limit of 10,000 distinct company-and-scope targets. Account picks and market discovery pins stay at 1,000. Overlapping sources count once, and different Salesforce Accounts remain separate.
  4. Review — set when and how much the agent tops up your review queue with one sentence:
    When I click Run | Each week, top up my pipeline so it has 10 | 100 | 1,000 recommendations ready to review.
    Each choice opens a keyboard-accessible menu. New agents default to When I click Run and 100. See How runs top up your queue. A summary card reads back what the agent looks for, its plan, and its sources, each with Edit, followed by What happens next. For a weekly agent, the card estimates the first weekly top-up as one week from today. Attach any files the agent should read, such as playbooks, case studies, or product sheets, at the end of this step.
Confirming the wizard creates the agent, starts its first run, and opens the agent’s detail view. The agent takes its name from the plan. New agents only recommend companies graded A or better. Change the minimum grade and add additional guidance later in Settings → Advanced. Failed creation keeps your inputs for correction and retry. New agents do not set a revenue goal.

How runs top up your queue

Each run refills your review queue to the size you chose: 10, 100, or 1,000 recommendations ready to review. The size is the only run limit you set. Use 10 for a short list of your strongest fits, 100 for a steady list to review, or 1,000 for broad coverage that takes longer to fill.
  • When I click Run — the agent tops up only when you click Run now.
  • Each week — the agent tops up automatically once a week. Clicking Run now starts a run immediately, and the next weekly top-up then comes a week after that run finishes.
When a run starts, ShiftUp counts the open spots in your queue and sets a research budget of about 10 companies per open spot. The run checks companies in this order:
  1. Companies from your own sources that the agent has never checked.
  2. Leftover companies from earlier runs.
  3. Market discovery list builds. Each run builds at most ten lists of up to 1,000 companies and stops building after a list finds no more good fits.
  4. Re-checks of your own companies, only when market discovery has no more to offer.
A run stops when the first of these happens:
  • The queue is full.
  • The research budget is used up.
  • The sources and market discovery run out of companies to check.
When the queue is already full, a run starts no new research. It still refreshes the recommendations waiting for review and starts any due strategy refreshes. If there aren’t enough good fits, you may have fewer recommendations ready to review than the size you chose. If you save a new size or minimum grade while a run is still starting research, the change applies to the rest of that run. A larger size counts from where the run started and adds the companies the run had left for later. Companies already being checked keep the grade they started with. A run that has stopped starting research keeps its size, and the next run uses the new one. Agents created before queue top-ups keep their saved values until you save. ShiftUp reads an older review queue threshold as the next size up: 1 to 10 reads as 10, 11 to 100 as 100, and anything higher as 1,000.

Clean an uploaded list with the list assistant

When your ShiftUp backend supports list cleaning, an uploaded list goes to the list assistant before anything runs. The assistant reads every row, splits companies from their sites, and tidies the values. Older backends keep the column-mapping step instead.
  1. Upload a CSV or Excel file (up to 100 MB). Optionally tell the assistant anything it should know, such as “each plant is its own account” or “skip the contact columns”. Research on these targets also uses this guidance.
  2. Watch live progress. The setup card shows the assistant’s current step, rows saved so far, and a progress bar with the estimated time left.
  3. Review the Cleaned list preview. Click Download CSV to see every value.
  4. Refine the list in chat, for example “Write site names as City, State” or “Use one row per company”. Each request builds on the previous one.
  5. Check How rows become targets. The assistant picks the Company, Website, and Site, division or region columns. Change any role that looks off, or choose None when every row is a whole company.
  6. Set Account matching, then click Review targets.
Review targets loads every target in the list and shows them 100 at a time. Your selection stays as you move between pages. When a new list finishes loading, ShiftUp selects every target if the list and your other picks fit within the 10,000-target limit. Otherwise only the first page starts selected, and ticking stops at the limit with a warning. If a page fails to load, the targets loaded so far stay, and you can load the rest. Saved lists reopen with the chat that produced them, so you can keep refining later from Settings → Sources.

Scoped sites and Account matching

When a list has a site, division, or region column, each company-and-scope pair is a separate research target. Sibling sites under the same company keep their own activity rows and strategy recommendations, even when they share a Salesforce Account. A different scope under the same company stays eligible even while a sibling is in cooldown. Account matching controls which Salesforce Account each scoped target activates into:
  • Match Accounts using analysis scope — match or create an Account for each site, subsidiary, or division. Leave it unchecked to match or create the company Account while keeping a separate strategy for each scope. Rows with a blank scope stay company-wide.
  • Match parent Account — available only with scope matching. ShiftUp matches or creates the company Account and fills the scoped Account’s Parent Account field. If the scoped Account already has a different parent, you can review and resolve that relationship.
When several Accounts tie as strong matches, ShiftUp attaches the top one as a suggested match and lets activation proceed. See Suggested account matches. Weak or conflicting Account or parent matches stay unresolved until you pick one. Research can continue, but ShiftUp blocks single and bulk activation for those targets.

Choose Salesforce accounts

The Salesforce accounts source offers three ways to choose Accounts:
  • Pick accounts — search for Accounts and select them one by one. You can pick up to 1,000 Accounts, and picks count toward the shared target limit.
  • Use list view — choose a Salesforce Account list view. Use it when your team already maintains the Accounts in a list view, such as a territory or segment view. A list view counts no targets against the shared target limit.
  • Use custom criteria — add up to five Filters. The agent uses Accounts that match every filter. Filters use the same fields and rules as bulk account import. Date filters use the saving user’s time zone.
A source uses one of these at a time. Saving custom criteria together with picked accounts or a list view is rejected. List views and custom criteria are resolved as the Salesforce integration user, not as you. ShiftUp reads them at the start of each run, so the Accounts in scope follow changes to the view or to your data. The picker shows two counts:
  • The integration user’s count, which the agent uses.
  • Your own count, which stops at 2,000 and shows as 2,000+ above that.
When the counts differ, the picker warns that you and the integration user see different accounts. Share the list view with the integration user, or check that it can read every filtered field. Use Refresh on a list view, or Recount on criteria, to update the counts. A list view or criteria source uses at most 10,000 Accounts per run. Above that, a list view keeps the first 10,000 in the view’s own order. Narrow the view or the filters to choose which Accounts the agent uses. Accounts picked alongside a saved list view stay in the selection through unrelated saves. The picker shows how many, for example 3 accounts captured on an earlier save. They are cleared when you pick the list view again or refresh it. Companies to skip can also use a List view or Custom criteria. Exclusions are resolved the same way, as the integration user, but have no 10,000-Account cap. The agent skips every matching Account.

Save rules for list views and criteria

  • Adding a new list view, or moving a list view between the source and Companies to skip, requires read access to the Account object. Unchanged list views survive unrelated edits even after you lose that access. New or edited custom criteria have the same requirement.
  • You can only save a list view you can see.
  • If another editor changed the agent after you loaded its settings, Salesforce rejects your save with “This pipeline agent changed while you were saving. Reload its settings and try again.” ShiftUp then refreshes the agent so you can reapply your change.

When a list view or criteria can’t be read

  • Source — if the integration user can’t read a source list view, or can’t run its criteria, that source contributes no Accounts. Settings → Sources says so and asks you to share the view with the integration user or adjust the filters.
  • Companies to skip — if the integration user can’t read an exclusion list view or criteria, the run ends instead of researching companies you meant to skip. The run ends once, without retrying, and names the unreadable source.
In Settings → Sources, the accounts in scope show the first accounts of a large source with the total the integration user would include. When the total is an upper bound, for example because uploaded or discovered rows without a Salesforce match could duplicate Accounts not shown, it reads as up to that number.

Agent detail

Selecting an agent opens its detail view with three tabs:
  • Overview — one overview card above the full-width Agent results list.
  • Settings — grouped into Focus, Sources, Review, and Advanced. Hidden for view-only users.
  • Sharing — who can see the agent and its draft strategies. See Sharing an agent. The tab appears only when your org’s sharing settings allow granting extra access on Pipeline Agents.
The Activity tab has been removed. Agent history now lives in Agent results on the Overview: choose All results to see every outcome, and group by Run to see each past run.

The overview card

The Overview card tells you how many recommendations are ready, when more come, where the agent looks, and what it has done so far.
  • State pill — shows where the agent stands, such as First run in progress, Finding more now, Topped up, Next top-up with a date (weekly agents), Tops up each week, Tops up when you click Run, or Paused. An agent is paused while it is turned off or none of its seller profiles is active.
  • Headline and story — how many recommendations are ready for you, and what happens next. When a run ends short, the card says why once and offers one fix, such as Add a source or Broaden the focus. Stopped and failed runs say so, and the recommendations they found stay in Agent results.
  • Now: — while a run works, this line rotates through the run’s live updates every five seconds, such as seller research, market discovery, and each company being researched. Point at the line to hold an update and read its full text.
  • Top-up settings — below the sources, the card shows the top-up size, when the agent tops up, and the minimum grade. Each has a Change link to its Settings section. View-only users see no Change links.
  • So far — companies researched, strategies you started, and deals won. Deals won appears once the agent has a win, with won amounts shown per currency. Counts that have not loaded show a dash, never zero.
  • Last run details — when the run started, how many recommendations it added and from which sources, how many waiting recommendations it refreshed, how many companies it researched, and why it stopped (for example, the queue reached your size, or every company in the sources was checked).
  • Review — the primary action when recommendations are waiting. It scrolls to Agent results with only In review selected. The ready count matches the In review rows in Agent results.
  • Run now — its tooltip explains what a run started now would do: start the first run, look for more until the queue reaches your size, or, when you’re topped up, only refresh the recommendations in review. For a weekly agent, it adds that the next weekly top-up comes a week after this run finishes. While a run works, Stop run ends it. A run requested during another run shows as queued.
Recommendations appear in Agent results as soon as ShiftUp completes them, while the rest of the run continues.

Settings

  • Focus — the plan, with the same refine box as setup. A live summary line shows while ShiftUp writes or refines the plan. Saving Focus does not automatically regenerate priorities or filters.
  • Sources — each source has independent controls and validation. A source can be collapsed without turning it off, and re-enabling it restores its unsaved draft.
  • Review — the same top-up sentence and summary card as setup, the date of the next weekly top-up, and the agent’s files.
  • Advanced — the agent name, Enabled, auto-scan, the minimum quality grade (A+ only, A or better, or B or better), additional guidance, Re-evaluate all candidates, and Archive. Archive is hidden for the default agent.

Re-evaluate the saved backlog

Use Settings → Advanced → Re-evaluate all candidates after you change an agent’s focus or priorities and want the existing backlog reassessed. The run:
  • Skips cooldowns and your top-up size, so it can take longer than a normal run.
  • Refreshes existing recommendations using the agent’s current settings.
  • Refreshes activated strategies separately, using each strategy’s own saved criteria.
  • Retries previously rejected companies.
  • Keeps dismissed candidates dismissed and discovers no new companies.
The button is disabled while another run is active. It is also disabled until the agent and a linked seller profile are active.

Agent results

Agent results on the Overview lists every company the agent researched, as one company-centered table.

Result sets

The set picker lists Recommendations and All results with their counts, followed by your saved sets.
  • Recommendations (default) — In review, Creating, and Active rows. This built-in set is read-only.
  • All results — every outcome, including rejected, dismissed, failed, and cancelled research. Choosing it clears filters, Status, search, and checked rows.
  • Saved sets — private sets you create with Save as. Applying a saved set replaces the filters while keeping your search, sort, and grouping. When you edit a saved set’s filters, Update saves the edits and Reapply restores the saved filters. You can rename and delete your saved sets, up to 50 per user.
Current filters appears in the picker when you filter without a saved set.

Group and sort

Group by Status, Company, Run, Account owner, Industry, or None. Run groups show each run’s date. Sort by Quality grade, Potential, Estimated deal value, Time to close, Latest, or Company A–Z. The default order ranks grade descending, then numeric quality descending, then recency, with ungraded rows last.

Status

Each row shows one status:
  • In review — awaiting your decision.
  • Creating — a sales strategy is being created in Salesforce; Cancel creation stops creation.
  • Active — a seller created the sales strategy in Salesforce.
  • Dismissed — a seller dismissed the recommendation; it stays in Agent results but is not re-surfaced.
  • Evaluating, Rejected, Cancelled, Failed, Too soon, Overridden — the various research outcomes.
The Status facet is the first filter and covers every outcome.

Filters

The filter panel exposes the same facets the agent used during evaluation, such as industry, employee band, timing, signals, opportunity value band, and account owner. A No owner choice selects results without an Account owner. One search box finds both filter names and option labels. Filter menus hide choices without matches, and each choice shows its matching-row count. Applied filters show as removable chips, with Clear all. On narrow screens, filters open in a drawer. Filter selections persist per agent and restore when you return. You can also build filters in chat. Describe the results you want in your own words, and ShiftUp applies the matching filters to Agent results. The first time you open Agent results, a Tour the new experience link marked New walks you through the filters, the set picker, Status, run grouping, chat edits, and action scope.

Act on a set or on checked rows

With no rows checked, Activate and Export apply to the whole set, including rows on pages the table has not loaded. Whole-set Activate counts only rows that are in review and not already being created. It stays available only while the Status filter includes In review. When your admin turns on Enable Account Creation Flow, Activate applies only to checked rows that are linked to existing Accounts. With no rows checked, the action bar reads Select strategies to activate. See Account creation options. Check rows to make them the action scope. The action bar shows how many rows are selected, Clear selection, and each action with the number of checked rows it applies to:
  • Activate
  • Cancel creation
  • Undo dismissal — returns a dismissed recommendation to In review without new research.
  • Override rejected — reopens a rejected candidate for another evaluation.
  • Dismiss
  • Delete — removes the row from Agent results. Any active Salesforce strategy stays.
Every bulk action confirms its scope, shows progress, and supports Stop. Search, filters, and sorting remove hidden rows from the selection. Each row also has a menu with the actions available for its status.

Export results

Exports follow the current set: its search, filters, and Status, or only the checked rows. The Status filter decides which outcomes an export includes. To export rejected results, include Rejected in the Status filter.
  • CSV — every row in the set, with or without a strategy. CSV has no row limit. For every saved stakeholder, use a PDF export. See CSV columns.
  • Executive Summary — a PDF summary of the set. Rows without a strategy show their outcome and decision reason.
  • Full Data — one PDF with the summary followed by each row’s research brief.

CSV columns

Besides company details, grade, outcome, hypothesis, filters, and scores, each CSV row includes these columns: Missing values stay blank. Exporting never triggers contact or company research. Newly evaluated candidates capture headquarters state and city. Earlier candidates are not backfilled, so their headquarters cells stay blank.

Quality grades

Candidate quality renders as one of four letter grades on the same numeric thresholds ShiftUp already uses: Missing scores render as Ungraded rather than a numeric zero. Filter and API grade bands remain A/B/C/D so saved selections and integrations keep their existing values; the seller-facing labels are derived from the same thresholds.

Grades on activated strategies

Once you activate a candidate, the new strategy owns its grade. The pipeline’s Active row and the strategy page show the same saved assessment. When ShiftUp reassesses a strategy, the current grade stays in place until a replacement is published. The Quality grade filter on the Strategies list shows only strategies that match the selected grades. Click any grade to open its breakdown popover. It shows Why this grade, All dimensions, Mission priorities, and What changed since the previous assessment. When Enable Pipeline Agents is disabled, strategy lists, detail pages, and PDFs fall back to the released numeric Confidence percentage and the legacy strategy strength display instead of the quality grade.

The decision brief

Selecting a candidate opens its decision brief — one shared surface used by Agent results and the original-candidate dialog.
  • Overview pairs a company introduction and facts with the complete suggested approach (or why not now for rejected candidates), the timing estimate, and the recommended people.
  • A persistent contents menu on desktop, or a grouped picker on narrow screens, opens Overview, Estimate & timing, Signals, Research & quality, and each saved person directly. Navigation moves keyboard focus to the selected heading and keeps visited evidence disclosures.
  • Each person card opens the same saved profile as the contents menu, with saved research, sources, and a collapsed suggested message.
  • Signals, company research, and estimate assumptions are directly readable. Quality factors and close stages expand individually; validation questions share one disclosure.
  • Estimated deal value shows the saved Base scenario; Low / Base / High assumptions and evidence remain available. Any linked CRM opportunity amount stays a separate fact. A saved zero stays a zero; a missing scenario shows Estimate unknown.
  • Rejected candidates lead with why not now and retain any saved estimate and people research. The saved admission explanation for that run, including its required grade, is shown.
  • Export PDF produces a full decision brief that follows the same order and retains every saved question, stakeholder, assumption, source, and reasoning step. Rejected exports lead with why not now. Grade versus strength display in the PDF follows the same Pipeline Agents flag as the on-screen brief.

Candidate actions

  • Activate — creates a full opportunity strategy from the candidate. The activation dialog picks who owns each new strategy (see Assignment on activation).
  • Bulk actions — check rows, or act on the whole set, from the Agent results action bar. See Act on a set or on checked rows.
  • Cancel creation — returns an in-flight creation to review.
  • Dismiss — marks the candidate as dismissed; it stays in Agent results but is not re-surfaced. Undo dismissal returns it to review.
  • Override rejected — reopens a rejected candidate for another evaluation.
Pending rows show the Salesforce destination — New account, Matched account, Monitored account, or Restricted account — with an inline change control so you can pick a different account before activation. Scoped rows also show their analysis scope.

Suggested account matches

Sometimes a candidate’s company ties between two or more strong Salesforce Account matches. ShiftUp no longer blocks activation in this case. Instead, ShiftUp attaches the top suggestion and the row shows a Suggested chip. The chip’s hint reads “The sales strategy will be automatically linked to the existing account … unless you select or create a different account.” To review the match, click Change on the row. The Salesforce account dialog opens on Use existing account with the suggested Account preselected and lists the alternatives. You can:
  • Keep the suggestion. Activation links the strategy to the suggested Account.
  • Select a different existing Account, then click Save account choice.
  • Switch to Create new account to create a new Account instead.
When the batch you activate includes suggested matches, the Activate confirmation shows a warning callout. For example: “3 strategies have unconfirmed account matches. They will be automatically linked to their suggested accounts.” If some selected rows aren’t loaded yet, the callout adds “Counted from loaded strategies only; the full set may include more.” The callout is informational and never blocks activation. Weak or conflicting matches still block activation until you choose an Account. When scoped activation sets parent accounts, the activation dialog names the parent account it sets and notes when ShiftUp will create it in Salesforce. Sibling sites and earlier activations share one parent, so ShiftUp creates each parent only once. If a target has no Account Plan yet, the creating row shows Account Plan research and save progress before strategy generation starts. After a reload, the row waits for the next progress update instead of guessing a step. On an Account Plan, you can open the immediate parent plan and a menu of immediate child plans. Both directions list only plans you can access that belong to the same Seller Profile.

Account creation options

The ShiftUp form saves Account details as a draft and creates the Account when the strategy activates. Your admin can enable its customizable version to add fields. ShiftUp Pipeline Account Before Create can supply defaults when the current activation process creates each new target or parent Account. If your admin turns on Enable Account Creation Flow, Create new account opens a Salesforce screen flow. Complete the required fields and select Create Account. The Account is saved immediately and linked to the strategy; activation is a separate next step. A strategy cannot activate while it still needs a new target or parent Account. Create or choose those Accounts first, then check the rows you want to activate. Whole-result-set activation is unavailable while this setting is on. Accounts created by the screen flow already exist at activation, so Before Create does not run for them. See How Account creation works in Pipeline agents for the comparison and links to configure either option.

Assignment on activation

The activation dialog picks who owns each new strategy:
  • Automatic (default) — each strategy is assigned to its account’s Salesforce owner. ShiftUp re-reads Account.OwnerId at activation time, so stale seed data on a candidate row cannot misroute a strategy or overwrite a new owner. A preview breaks the batch into owned accounts, ownerless accounts, and accounts not yet in Salesforce.
  • Fallback for accounts without an owner — pick a single user (or leave unassigned) to catch accounts that have no resolvable owner. This applies only to those rows. When the batch includes accounts not yet in Salesforce, the picker’s label calls them out so you know the fallback pick also decides who owns those new accounts.
  • Everything to one user — switch to a typeahead to search users by name and assign the entire batch to one person.
  • Suggested assignees — the last successful assignment for the current filter set is remembered per agent and offered back the next time you activate a similar batch, with provenance.
  • Also make this user the account owner — an opt-in checkbox on both pickers. When checked, ShiftUp updates the Salesforce Account owner and the ShiftUp Account Plan owner to the chosen user after the strategy is created. The transfer is scoped to the accounts the chosen user was assigned in this activation. This option is hidden or disabled unless the transfer feature is turned on for the org and you have Modify All Data — see Permissions.

Owners for accounts created during activation

With Enable Account Creation Flow off, when a candidate’s Salesforce destination is New account, ShiftUp creates the Account and its ShiftUp Account Plan as part of activation. The owner of those new records is set at creation time from the same assignment choice you made in the dialog:
  • Everything to one user — the new Account and its Account Plan are created with the chosen user as owner.
  • Automatic with a fallback user picked — the fallback user owns each new Account and its Account Plan. Automatic assignment then reads that live owner and routes the strategy to the same user.
  • Automatic with no fallback picked (or Leave all unassigned) — new Accounts and their Account Plans are created for the seller profile owner, and the strategy follows that owner.
Existing Accounts and their existing owners are never changed by this step; only accounts created during activation are affected. Use the Also make this user the account owner opt-in when you need to transfer an existing Account too. The dialog surfaces how many candidates in the batch are new to Salesforce alongside the owned and ownerless counts, so you can see at a glance how many accounts the assignment will create. The user chosen as the new-account owner (specific user, or the automatic-mode fallback) must hold a Salesforce license — the shared assignee picker filters to active Standard users, and the server re-checks the user before any Account is written. A user who is not an active Standard user is rejected with invalid_new_account_owner and no records are created.

Provenance on activated strategies

Every strategy an agent creates carries the source agent in a Sourced by badge on the strategy detail page. The strategies list also includes a sortable Pipeline Agent column, letting you slice pipeline by source and jump from a strategy back to the agent that generated it.

Approvals in the Workspace

The Strategy approvals widget in the Workspace is the manager’s shared queue for pipeline agent candidates. When more than one agent exists, pick an agent from the widget picker; the widget then scrolls through every pending candidate for that agent, sorted server-side, with the same activate / dismiss / bulk actions available on the agent detail page. Managers and admins land on a pending-led workspace layout by default that surfaces this widget first. The widget follows the Workspace global filter you select. Account owner criteria (Me, team users, or None) match the candidate’s captured Salesforce Account owner, which can differ from the Account plan owner. None also includes candidates with missing owner data. Industry criteria match the candidate’s industry. Criteria without a candidate equivalent, such as Favorites, don’t narrow the queue. See Strategy approvals and global filters.

Older agents

Pipeline agents load and render even when older agents are missing non-critical fields:
  • An agent whose saved configuration does not carry a target mix loads with Any customer focus.
  • A missing agent description stays blank rather than blocking the list or detail view.
  • Saving unrelated settings does not overwrite the absent values.
One agent’s missing optional data never prevents the rest of the list from rendering.

Sharing an agent

The Sharing tab on the agent detail view controls who can see the pipeline agent and its draft strategies. Pipeline agents follow standard Salesforce record sharing: the tab appears only when the Pipeline Agent object’s organization-wide default leaves room to grant additional access. When the org-wide default already gives everyone full access, the tab is hidden.

Who can manage sharing

You can add and remove shares when you are the agent’s owner, sit above the owner in the role hierarchy, or hold Modify All on Pipeline Agents or the Salesforce Modify All Data permission. Everyone else sees the Sharing tab in view-only mode: the current share list is visible, and a notice explains to contact the owner or an administrator for changes.

Add users or groups

Search for users or public groups (switch between the two with the tabs above the search box), pick an access level, and add them. The access levels offered — Read Only and Read/Write — depend on how much room the org-wide default leaves to grant. Each share appears in the list with its access level. Remove a share to revoke that access. Sharing an agent also grants the recipient Read access to the agent’s linked Seller Profile, so the shared agent renders with its profile context. That synced access appears on the Seller Profile’s sharing list with a Via agent badge and is cleaned up when you unshare the agent, unless another shared agent still requires it. Shares can also arrive in the other direction: when someone shares the agent’s Seller Profile and opts to include the related pipeline agent, the resulting agent share carries a Via profile badge. Remove that access by unsharing the Seller Profile.

Copy Seller Profile access

On a seller profile’s default agent, users who can manage sharing see a Copy Seller Profile access button in the Sharing tab header (shown only when Seller Profile sharing is also available in your org). It copies everyone explicitly shared on the linked Seller Profile — users and groups — onto the pipeline agent, so they can see the agent and its draft strategies. If a recipient holds both levels through different shares, Read/Write wins. A confirmation dialog summarizes the effect before anything is copied. The copy is one-time: after it completes, agent access is managed independently, so later Seller Profile sharing changes are not synced. Run the copy again to pick them up. If the Seller Profile has no explicit shares to copy, ShiftUp reports that nothing was available to copy.

Permissions

Pipeline agent access is opt-in via two permission sets:
  • ShiftUp Pipeline Agent Viewer — read pipeline agents and their candidates.
  • ShiftUp Pipeline Agent Manager — create, edit, run, activate candidates, and archive agents.
Assign these from the user setup Permissions Management modal. They stack with your personas — Seller, Manager, Admin — and are removed cleanly when you use Remove Permissions.

Account ownership transfer on activation

The “Also make this user the account owner” opt-in on the activation dialog is gated by two things, both checked server-side at activation:
  • Enable_Account_Owner_Transfer app setting — an admin-only ShiftUp setting, off by default. Turn it on from ShiftUp Setup → Allow account ownership changes from activation. When the setting is off, the checkbox is hidden or disabled and the dialog explains that an admin needs to enable it.
  • Modify All Data — the acting user must hold the Salesforce Modify All Data system permission. Users without it see the option locked out even when the org setting is on.
Enabling the setting also syncs the packaged ShiftUp Account Transfer permission set, which carries the Salesforce object permissions needed to update Account.OwnerId and the ShiftUp Account Plan owner.