Salesforce Slack Administrator

Structure grows with the company. You plan how many workspaces an org needs, create and consolidate them, reorganize when the business changes, and keep channels and user groups tidy as teams move.

• Workspace design for an organization
• Creating a new workspace
• Consolidating several workspaces
• Reorganizing after a merger or reorg
• Managing channels and channel types
• Creating and managing user groups

You build A workspace plan that consolidates three workspaces and defines their channels.

People join, move and leave all the time. You connect Slack to an identity provider, provision and deprovision members automatically, and handle every stage from first sign-in to deactivation without leaving orphaned access.

• Single sign-on setup
• Provisioning members and groups
• Onboarding a new member
• Changing roles and access
• Deactivating and reactivating accounts
• Handing over ownership when someone leaves
• Guest access over time

You build A member lifecycle runbook, from sign-up through deactivation.

Good governance lets people work freely within clear limits. You set who may create channels, post and invite, decide retention rules, and choose settings that match how the organization wants to work.

• Who may create and manage channels
• Posting and invitation permissions
• Message and file retention
• Data export and its limits
• Writing a usage policy people read
• Keeping policy consistent across workspaces

You build A governance policy with its matching Slack settings.

Slack holds sensitive conversation. You protect data with session and device controls, read audit logs to answer questions, apply legal holds and exports where required, and decide how to control channels shared with other companies.

• Session length and device controls
• Data loss prevention concepts
• Reading audit logs
• Legal holds and eDiscovery exports
• Controlling Slack Connect
• Meeting a compliance requirement in settings

You build A security and compliance review of an org, with each gap and its fix.

Apps extend Slack, and each carries access. You decide which apps people may install, review the permissions they request, set up an approval route, and remove apps that no longer earn their place.

• App directory settings and restrictions
• Reading the scopes an app asks for
• Setting up an approval workflow
• Custom apps and internal integrations
• Reviewing and removing installed apps

You build An app approval process with a review checklist.

Routine requests can run themselves. You build workflows with triggers, steps and connections to other tools, decide who may build and publish them, and keep automations from becoming a governance blind spot.

• Triggers and steps in Workflow Builder
• Forms, approvals and messages
• Connecting workflows to other apps
• Permissions for who builds workflows
• Monitoring and retiring workflows

You build A request-and-approval workflow for a common internal process.

AI features read conversation, so rollout needs care. You decide who gets Slack AI and Slackbot, understand what data each can reach, control the connections to other tools, and explain the limits to the people using them.

• What Slack AI and Slackbot can do
• Turning features on for the right groups
• What data they can see and use
• Managing connections to other tools
• Explaining limits and safe use to members

You build A rollout plan for Slack AI with data access rules and member guidance.

A tool only helps if people use it well. You read usage analytics, plan a launch that brings teams on, find the groups that lag, and grow healthy habits through champions and clear guidance.

• Reading the analytics dashboard
• Measuring healthy adoption
• Planning a launch
• Champions and training
• Finding and helping lagging teams

You build A launch and adoption plan with the measures that will show if it works.

Pull the pieces into one plan. You design the structure, identity, policy, security and app governance for an organization, and write the routines that keep it running, so a new administrator could take over the next day.

• Reading an organization’s needs
• Designing structure and identity
• Setting policy, security and app governance
• Writing the routines that keep it running
• Handing the org to a new administrator

You build An administration handbook for one organization.