Ownership and responsibilities
Atlassian Dedicated Sites provide agencies with greater control over their environment. With this flexibility comes increased responsibility for managing configuration, security, and usage.
This topic outlines the responsibilities of site owners (Subscription Admins and Project Admins) and the SHIP-HATS team.
Responsibility matrix
Legend
✅ Responsible / Provided
🟨 Limited support (best effort)
❌ Not responsible
| Responsibility | Site owner / Site administrators | SHIP-HATS |
|---|---|---|
| Initial configuration | – | ✅ Provides baseline configuration aligned with the Shared model ❌ Plugins are not installed by default |
| Configuration changes | ✅ Responsible for assessing risks, implementing changes, and ensuring compliance | ❌ Not responsible for changes made after provisioning |
| Security posture | ✅ Responsible for maintaining security and handling incidents caused by misconfiguration or user actions | 🟨 May assist in identifying issues or coordinating with Atlassian ❌ Not responsible for user-caused issues |
| Monitoring & usage | ✅ Responsible for monitoring usage, performance, and user behaviour | ❌ Not responsible |
| Performance issues | ✅ Responsible for identifying and investigating issues caused by usage or configuration | 🟨 Can escalate platform-related issues to Atlassian |
| Plugin management | ✅ Responsible for installing plugins and ensuring required security approvals | ❌ Not responsible |
| Atlassian support | 🟨 May engage Atlassian support directly and manage requests | 🟨 May facilitate support where applicable |
| Data loss & recovery | ✅ Responsible for recovery and engaging Atlassian where needed | 🟨 May assist on a best-effort basis |
Key considerations
- A dedicated site gives agencies full administrative control, including configuration and plugin management.
- Agencies are accountable for security, compliance, and operational risks within their site.
- SHIP-HATS provides the platform and initial setup, but does not manage ongoing configurations.
