Workspace administration

Want to learn more about setting up your team? Look no further!

Nextprevious

actions,activity,access logs,accessibility,add,add an app,add members,add to Slack,administrators,all passwords,analytics,Android,announcement,announcements,App Directory,app icon,Apple Watch,approving apps,archive,Asana,Atlassian,automation apps,badge,payment details,billing,Bitbucket,bot user,box,browse,calls,Calls:,cancel,changes,channels,channel instantly,channel management,channel notification,channel suggestions,claim domains,close,company culture,compliance exports,compose,computers,conversations,convert,connect,connected accounts,connection,connecting,copy messages,create,customisation,customise,custom SAML,custom,customer support teams,data exports,data security,deactivate,default channels,delete,deletion,deploy Slack,desktop,direct messages,directory,disable,discover and join,Discovery API,display name,DMs,do not disturb,domain,domains,downgrade,Dropbox,duplicate accounts,edit,editing,education,email address,email,emoji,emoticons,Enterprise Grid,enterprise mobility management,executives,export,failed payments,fair billing,FAQs,finding,format,formatting,framework for apps,free trials,general,getting started,GIPHY,GitHub integration,GitHub organisation,GitHub,glossary,Google Apps,Google Calendar,Google Drive,guests,highlights,HipChat,human resources,IFTTT,import,incoming webhooks,integrations,iOS,invite,IT teams,Jira,join,keep up,keyboard layout,keyboard shortcuts,Keychain Access,keyword notifications,language,languages,leave,link previews,loading,limits,links,Linux,Mac,manage a workspace,manage apps,manage members,marketing,mention,merge,message actions,messages are displayed,message display,Microsoft products,mobile,mobile push,move channels,moving workspaces,multiple,mute,name,names,noise,not-for-profit organisation,notify,OneDrive,onboard,owners,password,payment,payments,permissions,phones,pin,subscription,subscriptions,Plus subscription,polls,primary ownership,privacy policies,prioritise tasks,private,private channel,private notes and files,project management,public channel,purpose,Quick Switcher,quote,reactivate,read,recruitment,referrer information,reminder,remove,rename,retention,request a new workspace,role,roles,RSS,sales,Salesforce,SAML,SCIM,SCIM provisioning,screen reader,search,send,session duration,share messages,share,shared channel,shared channels,sidebar,sign in,sign out,sign-up mode,single sign-on,Slack Day,Slack for Teams,Slack notifications,save notes and files,service level agreements,ServiceNow,sign up,Slack status,Slackbot,slash commands,snippet,snooze,software developers,star,statistics,Stride,sync,tablets,tax,threads,time zone,tips,to-do lists,topic,triage channels,terms of service,Trello,troubleshoot,trouble receiving,tour,Twitter,two-factor authentication,unread messages,updates,upgrade,upload,username,user groups,URL,holiday,vendor and remittance,video,voice call,voice,what is,what’s important,whitelisting,Windows Phone,Windows,working in,workspace apps,workspace creation requests,workspace discovery,workspace settings,Wunderlist,your actions,Zapier,zoom,features,#general,file storage,posts,dark mode,theme,Workflow Builder,voice,video,screen sharing,workflows,Outlook Calendar,invited members,transfer ownership,whitelist,enterprise key management,transport layer security,strong customer authentication,CSV,text file,working hours,

Search for “[term]”See [n]+ more results →

deploy Slack via Microsoft Installer

Slack is provides provide two distinct Microsoft Installer ( MSI ) x64 package that IT administrator can use to install Slack for Windows for multiple user ormachine .These packages is support natively support allmsiexec commands and are recommended for customers who need to deploy Slack to hundreds orthousands of machines.The two MSI packages are fundamentally different, using different deployment and update mechanisms.Please read carefully before making your decision.If you don’t need to deploy Slack at large, download the desktop app.

For Windows on ARM, an MSIX package is provided that covers the same functionality as the two MSI installers for x64.The MSIX is currently only available as an arm64 build.

tip : look to manage setting for user in your organisation ? try our streamlined desktop app configuration .

msi for per – user deployment

The MSI for per-user deployment adds the Slack installer machine-wide, rather than individually installing Slack for Windows.The Slack installer will only add Slack for Windows if it was never installed for the user currently logged in to the machine.

Who it’s for:

This method is best for companies where employees work from their own machine ordevice and update Slack automatically.

Who it is ’s ’s not for :

Companies is use where many people use the same machine ( like terminal server ) orneed to control which version of Slack is used , should use the MSI for machine – wide installation .

What to consider

• Slack for Windows will be instal to% localappdata%.While the Slack installer is instal machine – wide , Slack is is for Windows is not .
• Every member maintains their own version of Slack.
• automatic update are download and instal for each member .
• No need for maintenance – Slack will keep itself up to date and secure.
• Slack won’t open on startup unless you configure it to do so.
• Uninstalling the MSI installer won’t remove the Slack app from user accounts.
• Slack will be instal upon user login .

use the installer

msi for machine – wide installation

