Skip to main content

High-risk settings

đź“ť Note: If the AppDirect logo appears in the upper-left corner of the page, when Manage > Marketplace appears in this topic, click the grid icon > Switch to | Store, instead.

When Marketplace Managers attempt to change some marketplace settings, a dialog warns them that there is a high risk that the change could adversely affect the marketplace, billing, or users. When users (including AppDirect) change a high-risk setting, Marketplace Managers receive an email alert and a record of the change appears in the Event Logs table at Manage > Marketplace > Dashboard > Events | Event Logs.

High-risk settings pose a major or critical risk, defined as follows:

  • Major risk: There might be an impact on user experience, workflows, or billing.
  • Critical risk: There will be an impact on user experience, workflows, or billing.

The following list includes all the high-risk settings, how to find them in the user interface (UI), configuration options, risk ratings, and the risks if you change them.

Checkout v2 | All products​

Location in the UI—Go to Manage > Marketplace > Settings > Billing Functionality > Checkout | Checkout v2 | All products.

Default configuration—Unchecked.

Expected configuration—Unchecked. Marketplace Managers configure, by product, which products customers purchase with Checkout v2. Marketplace Managers then use the End users purchase with checkout v2 product setting that appears at Manage > Marketplace > Products > Catalog | Production Catalog > Product name | Gear icon > Edit Marketplace Settings > General to specify the products that customers purchase with Checkout v2.

Alternative configuration—Checked. Customers purchase all products with Checkout v2.

Risk if changed—Major.

  • When Marketplace Managers change this setting from unchecked to checked, checkout will fail if Checkout v2 does not support the product type or the products are configured for Checkout v1.
  • When Marketplace Managers change this setting from checked to unchecked, checkout will fail if the selected checkout version does not support the product type or the products are not configured for the selected checkout version.

Customer access​

For a description of this setting and the procedures to change it, see Configure Developer settings.

Location in the UI—Go to Manage > Marketplace > Settings > Settings | Developers > Developer Portal | Customer Access.

Default configuration—Unchecked.

Expected configuration—Unchecked. Developers can view customer data for customers who purchase their products.

Alternative configuration—Checked. Developers cannot view customer data for customers who purchase their products.

Risk if changed—Major.

  • When Marketplace Managers change this setting from unchecked to checked, Developers no longer have access to customer data to which they previously had access.
  • When Marketplace Managers change this setting from checked to unchecked, Developers have access to customer data to which they previously did not have access.

Daily spend limit​

For a description of this setting and the procedures to change it, see Configure purchase restrictions.

Location in the UI—Go to Manage > Marketplace > Settings > Settings | Billing Functionality > Purchase Restrictions | Daily Spend Limit.

Default configuration—Unchecked.

Expected configuration—Unchecked. Companies can spend an unlimited amount per day on new marketplace purchases.

Alternative configuration—Checked. Companies can only spend a maximum amount per day on new marketplace purchases. The value of recurring subscriptions is not included in this daily limit. (When you select Daily Spend Limit and then click Confirm in the dialog to indicate that you understand the impact of this change, the Set spend limit field appears for you to enter a maximum daily new purchase value.)

Risk if changed—Major.

  • When Marketplace Managers change this setting from unchecked to checked and set a maximum daily spending limit, customers could be blocked from making purchases that they want to make and daily revenue per customer is limited.
  • When Marketplace Managers change this setting from checked to unchecked, customers can purchase without limitation and revenue potential is no longer constrained.

Domain grace period​

For a description of this setting and the procedures to change it, see Configure subscriptions.

Location in the UI—Go to Manage > Marketplace > Settings > Settings | Billing Functionality > Subscriptions | Domain Grace Period.

Default configuration—15.

Expected configuration—30. When Marketplace Managers enter a number of days greater than zero, the marketplace waits that number of days after domain registration invoices become due to suspend customer subscriptions and their access to applications Although 30 days is common, it can be set to any number of days.

Alternative configuration—Blank or 0. If the Marketplace Manager makes this setting blank or enters zero, the marketplace suspends subscriptions and customer access to domains when invoices become overdue.

Risk if changed—Major.

  • When Marketplace Managers change this setting to a lesser number of days, customers could lose access to domains before they expect to. AppDirect recommends that you do not do this after marketplace launch.
  • When Marketplace Managers change this setting to a greater number of days, there is no risk to customers but it may delay payment collection for the marketplace.

Allow Vendors to configure contract restrictions per price​

For a description of this setting and the procedures to change it, see Configure contracts.

Location in the UI—Go to Manage > Marketplace > Settings > Billing Settings | Billing Functionality > Contracts | Enable advanced options for subscription changes with contracts > Allow developers to configure contract restrictions per price.

Default configuration—Unchecked.

Expected configuration—Unchecked. Developers do not have edition contract configuration fields available to block customers from upgrading, downgrading or changing the number of units purchased.

Alternative configuration—Checked. Developers have additional edition contract configuration fields available to block customers from upgrading, downgrading or changing the number of units purchased.

Risk if changed—Major. When you change this setting, the terms of existing contracts change.

  • When Marketplace Managers change this setting from checked to unchecked, the contract restrictions are removed and upgrades, downgrades, and quantity changes that were not allowed for existing subscriptions at the time of purchase become permitted.
  • When Marketplace Managers change this setting from unchecked to checked and configure contract upgrade, downgrade, and quantity change restrictions, all new and existing subscriptions are subject to them.

Was this page helpful?