Slack Enterprise users with multiple teams cannot use Lookerbot when the enableSharedWorkspaces configuration option is not enabled, while this should be the case when the user is part of the same workspace as the lookerbot user.
Cause of this problem is the Slack API not returning the "team_id" attribute for enterprise users.
The following data is pulled from the lookerbot by logging the user object returned from the Slack API when an Enterprise user is requesting a lookerbot command:
Slack Enterprise users with multiple teams cannot use Lookerbot when the
enableSharedWorkspaces
configuration option is not enabled, while this should be the case when the user is part of the same workspace as the lookerbot user.Cause of this problem is the Slack API not returning the "team_id" attribute for enterprise users.
Regular Slack users API response
https://api.slack.com/methods/users.info
Typical success response:
Enterprise Slack user API response
The following data is pulled from the lookerbot by logging the user object returned from the Slack API when an Enterprise user is requesting a lookerbot command:
Todo
Workspace membership validation https://github.com/looker/lookerbot/blob/master/src/services/slack_service.ts#L183 should also check on the
user.teams
to confirm a user is or is not part of the same workspace as the lookerbot user.