App Settings

This guide covers configuration options available within the Fours App settings and Salesforce setup.


API Connectivity

To connect the Fours Salesforce App with the Fours platform, you need to configure API credentials and integration settings. This includes setting up authentication, mapping rules, and sync preferences.

For detailed instructions on configuring API connectivity, see the Salesforce Integration Setup Guide.

Checking the connection. Clicking Save on the Settings card verifies the connection with an authenticated call to Fours. When the call succeeds you see Connection saved and verified — Successfully connected with Fours, including in an org that authenticates with OAuth credentials only and has no API key. When it fails, a toast that stays until you close it reads Unable to connect with Fours — Please double check the Fours Organization ID and OAuth credentials (or API Key)., followed by Reason: and the error Fours received when there is one — for example OAuth token exchange failed [401]: … when Salesforce could not exchange the OAuth credentials for a token.

OAuth credentials are required for AI notes

Generate AI Notes in the Azure co-sell share wizard calls Fours’ AI service, which accepts Bearer tokens only. An org still authenticating with an API key alone gets a 401 back and the button fails with:

AI note generation requires OAuth. Add the Fours OAuth Client ID and Client Secret in Fours Settings, then try again.

Add the Fours OAuth Client ID and Client Secret in Fours Settings to enable it. Everything else in the app continues to work on the API key.


Managing Tab Visibility

The Fours App includes both V1 and V2 tabs. The key differences are:

  • V1 tabs use Salesforce Lightning Record Tables that read from local Salesforce objects. Data may be delayed due to sync intervals between Fours and Salesforce.
  • V2 tabs read data directly from the Fours platform via API, providing real-time, up-to-date information.

To streamline the user experience and reduce clutter, Admins can hide unused or legacy tabs using one of the following methods.

Method 1: Hide Tabs via App Manager

This method removes tabs from the default navigation bar for all users accessing the Fours App.

How to Configure:

  1. Click the Gear Icon (⚙️) > Setup.

  2. In the Quick Find box, type App Manager.

  3. Locate the Fours in the list. Click the dropdown arrow (🔽) on the right and select Edit.

  4. Select Navigation Items from the left-hand menu.

  5. Select the tabs you wish to hide from the Selected Items list (right side) and use the Remove Arrow (⬅) to move them to the Available Items list (left side).

  6. Click Save.

Method 2: Disable V2 Access via Fours Settings

Unlike Method 1, which removes the tab from the navigation bar, this method does not hide the tab. Instead, it functionally disables the page content.

If a user clicks on a disabled tab, the page will load, but they will see a “Feature Disabled” message and cannot interact with any data.

How to Configure:

  1. Open the Salesforce Fours App and navigate to the Fours tab.

  2. In settings menu, scroll down to the Tabs Control section.

  3. Locate the toggle for the page you wish to restrict: Disable Products V2, Disable Offers V2, Disable Entitlements V2, Disable Companies V2, Disable Referrals V2, or Disable Partner Applications (the Partner Applications (Fours) tab, which then reads Partner Applications is Disabled).

  4. Turn ON the toggle to disable the feature.


Adding the Referrals Tab

To streamline your referral workflows and ensure quick access to key information, we recommend adding the Referrals tab to your Salesforce navigation bar. This lets you easily track both inbound referrals from AWS and outbound referrals submitted by your team.

How to Configure:

  1. On the top-right corner of your Salesforce screen, click the pencil icon (Customize My Navigation) to open the Navigation Editor.

Open the Navigation Editor from the pencil icon

  1. In the editor, click Add More Items, then go to the All section to see a list of available navigation items.

Add more navigation items from the All section

  1. In the search bar, type Fours. Find and select Referrals V2 (Fours), then click Add 1 Navigation Item. We suggest placing the Referrals tab directly below Opportunities, since they are commonly used together — use drag-and-drop to reposition it.

Search for and add the Referrals V2 (Suger) navigation item

  1. Click Save to apply your new navigation layout.

Accessing and Using Referrals

After saving, you’ll see the Referrals tab in your navigation bar. Click the tab to view and manage referrals, and use the Recently Viewed dropdown to switch between:

  • All Referrals
  • Inbound Referrals – Opportunities shared with you from AWS
  • Outbound Referrals – Opportunities your team has shared with AWS

