Requirements before you begin

Most installation issues come down to one of three things: permissions, platform requirements, or timing. This page helps you confirm everything is in place before you begin.

---

Permissions

You need administrative access to the Atlassian Cloud site. Specifically, you must hold one of these roles: Organisation admin, Site admin, or Jira admin.

Space admin alone is not sufficient. JSM LaunchPad deploys Assets schemas at the site level, which requires administrative permissions that space-scoped roles do not grant.

warning

⚠️ If you are not sure which role you have, go to admin.atlassian.com and check your access level. If you cannot see the site administration section, you will need to ask someone who can to either grant you access or install the app on your behalf.

---

Platform requirements

JSM LaunchPad requires Jira Service Management Cloud with Assets enabled on the site.

If Assets is not visible in your Jira navigation, it means either your plan does not include it or it has not been activated yet. Assets is included in Jira Service Management Premium and Enterprise plans. If you are on a Free or Standard plan, you will need to upgrade before installing LaunchPad.

---

A clean starting point

LaunchPad can be installed into an existing environment, but the smoothest experience comes when you start with a fresh service space. If you already have a complex CMDB structure or are in the middle of a data migration, consider waiting until that work is complete before deploying.

You can always connect existing data after the initial schema is in place. The goal right now is a clean deployment, not a comprehensive one.

---

How long this takes

Activity	Typical time
Checking requirements (this page)	2 minutes
Installation	5 minutes
Schema deployment	1 to 2 minutes
First working request	20 to 40 minutes

You are not expected to configure everything in one sitting. The goal of the first session is a working service, not a finished one. Customisation comes later.

---