Packages

Packages bundle reusable server content so you can move a finished setup to another server or share it with the community. After installation, the imported items are regular server content: review and edit them before you rely on them.

Find and install packages

Browse public packages from the package registry, open a package to review its description and files, then choose the server where you want to install it. Install only packages from creators you trust. A package can include content that sends messages, adds commands, or defines automations, so inspect it with the same care you would apply to a configuration shared by another server.

Creating packages

Packages may be created by anyone with dashboard permissions, and may be installed by anyone on the Assistance platform to any server.

Private packages

Certain privacy options are available for packages. Packages may be set to Private, which will exclude them from appearing in any public directories. Furthermore, private packages may be password protected.

Public packages and abuse reports

Public packages appear in the registry and can be installed by other Assistance servers. If a public package is misleading, unsafe, or infringes your rights, use Report abuse from its public page. Include enough context for the team to review the report; do not include credentials or other private information.

Reports are reviewed separately from installation. Reporting a package does not remove it immediately and does not change content already installed in a server.

After installing

Installed commands and templates are just like the ones you'd create yourself — edit them freely in the command editor and the library to fit your server.

Publishing your own

You can package up your own commands and templates to reuse across servers or share with others. Build and refine everything in one server, then publish it as a package.