Optimize Resource Sharing with Grant Binding

Learning Objectives

After completing this unit, you’ll be able to:

• Describe the purpose of binding grants to targets like accounts or contracts.
  
• Explore Binding Type, Binding Target Type, and Binding Target on line items.
  
• Set up a usage product grant binding policy.
  
• Create a quote and review grant binding.
  

Before You Start

Before you start this badge, make sure you complete this content. The work you do here builds on the concepts and work you do in that content.

• Agentforce Revenue Management Foundations
  
• Usage Management Foundations
  
• Usage Management with Agentforce Revenue Management
  
• Enhanced Usage Selling with Agentforce Revenue Management
  

Meet Grant Binding

In big organizations, various departments purchase usage resources as per their needs. These resources are often of the same type. For example, AI credits or data tokens. This creates separate, isolated wallets—one per asset, per purchase. If one department exhausts their credits midmonth while another department has a surplus, there’s no way to share that balance. And that leads to fragmented visibility of usage resources and wastage of unused entitlements. Wouldn’t it be great if organizations had a shared pool or a single grant balance that all teams within an account could access? This is where grant binding comes in.

Using grant binding in Agentforce Revenue Management, you can associate grants with a specific target such as an account or a contract, so that all consumption linked to that target draws from one shared pool. Think of it like a family mobile data plan. Instead of each family member having their own separate data allowance, the entire family shares one large pool. If one member uses less, another can use more. Grant binding applies this same principle to your usage products: You get efficient resource distribution, zero wastage, and maximum flexibility.

A Business Scenario

InfinitraBytes is a leading electronic products and solutions provider. Liam Hoko, the usage management admin at InfinitraBytes, uses Agentforce Revenue Management to constantly enhance the company’s consumption-based product offerings.

In the Enhanced Usage Selling with Agentforce Revenue Management badge, you learned how token resources enable customers to purchase virtual tokens and redeem them across a range of products. You also created the AI Services Plan, an InfinitraBytes product that is now in high demand. Many InfinitraBytes customers have subscribed to this plan, and now the sales team is ready to take things even further.

Most big customers of InfinitraBytes have multiple teams and departments that use the AI Services Plan. Currently, each team purchases and manages its own plan. There’s no way to share the remaining credit balances across teams, which leads to wastage. Liam wants to use the grant binding feature in Agentforce Revenue Management to resolve this. In this badge, follow along as he sets up grant binding for efficient pooling of usage resources and uses wallets to track them.

Time to explore grant binding policies. But first, start by setting up your own Salesforce org.

Sign Up for a Developer Edition Org with Agentforce Revenue Management

To complete this badge, you need a special Developer Edition org that contains Agentforce Revenue Management and our sample data. Get the free Developer Edition and connect it to Trailhead now so you can complete the challenges in this badge. Note that this Developer Edition is designed to work with the challenges in this badge, and might not work for other badges. Always check that you’re using the Trailhead Playground or the special Developer Edition org that we recommend.

1. Sign up for a free Agentforce Revenue Management Developer Edition org.
   
2. Fill out the form.
   

• For Email, enter an active email address.
  
• For Username, enter a username that looks like an email address and is unique, but it doesn’t need to be a valid email account (for example, yourname@example.com).
  
• For Country, select United States. Your Developer Edition org uses USD as currency. So to pass all the challenges, we need the country to be set to the United States.
  

3. After you fill out the form, click Sign me up. A confirmation message appears.
   
4. When you receive the activation email (this might take a few minutes), open it and click Verify Account.
   
5. Complete your registration by setting your password and answering the challenge question. Tip: Save your username, password, and login URL in a secure place—such as a password manager—for easy access later.
   
6. You’re logged in to your Developer Edition Org.
   

Now connect your new Developer Edition org to Trailhead.

1. Make sure you’re logged in to your Trailhead account.
   
2. In the Challenge section at the bottom of this page, click the playground name and then click Connect Org.
   
3. On the login screen, enter the username and password for the Developer Edition you just set up.
   
4. On the Allow Access? screen, click Allow.
   
5. On the Want to connect this org for hands-on challenges? screen, click Yes! Save it. You’re redirected back to the challenge page and ready to use your new Developer Edition to earn this badge.
   

Sync Pricing Data

Now that your org is connected, make sure it’s ready to use. How? You sync pricing data and refresh some decision tables. Make sure you complete these steps to pass the challenge (but we won’t check this).

1. From Setup, in the Quick Find box, search for and select Salesforce Pricing Setup.
   
2. Under the Sync Pricing Data section, click Sync.
   

3. Confirm that you want to sync your org.
   

The pricing data sync may take a few minutes to complete.

Refresh Decision Tables

Follow these steps to refresh decision tables so that the latest pricing data is available in your org.

1. From Setup, in the Quick Find box, find and select Decision Tables.
   
