Why use a desktop client?
A dedicated application can keep work conversations in a separate window and may integrate with operating-system notifications. The exact features depend on the provider and the installed version. A browser may be simpler if you use a shared machine or switch computers often.
Before installation
Check the supported operating-system version, processor architecture, update policy, and disk-space requirements published by the provider. Company computers may use centrally managed software; installing a second copy outside that process can create update or support problems.
Keep the app maintainable
Use the approved update method and restart when required. If notifications stop, check both the application preferences and the operating system’s focus or notification settings. Do not assume an app problem until you have checked account, network, and workspace access.
A useful desktop-client test
After the approved installation, open the correct workspace, send a low-stakes test message if appropriate, and verify whether an expected notification appears. Then check a link to a shared document and confirm that it opens in the intended account. If notifications are absent, compare the application’s settings with the operating system’s permissions and focus mode. Record the client version and the failing step before asking support for help.
Choose the next step
| Situation | What to check |
|---|---|
| App launches but access fails | Check identity and workspace membership. |
| Messages appear without alerts | Review app, OS, and focus settings. |
| An update is blocked | Use the managed update route or contact IT. |
A practical checklist
- Confirm a desktop client is available for your device.
- Install through the approved channel.
- Check operating-system and in-app notifications.
- Keep the client updated under your organization’s policy.