Cert++
  1. Home
  3. Slack Administrator

Slack Administrator

Checklist progressProgress

0/238Learned

Slack Administrator Study Checklist
  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect
  • Slack Administrator

Checklist progressProgress

0/238Learned

  • Public, private and multi-workspace channels for a collaboration need
  • Announcement-only, org-wide and default channels for broadcasting
  • Slack Connect channels versus guest accounts for external collaboration
  • User groups versus channel-wide mentions for reaching a team
  • Huddles versus audio and video clips for team communication
  • Canvases versus lists for organizing team information
  • Slack lists with forms and automations for tracking requests
  • When Workflow Builder fits a repeatable process requirement
  • Slack templates for setting up purpose-built channels
  • Slack AI features matched to a productivity need
  • Changing a person between guest and member account types
  • Invited members before account activation
  • Channel Manager versus Workspace Admin for channel-level delegation
  • Operational system roles and custom roles for targeted delegation
  • Compliance and security system roles for governance delegates
  • Canvas and list access levels for members, guests and external people
  • Limited sharing for canvases and lists
  • Workspace Owner versus Workspace Admin responsibilities
  • Owner and admin tasks versus default member and guest permissions
  • Workspace Primary Owner exclusive powers
  • Choosing the right Primary Owner and admin account practices
  • Org-level versus workspace-level administration on Enterprise Grid
  • Org Admin responsibilities on Enterprise Grid
  • Org Owner versus Org Admin responsibilities
  • Org Primary Owner exclusive capabilities
  • Promoting and demoting owner and admin roles
  • Routine admin upkeep and admin request intake
  • Free versus Pro plan for a growing team
  • Workflow and app automation needs by plan
  • When Business+ is the right choice over Pro
  • SAML SSO and SCIM provisioning availability by plan
  • Enterprise Grid versus a single-workspace plan
  • Compliance and security requirements that call for Enterprise+
  • GovSlack for government compliance requirements
  • Multi-workspace membership versus multi-workspace channels on Enterprise Grid
  • Member invitations, invitation approval and email-domain sign-up
  • Enterprise Grid workspace access levels and join requests
  • Methods for adding existing org members to a workspace
  • Default channel behavior for new workspace members
  • Org-wide default channels versus workspace-level default channels
  • User group default channels for adding many people to channels
  • Outcomes of deactivating and reactivating a member account
  • Deactivation rights by owner and admin role on Free, Pro and Business+ plans
  • Deactivation rights for Org Admins, Org Owners and the Org Primary Owner
  • Org-level deactivation versus workspace removal in Enterprise Grid
  • Delegating account deactivation through system roles
  • Primary Owner offboarding and ownership transfer before deactivation
  • Deprovisioning accounts through SCIM and the identity provider
  • Slack-credential sign-in versus SAML SSO across Slack plans
  • Workspace-level versus Enterprise Grid org-level SSO configuration
  • SSO enforcement options for members and guests
  • Two-factor authentication and session duration as added access controls
  • Required SAML attributes and account matching when switching identity providers
  • Just-in-Time versus SCIM provisioning for new accounts
  • SCIM provisioning availability and capabilities by Slack plan
  • Identity provider as source of truth for display names and email addresses
  • Workspace Primary Owner, Owner and Admin role boundaries
  • Org-level versus workspace-level administrative roles on Enterprise Grid
  • Owner-adjustable default permissions for members
  • System role and custom role availability by Slack plan
  • System role selection for a delegated admin duty
  • System role delegation versus promotion to a full admin role
  • Channel Managers versus the Channels Admin system role
  • Connecting IdP groups to workspaces in an Enterprise Grid org
  • Required versus optional workspace membership for IdP groups
  • Connecting IdP groups to channels for automatic membership
  • IdP as the source of truth for IdP group membership changes
  • Disconnecting an IdP group from a workspace or channel
  • Single-Channel Guest, Multi-Channel Guest or full member
  • Guest permissions compared with full members
  • Guest channel access management by admins and members
  • Guest account time limits and automatic deactivation
  • Inviting a new guest versus converting an existing member to a guest
  • SCIM provisioning of guest accounts by Slack plan
  • Managing external people's channel access in Slack Connect
  • Workspace-level versus org-level user group scope
  • Permission to create and edit user groups at org and workspace level
  • Org-level user groups for workspace membership and channel access
  • Admin-created org user groups versus IdP and SCIM-managed groups
  • User group eligibility for guests and Slack Connect external people
  • User group deactivation and mention visibility
  • Channel naming conventions and channel strategy
  • Channel management tools at the org level versus the workspace level
  • Channel Manager role capabilities and assignment
  • Delegating access to channel management tools and private channels
  • Permissions dashboard controls for channel actions by role
  • Channel posting permissions for announcement and multi-workspace channels
  • Channel activity data and CSV export for channel cleanup
  • Adding, removing and org-wide sharing of multi-workspace channels
  • Delegating the multi-workspace channel management permission
  • Moving a channel between workspaces versus sharing it across workspaces
  • Org-level versus workspace-level placement of a member-wide setting
  • Default feature access by role versus owner-changed defaults
  • Org-level permission overrides and workspace edit delegation
  • Joining, join requests and leaving workspaces in an Enterprise org
  • Multi-workspace channels versus new workspaces for cross-team access
  • Plan requirements and organization limits for Slack Connect
  • Slack Connect invitation types and external member permissions
  • Slack Connect channel ownership and adding organizations
  • Enabling Slack Connect for specific workspaces in Enterprise Grid
  • Controlling who can send Slack Connect channel invitations
  • Slack Connect invitation approval and invitation requests
  • Controlling who can join channels owned by other organizations
  • Per-organization Slack Connect settings and connection management
  • Slack Connect security and visibility settings
  • Removing external people versus removing or disconnecting an organization

