Salesforce Salesforce-Slack-Administrator Exam With Confidence Using Practice Dumps

In Enterprise Grid, if auto-provisioning is enabled via an IdP group, when a member is added to that group, they are automatically provisioned to the specified workspace. According to Slack’s official Enterprise Grid documentation:

"When a member is added to an IdP group that’s mapped to a workspace, they will be automatically provisioned (added) to the workspace, unless the workspace is set as hidden."

Hidden workspaces require an invitation or manual addition and are excluded from automatic group provisioning. Therefore, unless the workspace is hidden, members will automatically join it without needing to take any manual action.

(Reference: Slack Administration Study Guide - Enterprise Grid Configuration and IdP Group Management)

To automatically manage user deactivation:

"If your Identity Provider supports SCIM provisioning, and it is correctly configured with Slack, user deactivation in the IdP will trigger automatic deactivation of the user's Slack account."

SCIM ensures seamless deprovisioning. Just-in-Time deactivations (D) are not a Slack feature, and changing the email manually (A) is not secure or scalable.

(Reference: Slack Administration Study Guide - User Deprovisioning with SCIM)

Slack’s best practices for promoting open communication are:

"Keep everything in public channels for transparency and collaboration. Set public channel message retention to 'Keep Everything' and restrict DM retention to minimize private, siloed communication."

Also:

"Allow everyone to create channels to lower barriers to collaboration and prevent bottlenecks."

Restricting channel creation (Option C) would hinder users and reinforce the DM reliance problem.

(Reference: Slack Administration Study Guide - Messaging and Retention Policies)

===========

—