2. From the available decision tables list, select Price Book Entries V2.
   
3. Click Refresh.
   

4. Similarly, refresh all these five decision tables.
   

• Pricebook Rate Card Entries
  
• Rate Adjustment by Tier Entries 2
  
• Rate Adjustment by Tier Resolution Entries
  
• Rate Card Entries 2
  
• Rate Card Entry Resolution Entries 2
  

Make sure the Last Refreshed Date updates to your current date and time. Refresh the page if you don’t see the update.

Explore Grant Binding Policies

In Agentforce Revenue Management, grant binding behavior is managed through the Usage Product Grant Binding Policy object. This is where you define how grants are distributed and which target they are bound to.

When you create a Usage Product Grant Binding Policy, you configure two key fields–Grant Binding Type (1) and Grant Binding Target (2).

Choose Your Grant Binding Type

There are two primary ways to handle how grants are associated.

• Self: Select this if the usage grant should stay tied directly to the anchor product's own asset. The grant remains dedicated to the specific product it was purchased with.
  
• Target: Select this when you want to associate the grant with an external target such as an account, contract, or custom object. This is what enables grant pooling across multiple departments or teams.
  

Define Your Grant Binding Target

There are four possible targets for grant binding.

• Product: Grants are pooled at the product level. All line items for the same product share a single grant balance, regardless of account.
  
• Account: Grants are pooled at the account level. All line items under the same account share one grant balance.
  
• Contract: Grants are pooled at the contract level. All line items linked to the same contract share a single grant balance.
  
• Custom: Grants are pooled at a custom object level, defined by your specific business needs.
  

Create a Grant Binding Policy

For InfinitraBytes, the goal is to pool the grants associated with the AI Services Plan across all teams within the same account. Follow along with Liam to configure this in your DE org.

1. From the App Launcher, find and select Usage Product Grant Binding Policies.
   
2. Click New.
   
3. Add these details.
   

• Name: AI Credits Account Binding Policy
• Product: AI Services Plan
  
• Grant Binding Type: Target
  
• Grant Binding Target: Account
  

4. Save your changes.
   

With this setup, the grants for AI Credits and AI Agent Interactions associated with the AI Services Plan are bound to a specific account. As a result, all consumption records for that account draw from a shared pool of credits.

Review Grant Binding on a Quote

When a sales rep adds a usage product to a quote, the system uses your grant binding policy to determine how to pool those resource grants. For InfinitraBytes, this means when a customer signs up for the AI Services Plan, their credits are automatically funneled into a shared account-level bucket. This centralized approach ensures that any department under the same account can use the same pool of AI credits.

Follow along to create a quote and see the runtime behavior of grant binding on it.

1. From the App Launcher, find and select Quotes.
   
2. Click New Quote.
   
3. Add these details.
   

• Quote Name: Grant Binding Test
• Start Date: Today’s date
  
• Account for Quote: EdgeMX
  

4. Save your changes.
   
5. From the newly created quote page, click Browse Catalogs.
   
6. In the Choose Price Book window, make sure Standard Price Book is selected, and save your work.
   
7. In the All Catalogs list, select Service Catalog, and click Next.
   
8. From the products list, select AI Services Plan, and click Add.
   
9. Click Save Quote.
   
10. From the AI Services Plan line item, click , and then select Manage Usage Resources. If you don’t see the action menu scroll to the side.
    

11. On the Manage Usage Resources page, select these details
    
    • Binding Type: Target
      
    • Binding Target Type: Account
      
12. Notice that the Binding Target is automatically updated. Close the window.
    

The options available for the binding fields are based on the policy you created. By selecting the appropriate values, you confirm that grants are correctly pooled and available to all consumption records associated with the EdgeMX account.

Understanding Rates in Grant Binding

When multiple assets are bound together under the same grant binding target, they share not just their usage entitlements but also their rates. However, because individual assets might be purchased at different times or price points, Agentforce Revenue Management automatically calculates a single winning rate to ensure consistent and fair billing across the entire shared pool.

The winning rate is determined automatically based on two rules.

• Latest: The rate from the asset with the most recent start date takes precedence.
  
• Cheapest: If two or more assets share the exact same start date, the lowest rate among them is selected.
  

When determined, this winning rate is uniformly applied to all consumption activity across every asset bound to that target, whether it is a product, account, contract, or custom object. This ensures that customers receive consistent, predictable billing, regardless of which team or department generated the usage. To learn more about how rates are resolved across bound assets, see Anchor Product with Packs.

Next Up

Good job! You have successfully configured grant binding: You associated all the available grants to an account so that usage resources can be shared across the organization. In the next unit, discover the Wallets Dashboard and how to use wallets to monitor consumption of usage resources.

For now, make sure to click Check Challenge to Earn 500 Points.

Resources

• Salesforce Help: Grant Binding