Tenant Isolation & Data Security
Audience: Admin, Security, Compliance
Page Type: Concept
Summary: How COS separates workspace data, controls access via roles, and provides audit trails.
Workspace (tenant) basics
A workspace (sometimes called a tenant) is your company’s environment inside COS.
- Your users, org structure, OKRs, KPIs, dashboards, and audit logs belong to your workspace.
- Users in one workspace cannot view or edit data from another workspace.
What COS isolates
COS is designed so that data is separated per workspace, including:
- Users and roles
- Organization structure (units)
- Strategic cycles and OKR cycles
- Objectives, Key Results, initiatives
- KPIs and measurements
- Reports and dashboards
- Audit logs
Access control (roles & permissions)
Inside a workspace, COS uses roles & permissions to decide what each user can see and do.
COS authorization consists of 4 independent layers:
| Layer | Description |
|---|---|
| Platform | Super Admin — manages the entire system |
| Holding / Group | Group Admin — accesses business data across all companies in their group |
| Company (Tenant) | Admin, Strategy Manager, Member — company-level roles |
| Org Unit | Team Lead — leadership assignment in the org chart |
Typical examples:
- Some users can only update their own OKRs.
- Team leads can view and manage their unit's OKRs.
- Strategy Managers manage company-wide strategic cycles.
- Group Admins can view business data across all companies in their group.
- Admins can manage users, roles, and settings.
Important: A user can hold roles in multiple layers simultaneously. A Group Admin can also be an Admin within a specific company; both permissions apply independently.
See: Roles & Permissions
Audit logging
COS keeps an audit trail for important changes so admins can understand “who did what, when”.
Where to view it
- Admin → Audit Log
Typical use cases
- Investigate why an OKR changed
- Verify approvals and rejections
- Support compliance reporting
See: Viewing Audit Logs
Backups, retention, and exports
Backup and retention practices may vary by deployment and agreement.
- For backup/restore or retention confirmation, contact your COS administrator or support.
If you suspect a security issue
If a user reports seeing data that looks like it belongs to another company/workspace:
- Treat it as a security incident.
- Capture evidence (screenshots, user, time, steps).
- Contact support immediately.
Best practices
For Admins
- Assign Admin roles sparingly.
- Review Audit Log regularly.
- Remove access promptly for leavers.
For Users
- Use strong passwords.
- Don’t share credentials.
- Report suspicious access.