Overview of Atlassian Cloud - dedicated model
SHIP-HATS offers Atlassian Cloud in two models to meet the varying needs of government agencies:
Shared model – suitable for most agencies with standard requirements
Dedicated model – designed for agencies with advanced or specialised needs
While the Shared model provides a centrally managed environment with standard configurations and plugins, some agencies may need greater control, flexibility, or access to features not supported in a shared setup. For such cases, SHIP-HATS now offers the Dedicated model, which provides agencies with their own Atlassian Cloud site and full administrative rights.
This document explains the dedicated model, its benefits, use cases, and key responsibilities.
Benefits of Atlassian dedicated model
Enables agencies that were previously unable to onboard Atlassian (Jira, Confluence and JSM) via the Shared model to onboard and make use of Atlassian tools.
Centralised identity management enhances user visibility, usage tracking, and transparency.
Addresses flexibility gaps that the Shared model cannot address.
Drives Whole-of-Government (WOG) cost savings through bulk licensing and procurement.
Use cases for Atlassian Cloud - dedicated model
The default recommendation remains the “Shared” site. Dedicated sites are reserved for scenarios where the Shared model is insufficient. Use the table below to assess when a Dedicated site may be needed.
| Use case | What it solves | Why shared model doesn’t work | How dedicated model helps |
|---|---|---|---|
| Granular site control | Need to configure site-level settings like creating global templates. | Shared model enforces generalised site-wide policies which may not be suitable for certain teams with specialised needs. | Site admins have full control over site settings, including the option to enable creation of global templates. |
| Plugin flexibility | Need for specific plugins that are essential for certain agency workflows or integrations. | Shared model has a fixed set of centrally managed plugins. Agencies may request additional plugins, but approval is subject to considerations such as security, suitability, and cost implications—especially due to the scale of the shared environment. | Agencies can manage their own plugins. |
| Hybrid flexibility with central alignment | Provides the flexibility to customise while staying aligned with SG Tech Stack’s IDP and SHIP-HATS procurement/onboarding. | Running a fully self-managed setup would lose central integration, requiring manual identity, procurement, and onboarding management. | Dedicated sites still integrate with SG Tech Stack’s IDP and benefit from SHIP-HATS-managed procurement and onboarding. |
What’s included in Atlassian Cloud - dedicated model?
Dedicated site with site admin rights: Agencies receive their own Atlassian Cloud site, granting full administrative control over settings, plugins, and user management.
App options: You can choose to include apps such as Jira, Confluence and Jira Service Management (JSM) in your Dedicated site, as required.
Before adding users to your Dedicated site, ensure they have the necessary licenses for Jira, Confluence, and/or Jira Service Management (JSM)—based on the apps you’ve included in your site.
When to use a dedicated site
A dedicated site is recommended when your agency requires:
- Greater control over site configuration and settings
- Flexibility to install and manage plugins
- Custom workflows or configurations not supported in the shared environment
