Sharing configurations
Export, import and publish configurations with short codes and Community Configs.
What is shared
Only the language, the detections and the blacklists. Permissions and webhooks are never shared. When importing, your license keeps its own.
Export Config
In the server configuration press Export Config. You get a short code like KKG8M-J2 that you can copy and give to another server. As long as the configuration does not change, the code stays the same. Codes are unique and never reused.
Import Config
- Open the configuration of the server you want to change and press Import Config.
- Paste the code (upper or lower case, the dash is added for you).
- Press Import configuration. The page reloads with the new configuration.
It is the fastest way to copy a configuration between your own servers.
Publish Config
- Press Publish Config.
- Give it a name (3 characters or more) and, optionally, a description.
- Press Publish configuration.
Your configuration appears in Community Configs for every user with a license. The button then says Published. From there you can:
- Update with current configuration: publish your current configuration (and change the name or description).
- Make private again: remove it from Community Configs. The publication code stops working, but Export Config codes keep working.
Each license can only have one publication. You need an active license to publish.
Community Configs
In the sidebar, Community Configs lists the published configurations, most imported first. Anyone can open the page, but only users with a license see the list.
Each card shows the name, author, date, description, enabled detections, how many blacklist entries it has, the language and how many times it was imported.
- Preview: see every detection (enabled or not) and the blacklists before importing.
- Import: choose which of your licenses receives it and confirm.