Getting Started with Atlassian Cloud

If your team has just migrated to Atlassian Cloud — or is evaluating it for the first time — the platform can feel overwhelming. There are products, plans, admin panels, and integrations pulling you in every direction.

This guide gives you a clear, practical orientation. No fluff. Just what you need to understand to start working productively.

What Atlassian Cloud Actually Is

Atlassian Cloud is the hosted version of Atlassian's product suite. Instead of installing and maintaining Jira or Confluence on your own servers, Atlassian runs it for you — handling infrastructure, upgrades, backups, and security patches.

The core products available on Cloud:

  • Jira Software — agile project and delivery tracking
  • Jira Service Management (JSM) — IT and operational service desk
  • Confluence — documentation and knowledge management
  • Bitbucket — Git repository hosting with built-in CI/CD
  • Trello — lightweight visual task management

All of these connect to each other natively. A Jira issue links to a Confluence page. A Bitbucket commit transitions a Jira ticket. That integration is what makes the Cloud ecosystem powerful.

Your First Week: What to Set Up

1. Create Your Atlassian Organization

Go to admin.atlassian.com. This is your central control panel. From here you manage users, products, security policies, and billing across everything.

Your organization is separate from your individual product instances. Think of it as the roof — your Jira site, your Confluence site, and your Bitbucket workspace all live under it.

2. Set Up a Jira Software Project

When you create a project in Jira Software, you choose a template:

  • Scrum — for sprint-based delivery teams
  • Kanban — for continuous flow work
  • Bug tracking — simple, queue-based issue management

For most engineering teams starting out, Scrum or Kanban is the right choice. Pick one and resist the urge to customize everything immediately. Work with the defaults for two weeks, then adjust based on what actually hurts.

3. Create a Confluence Space

A Space in Confluence is a container for pages. Create one space per team or product area to start. Don't create too many — five spaces are manageable, fifty are chaos.

Inside your space, create:

  • A team home page (who we are, what we own)
  • A decisions log (architecture decisions, process changes)
  • A runbooks folder (how to do recurring operational tasks)

4. Connect Jira and Confluence

In your Confluence space settings, link it to your Jira project. This lets you embed live Jira issue lists, sprint boards, and roadmaps directly into Confluence pages — without copy-pasting data that immediately goes stale.

Understanding Users and Permissions

Atlassian Cloud uses a layered permission model:

  • Organization admin — controls everything: products, users, security
  • Product admin — controls settings within a specific product (Jira, Confluence)
  • Project admin — controls settings within a specific Jira project
  • User — can view and edit based on project permissions

When starting out, keep the admin roles minimal. Too many admins leads to inconsistent configurations that are painful to untangle later.

The Most Common Beginner Mistakes

Customizing workflows before understanding the defaults. Jira's default workflows are good. Most teams customize them prematurely and end up with fragmented, inconsistent statuses that don't map to how work actually flows.

Creating too many projects. One project per team is usually the right starting point. Splitting work across ten projects for a five-person team adds overhead without benefit.

Ignoring Confluence from day one. Documentation debt compounds. Teams that don't build the documentation habit in week one are still not documenting in year two. Start a space, create a template, make it a norm.

Not linking Jira and Bitbucket early. The traceability between code and tickets — which commit fixed which bug, which branch is delivering which feature — only exists if Bitbucket and Jira are connected from the start.

What to Learn Next

Once you're comfortable with the basics:

  • Jira automation rules — reduce manual status updates and assignments
  • JSM — if your team handles IT or support requests, set up a service desk
  • Confluence templates — standardize how your team writes runbooks and postmortems
  • Atlassian Access — for SSO, SCIM provisioning, and enterprise security controls

The Atlassian Cloud platform rewards teams that invest in proper setup early. The defaults will get you started. Discipline and governance will keep you productive at scale.

Arivanandhan Chitheshwaran