Given a scenario, determine how to implement Slack AI

0/12

  • Slack AI feature availability by plan
  • Slack AI and member access to private channels and DMs
  • Slack AI data handling and LLM training
  • Turning individual Slack AI features on or off
  • Scoping AI feature access to specific people and groups
  • Additional settings for individual AI features
  • Future AI feature releases setting
  • Content safety filter settings for Slack AI
  • Restricting AI access in sensitive channels, canvases and lists
  • Retention of AI-generated summaries, answers and recaps
  • AI search answers versus enterprise search
  • AI steps and AI-built workflows in Workflow Builder

Assess a given scenario to determine how to manage app installation and approvals

0/23

  • App management features by Slack plan
  • Roles that manage apps at org and workspace levels
  • Enabling app approval for a single workspace
  • Pre-approving versus restricting apps
  • Member app requests and request notification routing
  • Appointing app managers to review app requests
  • Reviewing and resolving pending app requests
  • App approval policy review criteria
  • Controlling which members and channels can use an installed app
  • Marketplace-only installs, guest app use and link preview settings
  • Sign in with Slack permissions for third-party services
  • Org-level app management policy versus workspace app approval
  • Approving and restricting apps at the org level
  • Installing apps at the org level and adding them to workspaces
  • Building app approval automation rules
  • Choosing a resolution for app approval automation rules
  • Automation rule order, activation and removal
  • Admin API app versus UI tools for org-wide app approvals
  • App approval for Workflow Builder connector steps and workflow apps
  • Salesforce channels and record access in Slack
  • Auditing installed apps across an Enterprise Grid org
  • Recommended secure baseline for app management settings
  • Choosing an app governance decision model for an Enterprise Grid org

Given a scenario, evaluate the app scopes for compliance to security policies

0/11

Accessible data versus allowed actions in app permission review

Learn this concept
Unseen

Apps acting on behalf of a user versus acting as the app

Learn this concept
Unseen

Reviewing app permissions before and after installation

Learn this concept
Unseen

Least-privilege review of requested scopes against an app's purpose

Learn this concept
Unseen

Rating scopes by risk level for app approval

Learn this concept
Unseen

Security vetting of Marketplace apps and internal integrations

Learn this concept
Unseen

Approving optional scopes when reviewing app requests

Learn this concept
Unseen

App scope change requests after installation

Learn this concept
Unseen

Legacy bot scope versus granular bot scopes

Learn this concept
Unseen

Scopes requested versus scopes resolved as automation rule components

Learn this concept
Unseen

Third-party AI agent apps versus native Slack AI controls

