Skip to content

Choose available components

The COMPONENT CATALOGUE half of Components & Plugins lists every component type in Profinity, and the Status column shows which ones are available. It also lets you choose which types engineers see when they add a component to a profile.

Opening the screen needs the View plugins permission and a licence that includes the Custom Plugins feature. Changing the catalogue needs Modify plugins. Refer to Install and manage plugins.

The COMPONENT CATALOGUE table lists every component type in Profinity, grouped by family. Disabling a component type or a whole group removes it from the ADD COMPONENT list without uninstalling anything. This keeps the choices short for a deployment that uses only a few device types. Enabling it again brings it straight back.

Expand a group to show its component types. Use the search box on the COMPONENT CATALOGUE table to filter by name. The Status column shows whether each row is currently available. The Actions column holds the button that changes it:

  • Disable hides a single component type, and Enable makes it available again.
  • Disable group hides every component type in a group at once, and Enable group restores them.

The change takes effect as soon as you select the button, without restarting Profinity. Enabling one component type inside a disabled group enables the group and leaves the other types in it disabled. This lets you bring back a single device without exposing the rest of its family. The components of a disabled plugin do not appear in the catalogue at all, so enable the plugin first, as described in Install and manage plugins.

Why a component can be unavailable

A component type is available only when the licence, the custom.yaml file and the site configuration (config.yaml) all allow it. Profinity checks the licence first, then custom.yaml, then config.yaml. Selecting Enable on a row that the site configuration disables removes it from the disabled list in config.yaml.

Locked and disabled rows

A row with no action button is locked, and the Status column says why.

  • Not licensed means your licence does not cover the component. Refer to Licensing.
  • Disabled (Custom.yaml) means the supplier of your Profinity build hid the component through the custom.yaml file in the config folder. Profinity only reads that file, so you cannot enable the component from this screen. To make the component available, ask your supplier.
  • Disabled means the site configuration disables the group.
  • Disabled (group) means the site configuration disables the group that holds the component.
  • Disabled (component) means the site configuration disables the component itself.

To make a Disabled, Disabled (group) or Disabled (component) row available, select Enable in its Actions column, or Enable group for a group row. The change takes effect straight away.

If an attempt to change a row fails, a message explains the reason.