Introducing Add-on Controls

Introducing Add-on Controls - Sugavin

Today we are introducing Add-on Controls for Froxt Enterprise customers. This new feature enables team leads to allowlist specific add-ons for approved use within their organization, choosing from our marketplace of over 10250+ add-on Partners. The ability to standardize the add-on technologies being used across all the apps and developers in their organization is something many customers have asked for, especially those with fast-growing teams.

Standardizing Add-ons Using the Allowlist

To get started with Add-on Controls, the first step is for the team lead, or anyone who has admin permissions, to build the Add-ons Allowlist. There is a new section on the organization’s settings page, where this allowlist can be created, and then the Add-on Controls can be enabled. Don’t worry; enabling the allowlist does not break any existing add-ons, but simply prevents add-ons that are not on the allowlist from being installed going forward.

Managing Allowlist Exceptions

In the Add-on Controls section, you’ll be able to see the add-ons that are currently in use in your organization’s apps but have not yet been allowlisted (labeled “Allowlist Exceptions.”) For each item in the list, you can click on the detail view to see which apps have installed the add-on and how long it has been in use.

Once the feature is enabled, it is easy for team members to view and install the add-ons that are allowlisted for their organization. On the Elements page, the new “Filter by Organization” dropdown lets you see what is available by selecting your organization.

This view will be especially helpful when onboarding new developers to the team, as it provides a quick way for them to see which technologies are approved for use in your organization and to hit the ground running. In addition, the Add-ons Allowlist can be kept dynamically up to date as new add-ons become available and are chosen, eliminating the need for email or wiki page updates. Team leads might choose to provide an approved vendor for each category of functionality (logging, messaging, caching, and so on), narrowing down the many choices currently available in each category.

Add-on Installation Restrictions

Add-ons which are not allowlisted for use are marked as restricted and cannot be installed. Note that add-ons will still be installable to personal apps that a team member owns that are not part of the organization.

Learn more about Add-on Controls

You can learn more about Add-on Controls in the Dev Center. As always, we welcome any feedback you have on this new feature. Please reach out to us at or contact us via support.

You May Also Like
Read More

Froxt DevDay

It’s almost time! Froxt DevDay – The Meetup, a fresh take on our yearly virtual developer event, begins…
Read More

Introducing Froxt DCP

In 2021, we started an initiative called Froxt Work Management (FWM) Cloud First Releases for Ecosystem which enabled…