Learn this concept
Unseen
  • Org-level policies versus workspace-level settings on Enterprise Grid
  • Mandatory two-factor authentication for members
  • Session duration and forced sign-out controls
  • Workspace access controls for invitations, domain signup and departures
  • Message editing and deletion permission policies
  • Security controls for external collaboration via Slack Connect and guests
  • App installation restrictions and app governance approach
  • Message retention policy options and revision tracking
  • Retention levels and conversation-level retention overrides
  • File retention versus message retention
  • Retention in multi-workspace and Slack Connect channels
  • Archiving versus deleting channels to preserve message history
  • Legal holds to preserve a specific member's message history
  • Native Slack export types by plan
  • Single-user data export in Enterprise Grid
  • Discovery API enablement, access and data coverage
  • Native exports versus the Discovery API for compliance needs
  • eDiscovery apps versus DLP apps with the Discovery API
  • Retention effects on native exports and eDiscovery archives
  • Slack support for regulated-industry compliance standards
  • Viewing, filtering and exporting Enterprise Grid audit logs
  • System roles for audit log access and security monitoring
  • Audit Logs API for SIEM integration and continuous monitoring
  • Investigating anomaly events on the Security Detections tab
  • Automatic anomaly event responses that end user sessions
  • Search query log exports for security investigations
  • Audit logs versus DLP, Discovery API and exports for a security concern
  • Slack DLP rules for detecting personal data
  • DLP rule actions for content that violates a rule
  • DLP Admin system role and access to flagged data
  • Reviewing and resolving alerts in the DLP dashboard
  • Content types outside Slack DLP scanning
  • Native Slack DLP versus third-party DLP through the Discovery API
  • Email address display in member profiles
  • Slack Connect discoverability and contact sharing preferences
  • Data residency for regional storage of personal data
  • Business scenarios that call for a workspace migration into Enterprise Grid
  • Workspace migration versus other consolidation methods
  • Migrating an existing workspace when launching a new Enterprise org
  • Initiating, approving and cancelling a migration request
  • Identity and SSO preparation before migrating a workspace
  • Resolving user account and settings conflicts in the migration checklist
  • Migration phases, downtime and member communication planning
  • Org-level versus workspace-level data after a grid migration
  • Data that does not carry over automatically in a migration
  • Post-migration effects on settings, access and Slack Connect channels
  • Content Admin system role for conversation moderation
  • Pausing versus hiding a harmful message thread
  • Member content flagging and admin review of flagged content
  • Proactive thread moderation versus member flagging versus DLP rules
  • Handling conduct violations by external Slack Connect participants
  • Active people versus people posting metrics
  • Total versus claimed members and nudging pending members
  • Public, private and direct message distribution as an engagement signal
  • Members tab metrics for tracking individual activity
  • Channel analytics for trending and inactive channels
  • Message activity analytics for announcement reach
  • Message activity eligibility and the Message Activity Manager role
  • Org-level versus workspace-level analytics in Enterprise Grid
  • Tracking huddle, app, workflow and Slack Connect adoption org-wide
  • Monitoring Slack AI and Slackbot feature usage
  • Department-level adoption views with SCIM profile fields
  • Controlling who can view the analytics dashboard
  • Org-wide controls for member metrics and private channel analytics
  • Choosing an analytics source by plan and monitoring need
  • Matching adoption metrics to business goals
  • Sentiment surveys and feedback loops after a Slack launch
  • Diagnosing adoption barriers and slow-adopting teams
  • Remedies for training gaps surfaced by user feedback
  • Channel findability and search usability complaints
  • Translating a Slack vision and business goals into Slack behaviors
  • Rollout ground rules: process scoping and public-by-default channels
  • Reinforcing the why with high-interest Slack use cases
  • Slack-first channel and workflow plans for a line of business
  • Lists and canvases versus channels for project team needs
  • Workflow Builder use cases matched to team processes
  • Workflow triggers for a business unit process
  • Workflow steps and connectors for team processes
  • Conditional branching in Workflow Builder
  • Workflow Builder access controls for business unit builders
  • Champions versus executive sponsors, managers and other adoption roles
  • Champion selection criteria beyond technical proficiency
  • Identifying champion candidates with member analytics
  • Champion network coverage and sizing across the organization
  • Champion-led enablement activities that sustain adoption
  • Champion involvement before, during and after a Slack rollout

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Slack Administrator studiers. 662 members and growing.

Go to Discord
  1. Slack Administrator Checklist
  3. App and AI Administration and Automations

Apps acting on behalf of a user versus acting as the app

Explainer

Learn More

Practice Question

Keep going

Next conceptReviewing app permissions before and after installation

Checklist progress

0/238 (0%)

0 of 238 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Slack Administrator studiers. 662 members and growing.

Go to Discord
Close
  1. Slack Administrator Checklist
  3. App and AI Administration and Automations
Apps acting on behalf of a user versus acting as the app

Explainer

Learn More

Practice Question

Keep going

Next conceptReviewing app permissions before and after installation

Explainer

Every Slack app asks for permission scopes, which define what information the app can see and what it can do. Some permissions let an app act on behalf of the person using it, and others let the app act on its own, as the app. Admins use this distinction to decide whether an app fits the organization's security policy.
Core information
  • Scopes are an app's permissions. Each app has its own set, and the scopes tell you what information the app can access in Slack and how it can use that information.
More details and nuances
  • Some apps create bot users. A bot can access the same information as workspace members, and it may be able to take the same actions that members can.

Explainer

Every Slack app asks for permission scopes, which define what information the app can see and what it can do. Some permissions let an app act on behalf of the person using it, and others let the app act on its own, as the app. Admins use this distinction to decide whether an app fits the organization's security policy.
Core information
  • Scopes are an app's permissions. Each app has its own set, and the scopes tell you what information the app can access in Slack and how it can use that information.
More details and nuances
  • Some apps create bot users. A bot can access the same information as workspace members, and it may be able to take the same actions that members can.