Slack cloud
Fair 1.3 Easy 4.7 Secure 3.0
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 5 | Almost no training needed. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 5 | Salesforce operates it. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 4 | Many integrations; SSO on paid tiers. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 2 | Paid export exists; history and apps do not move cleanly. Source |
| Fair | Sovereignty EU legal entity, EU hosting, and exposure to extra-EU lawful access? | 1 | US vendor (Salesforce); EU residency is limited. Source |
| Fair | Openness Open source or open standards? Are independent implementations possible? | 1 | Closed source; proprietary clients and APIs. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 4 | Enterprise security features on higher plans. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 3 | 2FA exists; workspace spam and phishing links are common. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 2 | US processor; DPA does not remove CLOUD Act risk. Source |