How Centro Works with Slack Connect, Single Channel, and Multi-Channel Guests
Centro helps teams work with Salesforce directly in Slack—whether it’s updating records, creating cases, or surfacing key insights. But not all Slack users have the same capabilities, especially when dealing with external collaborators or guest accounts. Here’s how Centro behaves with different user types and workspace configurations:
π Slack Connect Channels
Slack Connect allows multiple organizations to collaborate in a shared channel. Centro supports Slack Connect but behaves differently depending on where it’s installed.
If Centro is only installed in your workspace:
β Your users can use all Centro features: shortcuts, slash commands, case creation, record updates, etc.
π External users (from the other org):
Can see Centro messages (e.g., record previews, updates, case threads)
Can interact with Centro bot (e.g., click buttons, respond in threads)
Cannot use shortcuts or slash commands from Centro unless they install Centro in their own workspace
π Messages and updates posted by Centro are visible to all users in the channel, no matter who triggered them.
β οΈ Note: Slack Connect channels do not inherit app permissions across organizations. Each org must install Centro to use app-based features independently.
π€ Single-Channel Guests
Slack’s single-channel guests are often used for limited access, such as bringing in a client or vendor to one support or project channel. Centro supports several important interactions with these users.
What single-channel guests can do with Centro:
β See messages and bot posts from Centro (e.g., case updates, Salesforce previews)
β Interact with buttons and modals (e.g., click “Add Comment” and see a modal form)
β Use interactive link triggers (e.g., emoji reactions or message buttons to start workflows)
β Trigger unfurls when posting a registered domain (e.g., Salesforce link unfurls via Centro)
β @mention the Centro bot to initiate context
β Cannot use slash commands (e.g., /centro create case) — they’ll see an error: “This command can’t be used by guests in this workspace.”
β Cannot use app shortcuts (global or message-level)
β Cannot install apps or manage them via Slack app settings
π Even though they’re limited, single-channel guests can still be part of a productive workflow via interactive messages and proactive Centro automation.
π₯ Multi-Channel Guests
Multi-channel guests can access several channels and have broader permissions, but still aren’t full members.
What multi-channel guests can do with Centro:
β View Centro content and receive real-time Salesforce updates
β Use interactive elements (buttons, modals)
β In some workspaces, may be configured to use certain shortcuts or triggers
β οΈ Slash command and shortcut support is limited, and must be explicitly enabled via Slack admin settings
β Cannot install or manage apps across the workspace
β
Recommendation: For external consultants or vendors who need access to multiple parts of a project, multi-channel guest access + Centro visibility is often a solid configuration.
Summary Table
User Type | View Centro Bot Posts | Use Interactive Elements (Buttons/Modals) | Trigger Centro Workflows | Use Slash Commands | Install App |
---|---|---|---|---|---|
Slack Connect (Other Org) | β Yes | β Yes (if bot in channel) | β No (unless app is installed in their org) | β No | β Yes (in their org) |
Slack Connect (Your Org) | β Yes | β Yes | β Yes | β Yes | β Yes |
Single-Channel Guest | β Yes | β Yes (Buttons, Link Triggers, Emoji) | β Yes (via triggers) | β No | β No |
Multi-Channel Guest | β Yes | β Yes | β οΈ Maybe (admin-configurable) | β οΈ Maybe | β No |
Final Thoughts
Centro is built to flex across Slack’s complex permission model while ensuring secure and visible collaboration across internal and external teams. Whether you’re bringing in customers via Slack Connect, or onboarding vendors via guest access, Centro ensures everyone stays informed—without compromising control.