Troubleshooting

Bot does not respond in Slack

Make sure the bot is added to the channel: click the channel name > Integrations > Add an App.
Try mentioning it again: @PrivMan Approvals
Check logs: docker logs privman-slack-bot

Confirm the channel is registered by mentioning the bot and checking that it replies.
The bot polls every 60 seconds — wait up to a minute after a request is submitted.
Verify there are pending requests in Privilege Manager.
Check logs: docker logs -f privman-slack-bot

Run docker logs privman-slack-bot and look for ERROR lines. Common causes:

Slack tokens expired — Regenerate the tokens in the Slack app settings and re-run the container with the updated -e values.
Privilege Manager URL or credentials changed — Re-run the container with the corrected -e values.

Verify PRIVMAN_USERNAME and PRIVMAN_PASSWORD are correct.
Confirm PRIVMAN_BASE_URL ends exactly with /Tms.
Verify the API client exists in Privilege Manager and has the Privilege Manager Administrators role.

Run docker logs privman-slack-bot to see the error. The most likely cause is a missing or incorrect SLACK_BOT_TOKEN or SLACK_APP_TOKEN.

The SLACK_BOT_TOKEN variable is missing or empty. Verify your -e flags in the docker run command.

The container writes channel data relative to its working directory /app/data. Make sure the named volume is mounted correctly:

-v privman-bot-data:/app/data

USE_LOCAL_STORAGE is not set to true. Add -e USE_LOCAL_STORAGE=true to your docker run command.

Item	Value
Docker image	`delineaxpm/privman-slack:latest`
Default poll interval	60 seconds
Auto-approve duration	4 hours
Data volume	`privman-bot-data` (named Docker volume)
Data path inside container	`/app/data`
Runtime user	Non-root