Using Dailybot in your Slack Enterprise Grid environment
Slack Enterprise Grid (EG) lets one Slack organization contain many workspaces (one per business unit, department, or subsidiary). Dailybot works on Enterprise Grid; this article explains how the bot treats users and channels across the workspaces inside your directory so you can plan installation and avoid surprises.
Quick check
- Apps on Enterprise Grid install at the directory level. A single Dailybot install can be made available to all workspaces inside the directory, subject to Slack admin permissions.
- Dailybot treats each workspace as an independent context. A user who belongs to several workspaces may have a separate Dailybot user record per workspace.
- Shared channels are supported. Dailybot can post check-in reports to channels shared between workspaces. Look for the shared-channel icon next to the channel name in Slack.
How Dailybot behaves across workspaces
When the same person uses Dailybot from different workspaces inside the directory, the bot keeps a separate context per workspace. An example with two users – Alice and Bob – in a directory with three workspaces (Product, Business, Operations):
- Bob is only in Product. Dailybot knows him as “Bob from Product” and behaves the same way every time.
- Alice is in Product, Business, and Operations. Dailybot keeps three separate contexts: “Alice from Product”, “Alice from Business”, and “Alice from Operations”.
- When Alice DMs Dailybot from Business, the bot answers using the Business context only. If she moves to Operations and writes again, Dailybot switches to the Operations context.
Note: Because Dailybot is installed once at the directory level, the chat history with the bot is visible across workspaces in Slack. The bot still answers based on the workspace it received the message from, but be careful not to mix answers from different contexts.
Shared channels
Dailybot can deliver check-in reports to a channel that is shared between two or more workspaces in your Enterprise Grid. Slack marks shared channels with a dedicated icon after the channel name. Inviting @Dailybot to a shared channel follows the same flow as any other channel; permissions are inherited from the workspace where Dailybot posts the report.
If something looks off
- A user sees Dailybot but the bot does not reply: confirm the user has a Dailybot account in that specific workspace (each workspace may need its own account).
- Reports land in the wrong workspace: open Dailybot Settings > Check-ins and review the destination channel; if you moved to a different workspace recently, the channel reference may need to be updated.
- The bot disappears from one workspace: ask your Slack admin to confirm the Dailybot app is approved for that workspace inside the directory.