Share newsletters to multiple Slack and Microsoft teams workspaces

Overview

When creating or sharing a newsletter, newsletter managers can now choose which Slack or Microsoft Teams workspace to use based on the workspaces they are allowed to access. This is especially useful for organizations where a single user may be connected to multiple Slack or Microsoft Teams workspace instances in the intranet.

Before you begin

This feature is intended for newsletter managers who share newsletters to Slack or Microsoft Teams. It is generally available for AWS customers.

What changed

Previously, newsletter sharing flows could rely on a single connected workspace or default to the first available connected workspace. In environments with multiple workspace instances, that made it harder to control where a newsletter was shared.

With this update, Simpplr supports multi-instance Slack and Microsoft Teams connections in newsletters, so eligible users can select the right workspace for the audience they are working with.

• Choose from multiple connected Slack workspaces

• Choose from multiple connected Microsoft Teams workspaces

• See only workspace options you are allowed to access

• Use the selected workspace in newsletter configuration and share flows

• Retain the existing simpler experience when only one workspace is available

How it works

If your organization has configured multiple Slack or Microsoft Teams workspaces and you have access to more than one of them, Simpplr will show a workspace selector while setting up newsletter sharing.

The selected workspace is preserved for the newsletter so the correct workspace can be restored later.

Access and visibility rules

This feature respects workspace permissions and audience-based access controls. Users only see the workspaces and channels they are allowed to use.

• Only accessible Slack or Microsoft Teams workspaces are shown.

• Only channels from the selected accessible workspace are available.

• Users do not see channel names from workspaces they cannot access.

• Share options can be hidden when the user does not have access to any eligible workspace.

Workspace and channel visibility is based on the logged-in user's allowed access. Different users may see different workspace choices for the same tenant.

Where you can select a workspace

The multi-instance experience is supported in the main newsletter sharing flow and in related sharing actions.

• Newsletter configuration: Choose the Slack or Microsoft Teams workspace while configuring the newsletter.

• Share flows: Choose the workspace when sharing a newsletter to Slack or Microsoft Teams.

• Listing page actions: Share actions respect the same access rules and only appear when available to the user.

If a saved newsletter is already linked to a workspace you can access, that saved workspace selection is restored correctly.

What this improves

• Better control: Choose the right workspace for the intended audience.

• Cleaner experience: No need to rely on an arbitrary default workspace.

• Safer sharing: Inaccessible workspaces and channels are not exposed to users.

• Consistency: The same multi-instance logic applies across newsletter configuration and sharing flows.

Troubleshooting

The workspace selector is not appearing even though multiple workspaces are configured.

What happened: The workspace selector only appears when the logged-in user has access to more than one connected workspace. If only one workspace is accessible to that user, no picker is shown and the single-workspace experience continues as before.

What to do: Confirm that the user has been granted access to more than one Slack or Microsoft Teams workspace in the tenant configuration. If multiple workspaces should be accessible to that user and the picker is still not appearing, verify that the relevant workspace permissions and audience-based access settings are configured correctly.

The Slack or Microsoft Teams sharing option is not visible in the newsletter flow.

What happened: Share options are hidden when the logged-in user does not have access to any eligible tenant-level Slack or Microsoft Teams connection. This is by design to prevent users from seeing or attempting to share to workspaces they are not permitted to access.

What to do: Confirm that at least one Slack or Microsoft Teams workspace is connected at the tenant level and that the user has been granted access to it. If the workspace connection exists and the user should have access, review the audience-based access settings for that workspace. If the issue persists, raise a support request.

A previously saved workspace selection is not being restored when editing a newsletter.

What happened: The selected workspace is preserved with the newsletter configuration so it can be restored during subsequent edits. If the saved workspace is no longer being restored, the workspace may have been disconnected, or the user's access to that workspace may have changed since the newsletter was last saved.

What to do: Open the newsletter and check whether the previously selected workspace is still available in the workspace selector. If the workspace is no longer listed, confirm that it is still connected at the tenant level and that the user retains access to it. Select the correct workspace again and save the newsletter configuration.

A user can see workspace options that should not be available to them.

What happened: Workspace and channel visibility is based on the logged-in user's allowed access as defined by workspace permissions and audience-based access controls. If a user is seeing workspaces they should not have access to, the access configuration for that user or workspace may not be set up correctly.

What to do: Review the workspace permissions and audience-based access settings for the affected user and the workspaces in question. Adjust the access configuration so that only the intended workspaces are visible to that user. If the issue persists after updating the configuration, raise a support request.

Only some channels are visible after selecting a workspace.

What happened: Channel visibility is limited to channels within the selected workspace that the logged-in user is permitted to access. Channels from workspaces the user cannot access are not shown, and some channels within an accessible workspace may also be restricted based on permissions.

What to do: Confirm that the expected channels are available within the selected workspace and that the logged-in user has the necessary permissions to access them. If channels that should be visible are missing, review the channel-level access settings for that workspace.

Frequently asked questions

Will the experience change if I only have one connected workspace? No. If you only have one eligible connected workspace for Slack or Microsoft Teams, the experience stays simple and no extra picker is shown.

Can two users in the same organization see different workspace options? Yes. Workspace visibility depends on each user's audience-based and workspace-based access, so two users may see different available workspaces and channels.

What happens if I do not have access to any eligible workspace? If you do not have access to an eligible tenant-level connection, the sharing option may be hidden, disabled, or unavailable in the newsletter flow.

Does this work for both Slack and Microsoft Teams? Yes. This feature supports multi-instance workspace selection for both Slack and Microsoft Teams in newsletter experiences.