Workshop 2: Workspace Admin | Workspace Visibility Settings Flashcards
Open
Welcome Workspace for all members to access when they 1st join your org
Anyone at your org can view👀 & join the Workspace
Social Workspace where we have a Secret Santa channel & yearbook photos
Workspace for standard biz func or Dept such as Sales
Global Workspace for all members
By Request
any org member can see 👀& request to join the Workspace
Req Admin overhead to accept requests to join the Workspace
Workspace for which you want to control membership to interested members only
Invite Only
any org member can see 👀 or be added to the Workspace
Req an invitation or addition by an Admin to join the Workspace
Workspace for a known project, details which should be kept private
Hidden
Members cannot see the Workspace & must be added or invited to join
Workspace for complex, high-risk projects
Workspace for mergers or acquisitions
Which of the following Workspace mgt tasks cannot be accomplished via Slack API?
Create a Workspace/Send a confirmation mssg to the requestor of a
Workspace/Invite members to a Workspace/Set Users’ notification settings in the Workspace
Set Users’ notification settings in the Workspace
How can you prevent employees from using company email addresses to create new workspaces outside of your existing Slack Enterprise Grid org?
Approve co-owned Slack Workspace using an SSL proxy within your corp network
Set up SAML-based SSO for authentication
Contact Slack to add Enterprise Key Mgmt (EKM) to your Slack Enterprise Grid plan
Contact Slack to claim your company’s email domain(s) for Slack Enterp Grid org
Which of the following are not benefits of claiming domains for your Enterprise org? Select 2:
Streamline member requests for guests
Make your org’s connected Workspaces easier to find
Prevent people from creating unsanctioned Workspaces outside of your org
Allow people with email addresses in specific domains to join your org.
Allow Org Owners to restrict member usage on mobile devices.
Streamline member requests for guests
Allow Org Owners to restrict member usage on mobile devices.
As a Workspace Admin:
I’ve just received 2 new workspace requests.
1 is for an initiative called Q Preparedness and another is for a Romulan Trade Deal project.
I’m not going to just approve all requests.
I want to ensure that creating a workspace is the right decision for my org.
How would I gather information to best make that decision?
Design a process that ports member requests into a private multi-workspace channel.
Members are asked to provide info with each request.
What are my options for responding to a member’s request for a new workspace?
Approve or deny the request for a new workspace OR follow up with the requestor to understand if a multi-workspace channel is more appropriate.
a project that requires members from different workspaces to work together may be better served by a multi-workspace channel than by a new workspace.
What do I do? Let’s start with the request for Q Preparedness. What’s the first question I should look to answer in making my decision?
Is it a cross-functional project?
Q Preparedness is a cross-functional project with members in the Security and Legal departments.
Ok, so it looks like Q Preparedness is cross-functional. What is the next question I should look to answer in making my decision?
What is the expected scope of the project?
If the project is cross-functional, then you should ask the requester about the expected scope of the project. For Q Preparedness, the scope is small and simple.
The team wants to develop a few strategies for responding to the appearance of Q. How should I respond to their request?
Create a multi-workspace channel.
the project is cross-functional, but simple and small in scope. A multi-workspace channel would fit the needs of the team.
For the project that is cross-functional, large and complex in scope. What should I do?
Create a new workspace. B/c the project is large and complex, so you should create a new workspace. Once approved, the person who requested the new workspace will become the Workspace Owner and can invite members to join.
Your company is in the process of acquiring a competitor. Until the legal approvals are complete, no one in the organization should know of the pending acquisition, except for the legal and executive teams.
What would be the most secure method of setting up a workspace to handle this sensitive information with a closed group of individuals?
Create a pvt channel & Invite only those who are part of the merger
Set up a new hidden workspace so that any info related to the merger is kept secure
Create a group direct message to share files related to the restructuring processes resulting from this merger
Create an Invite-only Workspace w/ a description indicating that the contents of the Workspace are confidential
Set up a new hidden workspace so that any info related to the merger is kept secure