Access CPQ Admin Home Page
The Conga Revenue Lifecycle Platform offers a streamlined login process by leveraging an external Identity Provider (IDP). This IDP integration is established through the widely adopted OAuth 2.0 protocol, facilitating seamless communication between the application and the external identity provider. Additionally, you have the option to sign in using a SAML username.
This approach eliminates the need to create new login credentials specifically for the Conga Platform application. Instead, you can utilize your existing credentials from trusted third-party identity providers or your SAML username for Signin.
- Microsoft
- Salesforce
- Salesforce Sandbox
- Dropbox
- Conga IDP
You can log in to the same organization with different user credentials using two separate tabs in a single browser window.
Signing-in to Conga Revenue Lifecycle Platform
Your Salesforce org must be onboarded on the Conga Revenue Lifecycle Platform. Contact your Conga Representative for the onboarding.
- Open the Conga Revenue Lifecycle Platform URL in the web browser. For example, https://<org Instance URL>.congacloud.io/cadmin. It will redirect you to the Conga Platform login screen.
- Enter your username and password and click Log In.
If you forgot your password, follow the selected Identity Provider or Single Sign-On process to reset your password.
Feature Settings
A feature setting is a configuration flag that controls the behavior of a specific feature within the application. Each setting is typically a simple boolean value — true to turn the associated behavior on, false to turn it off.
- They are applied at the tenant level, so the same feature can be enabled for one tenant and disabled for another.
- An administrator turn functionality on or off without requiring new code or a redeployment.
- Feature settings are designed to support controlled overrides, safe feature rollouts, and low‑latency reads.
CPQ Advantage Platform provides a single, unified system for storing, retrieving, and managing feature settings across every tenant. Feature settings are stored within Platform Config‑Management store. Any time a tenant's feature setting is overridden from its default, that override is captured in this shared configuration.
- A category that groups the entry with other revenue configuration.
- A configuration key that identifies it as the feature settings collection.
- A value, which is a serialized collection of name/value pairs — one entry per feature setting for that tenant.
{
"Category": "cpq",
"Name": "featuresettings",
"Value": "{\"EnableDisplayActionCallback\": true, \"EnableValidationCallback\": true, \"EnableCartLifecycleCallback\": true, \"EnablePriceRamps\": true, \"EnableAttributeMatrix\": true, \"EnableAttributeRule\": true, \"EnableApprovalCheck\": true, \"EnableDealGuidance\": true, \"EnableTotalingCallback\": true, \"EnableRelatedPricingCallback\": true, \"EnablePricingCallback\": true, \"EnableWildCard\": true, \"EnableProductFilterCallback\": true, \"EnableStoreModelLibrariesInPlatformDb\": true, \"EnableAssetPricing\": true, \"EnableBulkRecordSync\": false, \"EnableConfigProcessAfterPricing\": false, \"EnableResyncWorkerFlow\": false, \"UsePlatSearchConfiguration\": true,\"EnableProductDetailsOptionPagination\": false,\"EnablePriceWaterfall\":false,\"EnableSummaryGroupPriceWaterfall\":false,\"EnableBundleOptionRollupOnPriceWaterfall\":true,\"EnableConditionalChargeTypeForAssets\":false, \"EnableAIAgent\":false,\"EnablePaymentIntegration\":false,\"EnableTaxIntegration\":false }"
}| Property | Description |
|---|---|
Name | The name of the feature setting. |
Value | The boolean value (true/false) that controls the feature's behavior. |
Description | Explains the setting's purpose or functional impact. |
Category | The logical grouping the feature belongs to. |
SubCategory | An optional, more specific grouping under the main category. |
ImpactedComponents | The application components or modules affected by the setting, such as Catalog or Pricing. |
CreatedDate | The date the feature setting was created. |
IntroducedInRelease | The release in which the feature setting first became available. |
OverrideInRelease | The release in which the setting's value is automatically updated to its latest default for all existing tenants. |
DeprecatedInRelease | The release in which the setting is removed from all tenants and retired from use. |
Internal | Whether the setting is visible to and modifiable by administrators, or reserved for internal use only. |
The feature setting lifecycle:
-
Introduced: Defined with a default value. Applied to new tenants during onboarding and to existing tenants during their next upgrade.
-
In use: Each tenant can have its own value, read with a safe fallback to the default if nothing is explicitly set.
-
Overridden (optional): At a chosen release, existing tenants' values are refreshed to the latest default automatically.
-
Deprecated: Removed from every tenant's configuration and no longer read or used by the application.
Override feature settings:
To override existing feature setting values, define the override metadata within the feature setting itself. The override is applied automatically during the upgrade process for the specified release version. Locate the target feature setting and set the OverrideInRelease field with the appropriate release version. Ensure the feature setting has a valid default value in the seed data. During the specified release upgrade, the existing value will be automatically overridden with this latest default value.
- OverrideInRelease represents the release version in which the override is applied.
- The feature setting must already exist in the seed data.
- The feature setting must have a valid default value defined.
- No separate override configuration is required; override behavior is driven entirely by the feature setting metadata.
- During upgrade to the specified release version, the revenue upgrade worker reads feature settings from the seed data, including override metadata.
- For each feature setting where OverrideInRelease matches the target release, the existing tenant value is automatically overridden with the latest default value defined in the seed data.
Deprecating a feature:
Locate the target feature setting and set the DeprecatedInRelease field with the appropriate release version. Ensure the feature setting is no longer consumed in the codebase beyond the release.
- DeprecatedInRelease represents the release version in which the feature setting is deprecated.
- No separate deprecation configuration is required; deprecation is driven entirely by feature setting metadata.
- Deprecated feature settings should not be used in any new development or logic beyond the specified release.
- During upgrade, the revenue upgrade worker reads feature settings from the seed data.
- All feature settings with a non-empty DeprecatedInRelease value are identified as deprecated.
- Such feature settings are removed from all existing customer configurations as part of the upgrade.
- Deprecated feature settings are no longer returned or consumed by the system post-upgrade.
API Endpoints
GET api/revenue-admin/v1/feature-settingsGET api/revenue-admin/v1/feature-settings/{feature-setting-name}GetFeatureSettingValueAsync(string featureSettingName)GetFeatureSettingValueAsync(string featureSettingName)