You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary
Currently, slack notifier is configured at server level. So for one deployment of guardian, there can only be one slack workspace configured using the access token.
But if there are users who are on different slack workspaces (which can happen in a huge organization), sending notification to only one workspace wouldn't work.
For example -
If the guardian server is set up with slack server - workspaceA, and there is only deployment of guardian in the org which has multiple slack workspaces - workspaceA, workspaceB, workspaceC, workspaceD, etc.
If a user who is only in workspaceB, raises an appeal - the notification for the appeal and access get sent to workspaceA, but since the user is not in workspaceA - the notification will error out and the user wouldn't receive any notifications.
The text was updated successfully, but these errors were encountered:
Summary
Currently, slack notifier is configured at server level. So for one deployment of guardian, there can only be one slack workspace configured using the access token.
But if there are users who are on different slack workspaces (which can happen in a huge organization), sending notification to only one workspace wouldn't work.
For example -
If the guardian server is set up with slack server -
workspaceA
, and there is only deployment of guardian in the org which has multiple slack workspaces -workspaceA
,workspaceB
,workspaceC
,workspaceD
, etc.If a user who is only in
workspaceB
, raises an appeal - the notification for the appeal and access get sent toworkspaceA
, but since the user is not inworkspaceA
- the notification will error out and the user wouldn't receive any notifications.The text was updated successfully, but these errors were encountered: