Manage plugins for Atlassian Dedicated Site
Agencies can install and manage plugins for their Atlassian Dedicated Site to extend the functionality of Jira, Confluence, or Jira Service Management (JSM).
Plugins (also known as apps) provide additional features and integrations for Atlassian tools. In a dedicated site, agencies have full control over plugin management, including installation, evaluation, and usage.
Plugin trial and purchase guidelines for dedicated model
Trial period
- Each plugin installation includes a 30-day trial. By installing a plugin, you confirm that your agency has approved the required security clearance for its use.
- After 30 days, the trial expires and the plugin will be disabled.
- Your site will remain unaffected, but you will lose access to the plugin’s features and any data or config linked to the plugin.
What happens after the trial?
- Plugin functionality stops once the trial ends.
- To continue using the plugin, you must submit a service request for procurement and provide confirmation that your agency has granted the necessary security clearance. This requirement ensures that agencies take responsibility for assessing and approving the security posture of any plugins they choose to install on their dedicated site.
- Expect a disruption in functionality between the trial’s end and when the plugin is purchased and re-enabled.
Purchase plugins
After the trail period, plugin features will no longer be available. To avoid any disruption of plugin features, install trial plugins and confirm their purchase by 15th of the same month.
- Plugin procurement may take up to 30 days from the monthly request consolidation date (15th of each month)†.
- Agencies can use their purchased plugins for 1 year from the date of purchase.
- Plugin purchases or renewals are billed upfront for the year and your subscription will be billed accordingly for this.
- SHIP-HATS team confirms with the respective agencies before renewing the plugin annually.
Examples
| Scenario | Plugin installed | Trial ends | Request submitted | Request processed in | Plugin available by† | Outcome |
|---|---|---|---|---|---|---|
| Ideal timing | 15 Aug | 14 Sep | 15 Aug | 15 Aug batch | 15 Sep | No disruption of plugin features |
| Early installation, timely request | 5 Aug | 4 Sep | 14 Aug | 15 Aug batch | 15 Sep | Disruption of plugin features from 5–14 Sep |
| Late installation, delayed request | 20 Aug | 19 Sep | 2 Sep | 15 Sep batch | 15 Oct | Disruption of plugin features from 20 Sep to 14 Oct |
Additional considerations
If the 15th falls on a weekend or public holiday, the 30-day processing period will begin on the next working day.
In December, procurement timelines may be longer than usual.
Additional guidelines
- User-based billing: Plugin costs are tied to user tier selected for the dedicated site. So, estimate your user tier appropriately before installing. For details, refer to Create Atlassian dedicated site
- Termination: SA or PA can terminate or cancel the subscription of a plugin by contacting SHIP-HATS team. However, if you terminate a paid plugin mid-year, the cost is not prorated.
- More info: See Atlassian’s guide: Understand billing for cloud apps.
Responsibilities
Agencies are responsible for:
- Evaluating plugin suitability and security
- Managing plugin lifecycle (install, review, remove)
- Ensuring compliance with internal policies
SHIP-HATS:
- Does not manage or approve plugins
- May assist with procurement on a best-effort basis
See - Ownership and responsibilities.