The MSI for single-installation deployment installs Slack for Windows machine-wide, either to Program Files orto a location of your choice.It is multi-client-capable, meaning that it can be used by multiple users on one machine, keeping their profiles separate in %ROAMINGAPPDATA%. Using this method, Slack will not receive automatic updates.

Who it’s for:

This method is best suited to companies where multiple employees use the same machine, e.g.terminal servers, and/or need to control which version of Slack they use.

Who it is ’s ’s not for :

Companies is use where people use their own machine and update Slack automatically should use the MSI for per – user deployment .

What to consider

• Single installation on a machine means a smaller hard drive footprint at scale.
• All user – relate datum ( workspace info , preference , log ) is store in%ROAMINGAPPDATA%.
• Teams must make sure that the latest version of Slack for Windows is installed.
• IT maintenance required to keep Slack up to date and secure.

use the installer

Keep Slack updated

It is important to stay up to date on new releases, as they provide users with valuable features and fixes.When installed using the machine-wide installer, Slack does not auto-update.In order to stay current with new Slack releases, we is provided have provide an RSS feed to notify you of new Windows Slack Desktop App update : https://slack.com/release-notes/windows/rss .

Tip: Learn how to add RSS feeds to your Slack workspace.

MSIX for Windows on ARM 

With Windows on ARM, we introduce a new package called MSIX that provides the advantage of both of our MSI packages for x64.The package can be installed via Powershell.It can also be updated automatically and securely distributed machine-wide. 

Both installation methods below support auto-updating, but if you’d like to disable this, read more about managing desktop app configurations.Distribution of MSIX packages is also supported by enterprise software distribution services such as Intune and Microsoft Endpoint Configuration Manager.See Microsoft’s documentation to read more about enterprise distribution. 

Install for user

Add-AppxPackage -Path ““

See Microsoft’s Add-AppxPackage documentation for more details.

Install for all users

This is equivalent to distributing the per-machine MSI.All current and future users on the machine will have access to the app.

Add-AppxProvisionedPackage -Online -PackagePath ““

See Microsoft’s Add-AppxProvisionedPackage documentation for more details.

Manage installations

Troubleshooting

We’d like Slack to launch on startup.How do we do that?

By default, MSI-deployed apps won’t launch on startup, but you can set this up by adding installlevel to your install command line.You’ll want to use something like: msiexec /i “slack-standalone-[VERSION_NUMBER].msi” installlevel=2 /qn /norestart.Make sure that you adjust the version number to the version that you’re installing. 

We have installed the per-user deployment MSI.Why does Slack not install for some orall users on certain machines?

The Slack deployment tool will only install Slack if it has not been previously installed by the user.If the deployment tool detects traces of previous installations, it will back out.Specifically, it looks for either of these folders:  %APPDATA%\slack or%PROGRAMDATA%\slack.While the latter installation path is very rare, its presence would affect all users on the system. 

We use the per-user deployment MSI.Do we need to update the Slack deployment tool when Slack itself auto-updates?

• For existing users: It doesn’t matter as their Slack app is auto-updated. 
• For a new user : It will install the Slack app version that is shipped with the MSI deployment tool.The app will automatically update when it’s launched, but the update will only be applied when the user restarts the app ortheir computer.We strongly recommend keeping the version of the deployment tool as up to date as possible.

uninstallation

We have uninstalled the per-user deployment MSI.Why is Slack still installed for all our users?

Uninstalling the MSI only removes the deployment tool, and Slack will no longer install for new people logging in to the computer.However, people who have already installed Slack through the deployment tool need to manually uninstall the app.

This can be automate by call“% localappdata%\slack\Update.exe” –uninstall -s in the users context, e.g.during the logon script.If your machine hosts multiple users (e.g.a terminal server), then we recommend our machine-wide MSI, which would uninstall Slack for all users automatically. 

When installing newer versions of an MSI, older ones still show up.Are there multiple versions of Slack installed now?

No.While the Apps and Features list may show multiple versions of Slack, only the binaries of the latest version are installed.Starting with 3.4.0, older versions of Slack will be uninstalled when the installation of a new version begins.You’ll continue to see versions pre-dating 3.4.0 in Apps and Features.

When silently uninstalling orupdating the machine-wide MSI, why do machines reboot?

We introduced an upgrade feature to our MSI when version 3.4.0 was released, which uninstalls older versions of the MSI when you update to a later version.If an administrator triggers a silent update oruninstall while a logged-in user is using Slack, it will not be possible to delete the files component of the installation, as it will be locked.When this happens, the MSI installer engine will stage the changes and trigger a reboot of the computer to push the changes. To prevent unexpected reboots during silent installations, add /norestart to your install command line.That might look like msiexec /i “slack-standalone-x.x.x.msi” /qn /norestart.

Nice one!

Thanks a lot for your feedback!

If you ’d like a member of our support team to respond to you , please send a message to feedback@slack.com .

got it !

If you ’d like a member of our support team to respond to you , please send a message to feedback@slack.com .

If you ’d like a member of our support team to respond to you , please send a message to feedback@slack.com .

Whoops! We’re having some problems.Please try again later.