Skip to content

Manage plugins in your organization

A plugin brings skills, commands and connectors together, and it reaches people from the marketplace it’s in. You don’t install plugins one by one for the organization: you add a marketplace and its plugins come with it.

In Inventory, each plugin is one row with the Plugin mark, and its skills and commands aren’t separate rows: you see them on the plugin’s page. The Capabilities column says how many it brings (“3 skills · 2 commands · 1 connector”), Source is its marketplace, and Users (30d) is the highest of its skills and commands.

  • Type (Any, Skill or Plugin) filters the list. It shows up when there are plugins.
  • The three dots on a plugin’s row have View plugin and Open marketplace. Tapping the row opens the plugin.

The plugin’s page shows its version, its author and its Marketplace (with a link to Marketplaces), and tabs for Skills, Commands and Connectors, each with its count (a tab with nothing in it doesn’t show). Tap Inventory, at the top left, to go back: your search, filters and page are as you left them.

A plugin gets the access of its marketplace unless you set one for it (below). A plugin in a marketplace set to Not available is still in your Inventory, but members don’t see it unless you gave it another access.

You can give one plugin its own Default access: Not available, Available to install, Installed by default or Required. Open the three dots on its row in Inventory and pick one under Default access, or use Distribution on the plugin’s page. Required asks you to confirm first, because everyone gets the plugin and can’t turn it off or remove it.

  • It wins over the marketplace’s, even when the marketplace is Not available. You can leave a big repository on Not available and turn on only the plugins you want.
  • A plugin with no access of its own keeps following its marketplace, including plugins that arrive in a later sync. The page says so: “From the marketplace. Choosing one here applies to this plugin only.”
  • It survives a sync. If the plugin’s folder is renamed in the repository, it counts as a new plugin and loses it; so does a plugin whose plugin.json disappears.
  • Plugins from the Nouter Directory can only be Available to install or Not available.

You can also set the access per group. Open the three dots on the plugin’s row in Inventory (or Distribution on its page) and pick Group access…: choose a group and one of the four values, and save. Each group with a value is listed in the same window, with Remove.

  • A group’s value replaces the organization’s for its members, even when it’s stricter. A plugin that is Not available for everyone can be Required for one group.
  • If a person is in several groups with a value, the most permissive one wins: Required, then Installed by default, then Available to install, then Not available. With no value for any of their groups, they get the organization’s.
  • The Audience column says the organization’s value and, with groups, “+ 1 group”.
  • It takes an Owner, or a custom role with Libraries on Can manage and Identity & Access on Can view. The change reaches people within a few minutes.
  • In a shared workspace, the groups that count are the workspace owner’s.

In Personal settings, Customize has Plugins too, which takes you to Customize → Plugins: the plugins you use. See Use plugins.