Switch between All, Inbound, and Outbound referrals using the Recently Viewed dropdown

Referrals saved as a Draft and not yet submitted are listed in these views alongside submitted ones, so you can find and finish them from the same table. A draft does not exist on the cloud partner’s side yet, so its Partner Status and Stage columns show - until it is submitted.

Drafts appear in Salesforce only — the co-sell list in the Fours console omits them.


How Funding records open

Opening a Funding record from anywhere in Salesforce — a list view, a related list, global search, or a report — redirects to the Fours Funding Detail page rather than the standard Salesforce record layout, so you always land on the live Fours view of the funding application. The redirect uses the record’s Fours funding application ID, the same value the funding cards and tables link with.

If the redirect cannot resolve (for example the record is not readable under your permission set), Salesforce falls back to the standard record view. The package ships a page layout for it, Funding (Fours) Layout, which places every Funding field in sections — Information, AWS Status, Approval, Credits, Allocation and Issuance, Cash Request, Project, Customer and Opportunity, Public Sector, Partner Contact and System Information — with the request’s Funding Cash Claims and Funding Credit Codes as related lists. Every field the Fours sync writes is read-only there, because the next sync would overwrite an edit; only Owner is editable.

When AWS created and last updated the request. The Funding Detail page’s Funding Request Information section ends with AWS Created Date and AWS Last Modified Date: the date and time the request was created and last updated in AWS Partner Central, shown in your local time, or - until AWS has reported them. The Funding record’s own Created Date only says when Fours first synced it. The same two timestamps sync to the record under the same names for reporting — see Funding__c.

Find a Funding record. Funding records are returned by Salesforce global search, and each result shows the Funding Application ID, Partner, Program, Project Name, Partner Status, Approval Status, Opportunity, Project Start Date, and Project End Date. The Fours app also has a tab for the Funding object itself, placed just before Funding V2 (Fours) in the app’s navigation; its All list view shows Funding Name plus those nine columns. Funding V2 (Fours) (formerly Funding (Suger)) is the funding table that reads straight from Fours, and its Project Name links open the Funding Detail page. The Fours Funding and Fours Funding (Read Only) permission sets make both tabs visible.

AWS status, allocation and the request’s own fields. The request’s status with AWS is the Partner Status on the page’s status card, the same field reports call Partner Status. After Funding Request Information, the page shows these sections, each only when the request carries them:

SectionWhen it showsWhat it holds
AWS StatusAlwaysAWS Status Reason and AWS Status Reason Codes — why AWS gave the request its status, or - when AWS gave no reason
Benefit AllocationA request fulfilled in credits or cashAWS Allocation Status, AWS Allocation Status Reason, AWS Allocation Start Date, Expires At and AWS Allocated Amount, plus AWS Issued Amount for credits and AWS Utilized Amount and AWS Remaining Amount for cash. The rows read - until AWS allocates
Credit Request DetailsA request fulfilled in creditsThe credit request’s fields for that program, such as Credit Currency, Credit Requested Amount, Credit Approved Amount, Credit Value Per Code and Credit Number Of Codes
Additional DetailsThe program has fields of its ownThe rest of that program’s request fields that no other section shows

The page works out the program from the request’s AWS benefit, so ISV Workload Migration, MPOPP and SCA GenAI requests get their own fields too. The APN and Marketplace MDF Wallet panel shows its amounts in the allocation’s own currency.

On a cash-based MDF or POC request, the Funding Detail page has a Cash Claim section with one tab per planned claim (Activity 1, Activity 2, … on MDF; Cash Claim 1, … on POC). Each tab shows the claim filed for it — its Fund Claim ID, Cash Claim Status, and Claim Due Date — and on an MDF request an Invoice & Payment block with Invoice Currency, Invoice Amount (Local Currency), and Scheduled Paid Date. AWS records each cash claim as its own application linked to the request, and the page reads those claims when it opens, so the values match the Fours Console. A tab whose claim has not been filed yet, or cannot be matched to it, shows a dash in those fields. The same claim dates also sync to the FundingCashClaim__c record once AWS records them.

On a cash request — MDF, POC, a PIF: SCA GenAI program, or a program the page has no layout for — the Cash Request Information section shows the request’s PO Number and its Payee Central Account Profile ID — the purchase order AWS issued and the Payee Central profile the cash is paid to. Both also sync to the Funding record (Funding__c).

