mirror of
https://github.com/42wim/matterbridge.git
synced 2024-11-22 12:09:30 +01:00
Link out to official slack docs on tokens.
parent
eba88c0965
commit
b78d9050aa
@ -10,6 +10,8 @@
|
||||
# Bot-based Setup
|
||||
Slack's model for bot users and other third-party integrations revolves around Slack Apps. They have been around for a while and are the only and default way of integrating services like Matterbridge going forward.
|
||||
|
||||
Slack Docs: [Bot user tokens](https://api.slack.com/docs/token-types#bot)
|
||||
|
||||
## Create the Slack App
|
||||
1. Navigate to [your Apps page](https://api.slack.com/apps). You'll need to be logged in with an account that has administrative permissions over the Slack Workspace (server) that you want to sync with Matterbridge.
|
||||
|
||||
@ -63,6 +65,8 @@ Now you are all set to go. Just configure and start your Matterbridge instance a
|
||||
|
||||
🛑 This setup is not recommended and will disappear in future versions of Matterbridge. Please use it only if you are absolutely sure that you can not use the normal setup. Legacy tokens are, as their name indicates, a legacy feature and Slack can in the future **deprecate them at short notice** as they have a weak security model and **give access to a wide-range of privileged actions**. Always store your token securely!
|
||||
|
||||
Slack Docs: [Legacy tokens](https://api.slack.com/docs/token-types#legacy)
|
||||
|
||||
***
|
||||
|
||||
In order to use this setup your channel configuration should use the `slack-legacy` setup instead of `slack`:
|
||||
|
Loading…
Reference in New Issue
Block a user