Import a plugin for your team

What this does for you

An administrator can bring a plugin from a git repository into the organisation as a team package. Members then add it from Plugins like any other plugin. What the plugin carries besides its servers and skills comes with it: its guidance, the values its servers need, a limit to chosen groups, and a private repository.

Before you start

• You need to be an administrator of a team organisation.
• To import from a private repository, connect its git host first: on Organisation → Packages, store a read-only token for that host. Botseon sends the token only to that host.

Steps

1. Open Organisation → Packages and, under the import, give the repository's address, the full 40-character commit and the plugin's Directory (leave it empty for the repository root).
2. Press Read plugin. The card shows everything the plugin holds at that commit: its servers, its skills, the values a member is asked for, its Guidance, and everything that was left out.
3. Press Import. If your organisation asks for a review first, the plugin waits under Imported plugins awaiting review; press Approve on its card there. Otherwise it is published at once.
4. If the plugin ships guidance, find it under Plugin guidance on the same page. Read it, then press Promote to let bots use it, or leave it switched off.
5. To offer the package to some of the team only, add it to a team marketplace and tick the groups that marketplace is for.

What members see

• Guidance is the plugin publisher's advice for its own tools. It stays switched off until you promote it. Once promoted, a bot that uses the plugin reads it as third-party text, after your organisation's rules. Switch off takes it away from the next run.
• Values. When a plugin's servers need something from each person (an API key, a tenant name), a member is asked for each value when they press Add, and the package is not added while a required value is missing. A secret is stored sealed and never shown again; the member can replace it later. The plugin's tools then run with that member's own values.
• Groups. A member outside the groups you chose does not see the package in Plugins. Its link shows them nothing, and they cannot add it.
• Link. Copy link on a package card copies a link to the package. A member it is offered to opens it and presses Add. A package that asks for values sends them to its card in Botseon to give them first.
• Private repositories. Members do not need access to the repository. The organisation keeps the copy you approved, and adding it never contacts the git host.

Good to know

• A plugin's hooks and scripts never run, and an OAuth client id it ships is never used.
• A newer commit whose guidance changed arrives switched off again, even if you promoted the earlier one.