Using Plugins Estimated Reading Time: 2 Minutes A plugin adds functionality on top of the core Ubersmith system. This article covers enabling and configuring a plugin that's already installed. For building a plugin with the Ubersmith SDK, see Creating Plugins. Note: Add-ons, in the left navigation, is a separate storefront page for browsing and purchasing certain plugins. Configuring an add-on you've purchased still uses the Plugins page described in this article. Accessing the Plugins Page Go to Settings > Global Settings > Customization > Plugins. The page lists plugins in two tables: Custom Plugins (plugins uploaded to your instance) and Core Plugins (plugins that ship with Ubersmith). Both tables show the same columns: enabled status, name, version, description, and an edit action. Note: Custom Plugins - Refresh and Custom Plugins - Manage, at the top of the page, are for uploading and managing custom plugin code. That's a separate topic — see Creating Plugins. Settings, also at the top, opens plugin logging options for development and troubleshooting, not covered here. Enabling a Plugin On the Plugins page, click a plugin's name. In Plugin Details, click the toggle next to the plugin's name to switch it between DISABLED and ENABLED. Click Yes to confirm. Set Client Access to No Access, View, or Edit. This controls whether the plugin is hidden from the Client Portal, visible but read-only, or visible and editable. Click Show Implemented Hooks to see the hooks the plugin uses. If the plugin uses datasources, a Datasources row appears too, with a Show Datasources link. Adding a Module Instance Once a plugin is enabled, a Modules section appears next to Plugin Details. Each module card describes one way the plugin can be applied — for example, to order queues, datasources, service plans, brands, or device types, depending on the plugin — and lists how many instances of it already exist. On a module card, click add new instance. Under Associated Components, select what this instance applies to. Some plugins offer an Apply to all option to select everything at once, instead of picking items individually. Under Configuration, fill in the instance's settings. These fields are different for every plugin — see that plugin's own configuration article (for example, Configuring AWS Reseller Billing or Configuring the BitPay Plugin). Click Save. Note: A plugin can have more than one instance. Each instance has its own configuration — for example, one instance per brand, each with different settings. Viewing Plugin Usage The Plugin Usage section lists where the plugin's components are actually in use. Click Show [Component] Used — for example, Show Datasources Used — to view the list.