Installing the Deal Forge App Suite
This guide walks a Salesforce administrator through installing the Deal Forge App Suite, bootstrapping the first admin user, and verifying that the apps are ready to use.
Overview
Deal Forge is a suite of two native Salesforce apps that ship in one package and are licensed the same way:
- Deal Packages - lets revenue operations build reusable, pre-approved “deal packages” once, each made up of one or more products (including bundle products) with pre-configured quantities, discounts, and dynamic attributes, and apply them to a Quote in a single click. Reps get consistent, pre-configured pricing without manually rebuilding the same package every time; admins control what’s available, to whom, and on which price books.
- PCM Hub - a guided browsing and light-admin workspace over your org’s own Product Catalog Management data (products, price books, selling models, attributes, and the relationships between them), surfaced in one consistent, searchable interface instead of Salesforce’s default per-object record pages.
Deal Forge is currently undergoing Salesforce AppExchange Security Review. We expect this to clear soon. The app is fully functional today and installable directly via the package links in Section 3 - review status does not affect functionality.
Deal Forge runs entirely on Apex, Lightning Web Components, and Salesforce’s own Revenue Cloud objects inside your org. There is no external server, no middleware, and no integration user involved in normal use. Data never enters or leaves your Salesforce org, at install time or afterward.
Installing the package does three things automatically, with no configuration required:
- Installs the Deal Packages and PCM Hub apps, objects, and components
- Generates a unique encryption key for your org and provisions a starter FREE license for each app - 2 User seats + 1 Admin seat, valid for 6 months from install date (see Section 8 for renewal)
- Nothing calls out to an external service during install or normal use - Deal Forge’s configuration flow runs natively inside your org
The only manual step is granting the very first admin user access (Section 5) - after that, all further users are provisioned entirely inside the app.
Prerequisites
- A Salesforce org with System Administrator access for the person performing the install
- Lightning Experience enabled (Deal Forge does not support Classic)
- Salesforce Revenue Cloud enabled in the org. Deal Forge is built on top of Salesforce’s native Revenue Cloud objects (Product2, Pricebook2, PricebookEntry, Quote, and related catalog/configuration objects) - it does not include or provision Revenue Cloud itself
Every user of Deal Packages or PCM Hub - not only the installing admin - must also have certain standard Salesforce permission sets assigned, in addition to the Deal Forge permission set groups described later in this guide. These come from your org’s Revenue Cloud license, not from Deal Forge, and Deal Forge’s own permission sets cannot grant them.
Required for all users (both apps):
- Product Catalog Management Viewer
- Salesforce Pricing Run Time User
Required for Deal Packages users (to apply a package to a Quote - this uses Salesforce’s own native “Place Sales Transaction” service):
- PlaceOrder API
- Create Orders from Quotes
- ProductAndPriceConfiguration API
- Price and Tax Calculation for Quoting
- CalculatePrices API
Without these, non-admin users hit errors such as “You don’t have access to the place sales transaction service” when applying a deal package, or an access error opening PCM Hub. See Section 9 (Troubleshooting).
Installing the Package
Deal Forge is currently a Beta release. It is fully functional and supported - Beta package versions simply can’t be upgraded in place later (an existing install must be uninstalled before installing a newer Beta; we’ll communicate ahead of any such transition).
| Environment | Install link |
|---|---|
| Production | https://login.salesforce.com/packaging/installPackage.apexp?p0=04tUK000000QO9xYAG |
| Sandbox | https://test.salesforce.com/packaging/installPackage.apexp?p0=04tUK000000QO9xYAG |
- Open the install link above for your target environment
- Log in to the target org when prompted
- On the install screen, choose an install option:
- Install for Admins Only - only System Administrators get initial access; recommended if you want to control rollout through the in-app license tools (Section 7)
- Install for All Users / Install for Specific Profiles - choose whichever fits your rollout process
- Deal Forge’s own object/field/Apex access is granted per-user through its license tools regardless of which option you pick here (Section 7) - this screen only controls initial package visibility
- Click Install
- Wait for the confirmation email or the on-screen “Installation Complete” message
What Happens Automatically on First Install
Immediately after a fresh install completes (this step is skipped on upgrades), Deal Forge silently provisions a starter license:
| Deal Packages | PCM Hub | |
|---|---|---|
| User seats | 2 | 2 |
| Admin seats | 1 | 1 |
| License type | FREE | FREE |
| Expires | 6 months from install | 6 months from install |
You do not need to do anything for this to happen. If you open the app and see a License Invalid screen instead of the app itself, the automatic step failed to complete (rare) - see Section 9, Troubleshooting.
Bootstrapping the First Admin User
The app’s own user-management screen is only reachable by an admin - so the very first admin can’t grant themselves access through it. This one-time step must be done manually in Setup.
- In Setup, go to Users → Permission Set Groups (or search “Permission Set Groups” in the Quick Find box)
- Assign the following two permission set groups to the user who will administer Deal Forge (typically yourself, the installing admin):
- Dealforge_Package_Admin_Group
- Dealforge_PCMHub_Admin_Group
- Also assign the standard Revenue Cloud permission sets from Section 2 - both the “required for all users” and “required for Deal Packages users” lists - if this admin user doesn’t already have them. Deal Forge’s own permission set groups do not include these.
Deal Forge’s own technical access (Apex class access, field-level security on its custom objects) is granted automatically whenever a user is assigned a seat through the app itself - see Section 7. The standard Revenue Cloud permission sets above are the one thing that is not automatic and must be assigned by hand in Setup for every user, admin or not.
Verifying the Install
- Open the App Launcher and search for Deal Forge
- Open the Deal Packages app
- In the app header, click the license status indicator to open the License panel
- Confirm it shows:
- Status: Valid
- License type: FREE
- Seats: 2 Users / 1 Admin
- Expiration: 6 months from today
- Repeat for the PCM Hub app
Provisioning Additional Users
Once the first admin is bootstrapped (Section 5), every other user - admin or standard - is added entirely inside each app.
Each app has its own License panel and its own seat pool (2 Users + 1 Admin on the starter FREE license, per app - see Section 4). Assigning someone a seat in Deal Packages does not give them access to PCM Hub, and vice versa - if a user needs both apps, repeat the steps below in each app.
Provisioning users for Deal Packages
- Open the Deal Packages app and click the License shield icon in the header
- Select a user and assign them a User or Admin seat
- Deal Forge’s own permission set groups (Dealforge_Package_User_Group / Dealforge_Package_Admin_Group - technical access to Deal Packages’ custom objects, fields, and Apex classes) are assigned automatically - nothing further to do in Setup for those
- Separately, in Setup, assign the user the standard Revenue Cloud permission sets from Section 2 if they don’t already have them. This step is manual for every user and is not handled by the License panel.
Provisioning users for PCM Hub
- Open the PCM Hub app and click the License shield icon in the header
- Select a user and assign them a User or Admin seat
- Deal Forge’s own permission set groups (Dealforge_PCMHub_User_Group / Dealforge_PCMHub_Admin_Group - technical access to PCM Hub’s custom objects, fields, and Apex classes) are assigned automatically - nothing further to do in Setup for those
- Separately, in Setup, assign the user the same standard Revenue Cloud permission sets from Section 2 if they don’t already have them (the prerequisite is shared across both apps, even though the seat itself isn’t)
Seat counts are capped by each app’s own license (2 Users + 1 Admin on the starter FREE license). See the Admin Guide for the full walkthrough of user management, seat limits, and requesting more seats.
FREE Licenses & Renewal
Every fresh install provisions a FREE starter license per app, automatically (Section 4): 2 User seats + 1 Admin seat, valid for 6 months from the install date. No signup or approval is needed to get this - it’s provisioned the moment the package finishes installing.
Renewing within the last month of your license period
Starting 30 days before expiration (and any time after it has expired), the Extend License button in the License panel becomes active:
- FREE license - click Extend License and it self-extends 6 months further from the current expiration date, immediately, with no approval needed. This is self-service by design - no need to contact anyone for a FREE renewal.
- Commercial license - the same button opens a pre-addressed email to info@clerisoft.com to arrange renewal. Clerisoft issues a new license key, which you install from the same License panel (Enter License Key).
- Users and Admin seats for an app renew together in a single click - you don’t extend them separately.
- The button is only enabled inside that 30-day window (or after expiration) - it can’t be used to stack extensions early.
- If you need more seats than the starter FREE license provides, or want a commercial license before your FREE license expires, contact info@clerisoft.com any time - you don’t need to wait for the renewal window.
Troubleshooting
The user is missing one or more of the standard Revenue Cloud permission sets from Section 2 (Product Catalog Management Viewer, Salesforce Pricing Run Time User). Confirm both are listed under the user's Permission Set Assignments.
The user is missing one or more of the Deal Packages-specific standard permission sets from Section 2 - most commonly PlaceOrder API. Having the Revenue Cloud user permission set license alone is not sufficient; the standard permission set built on top of it must also be assigned. Assign PlaceOrder API, Create Orders from Quotes, ProductAndPriceConfiguration API, Price and Tax Calculation for Quoting, and CalculatePrices API in Setup and retry.