Funding stage. Once AWS reports a stage for the request, the Funding Detail page shows a progress bar with the six stages AWS Partner Central shows for a fund request, in this order. The progress bar shows only the stage names; the diagram adds, under each, the stage value AWS records that maps to it:

The Funding Stage on the funding cards in Fours Account Insights and the Fours Opportunity Quick Panel, and the Stage column of the Funding V2 (Fours) table, use the same names for the five mapped stages, Business approval through Application completion. They show - when AWS has reported no stage, and show any other value exactly as AWS sent it. The table’s Fund Request Stage filter splits cash claims into Cash claim (invoice) and Cash claim (disbursement).


Review partner applications

If you run a partner program in Fours PRM, you can approve or decline the applications to join it from Salesforce. The Partner Applications (Fours) tab, the last tab in the Fours app, lists your organization’s applications as Fours holds them now: it reads Fours each time you open it, search, filter, change page or click Refresh, so a decision made in the Fours Console shows at once.

The Partner Applications table opens on every application, newest first, 50 to a page:

ColumnWhat it shows
ApplicationThe applicant’s company (else their name or email); click it to open the application
Applicant / Email / CompanyWho applied, as entered on the form
StatusPending, Approved, Declined or Cancelled
SourcePartner Form (your partner registration form) or Deal Registration (a public deal registration)
Submitted / Decision DateWhen the application arrived and when it was decided

Search with Search by company, applicant, email or website, and use the Status filter to show one status. With Pending selected and nothing waiting, the table reads No applications are waiting for a decision. An application that arrived as a paired invitation from another Fours organization is not listed here, though the Fours Console’s Applications tab lists it.

Open an application from the tab, or from any Partner Application (Fours) record, whose record page opens the same view (see Partner_Application__c). It reads the application from Fours and shows the company name with a status badge and the applicant’s email domain, then:

  • Applicant: Name, Email, Company and Email Domain.
  • Application: Submitted, Form, Decision Date and Source.
  • Submission: Company Website, Why Partner With Us, and every other question on the form with its answer (Not answered where the applicant left it blank).
  • Decline Details: the Decline Reason, on a declined application.

The panel on the right explains the status: a pending application reads Waiting for your decision. Approving creates the partnership in Fours; declining emails the applicant.

Approve or decline. On a pending application, Approve and Decline appear in that panel for users with the Fours PRM permission set, which carries the Approve or Decline Partner Applications custom permission (see PRM Permissions). The decision is made in Fours, the same as from the Fours Console:

  1. Open the pending application.
  2. Click Approve to create the partnership in Fours, or Decline to turn the applicant down.
  3. For Decline, the Decline application dialog asks for an optional Reason of up to 4,000 characters — The applicant reads the reason in the decline email. — then click Decline.
  4. A toast confirms Application approved or Application declined — Fours made the decision. — and the status updates.

Who sees the tab. The Fours User, Fours User - Read Only, Fours User - Cosell, Fours Cosell (Read Only), Fours PRM and Fours PRM (Read Only) permission sets, and both Fours Integrator sets, make the tab visible; only Fours PRM can approve or decline. The tab and the page show every application to anyone who can read Partner Applications: record sharing and field-level security on the Partner Application (Fours) object narrow its list views and reports, not the tab. The tab instead reads PRM isn’t enabled when Fours PRM is not on for your Fours organization, and Partner Applications is Disabled when an admin has turned on Disable Partner Applications under Tabs Control (Method 2).


Widget Pin Control

In the Opportunity quick panel, each user can pin up to two sections (Offers, Entitlements, Co-Sell, Associated Contacts, Funding) to a Pinned tab for quick access. By default this is controlled individually per user.

Admins can instead enforce a company-wide set of pinned sections. When enabled, the chosen sections are pinned for every user, and individual users can no longer pin or unpin their own sections. Disabling it again restores each user’s previous personal pins.

How to Configure:

  1. Open the Salesforce Fours App and navigate to the Fours tab.

  2. In the settings menu, scroll down to the Widget Pin Control section.

  3. Turn ON Enable Widget Pin Lock.

  4. Select up to two sections to pin company-wide.

  5. Click Save.

Spotted something wrong or out of date on this page? Tell us and we'll correct it.