We're happy to announce that we now support restricted bot mode on our Keybase managed bot @sentinelbot.
The Keybase docs describe a restricted bot as a user that cannot access the contents of a conversation besides messages directed intended for them. This is a relatively new feature that lets you use a 3rd-party bot (like sentinelbot!) in a team channel without giving it access to all your messages — a perfect companion to a privacy-focused team.
Alongside support for Keybase restricted bot mode, we are also releasing a web interface to make it easier to manage all your integrations. You now have the ability to reuse your webhook URLs & mix and match them in different automation recipes to your heart's content!
Note: The migration instructions listed below only apply to customers who signed up before June 1, 2020. If you're a new opensentinel user our docs are a good starting point to get you going.
Transitioning over to using restricted bot mode roughly involves the following steps:
Sign up for an opensentinel account (if you don't already have one).
@sentinelbot from your Keybase team (in your Keybase app, under the Members tab in your Teams settings).
@sentinelbot to your team as a restricted bot user.
Re-create your Webhook URL integrations. A step-by-step example of this is documented in the Creating your first Automation Recipe guide.
You can retrieve a list of all your webhook integrations by issuing the
!list-integrations command. This will give you a full list of all your legacy integrations along with some relevant information (ID, name, channel, etc).
Finally delete your old integrations by issuing the
!delete-integration <ID> command. The
<ID> here refers to the integration ID from the previous
Note: Each of the previous bot commands are meant to be issued as private messages to
Your opensentinel webhook URL is being managed by the old chat interface if it looks like
https://api.opensentinel.com/kb/webhooks?.. The new webhook URLs are all served off the automations subdomain. Follow the migration instructions above.
Yes! We intend on supporting the legacy webhook URLs until October 1, 2020. We're also here if you need a hand migrating over.