Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.shiftupai.com/llms.txt

Use this file to discover all available pages before exploring further.

The Context Console is an admin tool inside ShiftUp Admin that lets you run a context provider against a specific account plan and inspect the raw data it returns. Use it to verify that your context provider configuration, integration user permissions, and Salesforce field-level security are producing the data you expect — before that data flows into account plans and sales strategies.

​
When to use it

  • Validate that a newly enabled context provider is returning the expected fields for a seller profile.
  • Diagnose missing or unexpected context in a generated account plan or strategy.
  • Confirm that the integration user’s permissions grant access to the records and fields you intend to expose.
  • Compare output across multiple providers for the same account by running them individually or all at once.

​
Access requirements

The Context Console is only visible to users who meet all three of the following:
  • CRM Context for Seller Profiles is enabled in ShiftUp Admin > Advanced > App Settings. See Context Providers for setup steps.
  • The user has the ShiftUp admin permission set.
  • The user has the Salesforce View All Data permission.
If any of these are not met, the Context Console tab is hidden and the in-app message reads: “Context Console is unavailable because context providers are disabled, you do not have the ShiftUp admin permission, or you do not have the View All Data permission.”

​
Opening the console

1

Open ShiftUp Admin

Navigate to ShiftUp Admin in your Salesforce app launcher.
2

Open the Context Console tab

Select the Context Console tab in the application setup view. The tab only appears when the access requirements above are met.

​
Running a provider

The console has two panels: a parameter form on the left and a results panel on the right.
1

Select a Seller Profile

Pick the seller profile whose context provider configuration you want to test. This scopes the account-plan search and determines which providers are available.
2

Select a Context Provider

Choose a single provider to inspect its output in isolation, or select All to run every enabled CRM context provider for the chosen seller profile in one pass.
3

Find an Account Plan

Type at least two characters into Search Account Plans and click the search icon. Pick the account plan you want to run the provider against from the dropdown.
4

Run

Click Run. The results panel displays the JSON returned by the provider, along with any errors.

​
Reading the results

The results panel renders the provider’s response as structured JSON. Use it to confirm:
  • Records returned — Does the provider find the accounts, opportunities, contacts, or other records you expect?
  • Fields populated — Are all the fields you configured present and populated? Missing fields usually indicate a field-level security restriction on the integration user, or a field that’s been filtered out by context provider field constraints (see Context Providers).
  • Errors — If the provider fails, the panel shows the underlying error message. Common causes are insufficient integration user permissions, disabled provider configurations, or invalid seller profile data.

​
Troubleshooting

SymptomLikely cause
Context Console tab is hiddenContext Providers are disabled, or you lack the ShiftUp admin permission or View All Data.
No seller profiles in dropdownNo active seller profiles exist in the org, or none are visible to your user.
No context providers availableCRM context is enabled but no providers are configured for the selected seller profile.
No account plans foundThe seller profile has no account plans matching the search term, or you need to refine your search.
Provider Execution FailedThe integration user is missing read permission on a required object or field. Review the error detail and update the integration user’s permission set.
Empty fields in the responseThe integration user has access to the record but not the field. Update field-level security on the integration user’s permission set.