---
schema_version: "1"
id: 0d64062649db1b5b4e4aaca6c70fab46d2610ede9e0bb76cbcc7aefadf73efb2
title: Supported User Context
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries/cme/guides/comms-t-supported-user-context.md
canonical_url: https://developer.salesforce.com/docs/industries/cme/guide/comms-t-supported-user-context.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 3a1a35611ea6f0410f3a771aac1517a0f0c9764e272b7ba7ef1b64842d4db010
products:
  - Communications, Media, Energy and Utilities APIs (Managed Package)
  - Industries Developer Documentation
---
# Supported User Context

The context eligibility rules for a logged-in user operate in the given context of the API that determines the results of the API request. Therefore, the contents of this parameter are important in determining eligibility.

Here is a list of the identifiable user contexts that can be applied:

- The **accountId** represents the account object and populates all the dimensions that start their source expression with Account or User object. This object helps you extract the user object.

- The **contractId** represents the contract object and populates all the dimensions that start their source expression with the Contract object.

- **rootAssetIds** represent the root assets of the provided account. Root assets allow you to generate all the assets present under that root asset and based on that you can generate the context key.

  You should send only one root asset ID in the context parameter. Sending more than one root asset ID might lead to performance issues.

- The **cartContextKey**: Running the URI that has contractId, accountId, and rootAssetIds returns the CartContextKey. When you add another rule to execute for this customer, instead of writing the API context again for contractId, accountId, and rootAssetIds, you can pass the CartContextKey which represents any or all of the API contexts.