-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUERY] Warning about External Teams #323
Comments
Hmm, odd, that remediation text certainly needs some work. To make sure I understand the situation: what are the first and second steps you are using in |
And now for your context: "External teams" implies usage of Slack Connect channels, channels that are shared/connected between multiple different workspaces (possibly from outside your organization). There are workspace/organization administrator settings that enable admins to restrict specific workflow steps from being used by 'external teams' - that is, users from workspaces that are not part of your workspace but that are members of these shared channels. |
@filmaj As an example here are the steps for Step One retrieves some data from a CRM and Step Two runs a modal function |
Generally though it sounds like the warning is not critical for us as we don't need any external users to use the workflow steps. Can I safely ignore it? |
Correct, if the command didn't error out, it is just informing you "hey users that are not members of the workspace this app was installed to will be unable to use this workflow." Let me follow up on the exact settings that are mentioned here so that you have the relevant info, and then we'll discuss with the team how to clarify the warning message raised by the CLI in this case. |
OK, found the info: https://slack.com/help/articles/14844871922195-Slack-administration--Manage-workflow-usage-in-Slack-Connect-conversations#enterprise-grid-1 The relevant bits are:
I'm going to keep this issue open until we figure out a better way of communicating this situation in the CLI warning repsonse. |
I started seeing the same thing within the last two days (may have been when I updated the CLI/deno-sdk from This was their response:
As @filmaj stated, this does not affect running the app; it is just a warning. In large organizations such as mine, this is a problem, but I will work through it in other channels/methods. |
I am also seeing these warnings for all 130+ steps in our app, so it's very noisy and takes a full year to scroll through 😅 Is there a way to silence these warnings for the time being? Maybe using a cli flag? |
FYI today's CLI release (v2.25.0) should somewhat address, at least, how much real estate these warnings take up by grouping the same warnings together. After speaking to different teams internally at Slack, we decided to have the underlying App Manifest APIs that return this warning maintain the warning, as it is contextually relevant for teams and this warning also shows up in Workflow Builder if you build a workflow that way. We are also debating maybe limiting the number of warnings that end up being displayed (to, say, 5) in an effort to further declutter the CLI's output. |
@filmaj I've just started getting warnings about external teams when running an app:
It says the remedy is to "remove external teams in Settings" but I don't know what is meant by "Settings" - there seems to be nothing in the app referring to external teams.
Could you help please?
The text was updated successfully, but these errors were encountered: