> For the complete documentation index, see [llms.txt](https://apis.rightrev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration.md).

# Configuration

- [Tenant Configuration](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/tenant-configuration.md): Users can manage various functionalities which are to be active and inactive in specific RightRev tenants based on their business requirements.
- [SSP Policy](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/ssp-policy.md): Defines rules for Standalone Selling Price calculations and allocation methods. API transactions referencing bundled items rely on this policy for revenue allocation.
- [SSP policy by upload method](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/ssp-policy/ssp-policy-by-upload-method.md)
- [SSP policy by formula method](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/ssp-policy/ssp-policy-by-formula-method.md)
- [SSP policy by calculator method](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/ssp-policy/ssp-policy-by-calculator-method.md)
- [Revenue Policies](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/revenue-policies.md)
- [Identify Customer Contract](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/revenue-policies/identify-customer-contract.md): Establishes the logic and rules used to identify or derive a customer contract from incoming API data. This policy ensures consistent contract grouping
- [Revenue Rules](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/revenue-policies/revenue-rules.md): Defines the conditions and methods used to determine how and when revenue should be recognized. These rules guide the transformation of API inputs into revenue events.
- [User Defined Events](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/revenue-policies/user-defined-events.md): Allows configuration of custom transaction types or events beyond standard system-defined events. API-triggered events are interpreted based on these definitions.
- [Holds](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/revenue-policies/holds.md): Define Holds which can be applied to revenue contracts to prevent revenue release or revenue recognition when data discrepancies occur. System holds are pre-defined and triggers automatically.
- [Contract Amendments](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/revenue-policies/contract-amendments.md): Specifies the rules for processing changes to a contract, including upgrades, downgrades, and modifications triggered by API inputs.
- [Bundle Configuration](https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration/revenue-policies/bundle-configuration.md): Determines how bundled products or services are structured and processed. This policy guides allocation and treatment of bundle components when received via APIs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://apis.rightrev.com/rightrev-rest-api/policy-sets/configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.