Main
OAuth Bot Token
Token input is placed in the Studio tab if Studio enabled. If its not, then its placed in the Project tab. You will only be able to input the token, you won’t be able to access it from here. So no one could theoretically rip it out. The token is stored in a json file at the Studio Path location. Otherwise it’s stored in the Project Pipeline json.
Notifications
Server
Settings
In the server section you will be able to input your App-Level Token that can be found on the Apps information page on Slack. This is using the same method as the Bot OAuth token above. You can only input it via the button below the text field, and you cannot access it unless you know where to look or can access it via the App page on Slack.
If you wanted to start the server here, please feel free to do so. Just know that if it is running, it will not start the server.
If you know the server is not running on a remote machine, and not running locally, chances are the ‘Start Server’ button is active. If you try and start the server from here, you will be unsuccessful. In this event you are welcome to press the ‘Reset Server’ button and then try to start the bolt server.
Prism Tray
With this plugin, you are able to check the status of the server in the Prism Tray. Just open the context menu of the tray, navigate to the Slack menu and in it you will be provided with the following:
From here you can see if the Slack Bolt Server is running by indicating it with a visual cue, and the current status. These are the current statuses:
You can choose to either Start or Stop the server as well. These commands will trigger a local server session to popup in the terminal.
The Server will not start if it is already running. However if you know it’s not running, and can’t start it, you can navigate to the Prism Settings window and choose: Reset Server. You can also do this via command line by using this: @reset_bolt_server_status