Topic
Document security and compliance
Data sovereignty, access control and the compliance questions teams ask before migrating.
Compliance is not a certificate you buy. It is a set of controls you can describe, evidence and hand to an auditor — residency, access, retention, encryption and the audit trail behind them.
14 articles4 documentation guides
All 14 articles
- September 2026A Zero-Knowledge Editor Is Not a Document Suite
- September 2026Answering a Security Review of a Self-Hosted Platform
- August 2026Secure Cloud Collaboration: Balancing Security and Productivity
- March 2026Document Encryption and Key Custody
- March 2026External Document Sharing: Where Audits Find Problems
- March 2026Access Control for Document Platforms
- March 2026Legal Hold in Document Platforms
- March 2026Building a Document Retention Policy That Holds
- March 2026A Practical Guide to Data Residency Requirements
- March 2026ISO 27001 and Document Management
- March 2026SOC 2 Controls for Document Collaboration
- March 2026HIPAA-Compliant Document Collaboration
- February 2026GDPR-Compliant Document Collaboration
- January 2026Data Sovereignty in Document Collaboration
From the documentation
The runbooks behind these articles: installation, sizing, configuration, and the checks worth running before a rollout reaches real work.
- Audit LogOperation logs are used to view and track user management operations in the system, helping with troubleshooting, security audits, and change tracking.
- System RequirementsSupported server resources, network access and deployment prerequisites for installing OfficeDocs Suite in your own private cloud infrastructure.
- Data BackupValidate backup targets and back up the databases, object storage and configuration of a self-hosted OfficeDocs Suite deployment before you need a restore.
- Suite User ManagementUser management is used to view users in each tenant of OfficeDocs Suite and to enable or disable user accounts in bulk.