Assets FAQs

Assets is Atlassian's app for tracking the things your business depends on, such as laptops, vendors, software licenses, contracts, and even people, and linking them to the work happening in Jira, Jira Service Management, and Teamwork Collection. Think of it as a smart inventory that connects to your work.

A schema is a folder or category that groups similar objects together, for example, a 'Locations' schema or a 'Vendors' schema. Schemas themselves are free and don't count toward your allowance; only the objects inside them do. For more information, see the Assets schemas docs.

One object = one thing you're tracking. One laptop, one license, one vendor = 1 object each. It doesn't matter how you create it (manually, CSV/import, sync/discovery, API, or automation), each record counts as one object.

Counts toward your usage allowance ✅

• Any object created or imported through any supported surface:

• Objects created manually

• Objects imported via CSV, JSON, or LDAP

• Objects synced via discovery tools or integrations

• Objects created via the REST API

• Objects created by automation flows

This includes any type of record, physical assets (laptops, servers, phones), digital assets (software licenses, certificates), configuration items (services, applications), or custom business objects (vendors, contracts, cost centers, locations, employees).

Does NOT count toward your usage allowance ❌

• Business Portfolio and Software Registry objects are the only objects in system schemas that don’t count.

• Objects in Data Manager don’t count as they are not in a schema.

• Sandbox, Backup, and Restore objects: objects in non-production environments.

• Deleted objects: once an object is removed, it immediately stops being counted.

What you need to know:

• Object attributes (fields on an object, such as serial number, status, and owner) don't count separately; only the object itself counts as one unit, regardless of how many attributes it has.

• Object relationships (references linking one object to another) don't count toward the total; only the objects at each end of the relationship count.

• Your object count is across all user-created schemas on a site. For example: 3 custom schemas with 1,000 objects each = 3,000 objects in total.

• If you delete objects, your count decreases immediately.

Eligible paid cloud plans come with an included objects usage allowance:

Jira Service Management/Service Collection:

Jira (single-site, Sep 1, 2026 GA):

Teamwork Collection (single-site, Sep 1, 2026 GA):

Allowances pool at the org level across subscriptions (e.g., Jira Service Management Premium 50K + Jira Standard 1K = 51K total). 

When your teams need more objects, you have options to upgrade your plan, pre-pay for objects, or pay as you go. You’ll see alerts before you approach limits so you can plan ahead with confidence.

The product isn’t changing, only who can use it and where it’s managed and billed. Jira Service Management/Service Collection customers have paid for Assets by object count since 2024. Extra usage billing also starts at different times, depending on your current billing cycle.

What's new with usage-based pricing:

• Who can use it: Assets allowances are now also included in Jira and Teamwork Collection. Assets is currently being rolled out to single-site organizations on Standard and Premium plans, and will roll out to multi-site organizations in the next calendar year

• Where it's managed: You can now manage Assets object usage in the centralized Platform usage dashboard in Atlassian Administration, alongside other meters such as Rovo credits and Automation steps.

• How it's billed: Billing moves to the unified usage-based billing platform, so usage-based billing is in one place.

  • Volume discounts for monthly customers has been moved to prepaid-only for existing Jira Service Management/Service Collection customers.

  • Extra usage billing for annual and monthly customers starts at different times:

    • Existing Assets annual plan customers: extra usage billing continues with no changes  

    • Existing Assets monthly plan customers: extra usage billing will start on Dec 3, 2026

    • New Assets customers: after Sep 1, 2026 extra usage billing will start on Dec 3, 2026

• The Assets experience itself doesn't change.

What stays the same: 

The Assets objects meter isn’t changing. System schemas still don't count toward your allowance and are free to use. Existing Jira Service Management/Service Collection customers keep their current allowances. Pricing stays at $0.02/object/month with volume discounts available for prepaid usage packs. Pricing remains at our published rates, with volume discounts available for prepaid.

Most usage-based meters count actions over time. For example, the number of automation steps run per month. Assets is different; it measures how many objects you have stored right now, like a fuel gauge, not a trip counter.

Why customers like this:

• It's predictable. Object counts grow slowly and steadily; they don't spike unexpectedly.

• It goes down too. Delete objects, and your count drops right away.

Centralized usage management across all meters: same Platform usage dashboard, same 80%/100% usage notifications, same forecasting and usage controls.

Most usage-based meters count actions over time. For example, the number of automation steps run per month. Assets is different; it measures how many objects you have stored right now, like a fuel gauge, not a trip counter.

Why customers like this:

• It's predictable. Object counts grow slowly and steadily; they don't spike unexpectedly.

• It goes down too. Delete objects, and your count drops right away.

Everything else works like the other meters: the same usage dashboard, the same 80%/100% alerts, and the same forecasting and controls

Yes, it all goes into one shared pool. It doesn't matter how many schemas (folders) you have or how objects are spread across them; they're all counted against a single site-level allowance.

• Across products: allowances stack at the org level. Example: Jira Service Management Premium (50K) + Jira Standard (1K) = 51,000 total.

For customers on multiple sites, talk to your account team for timing. We’re investing in giving admins more tools to manage and allocate capacity, including across sites.  We’ll keep you updated on our roadmap.

Yes, right away. Because Assets is a gauge meter (a point-in-time count, not an action count), deleting or archiving objects lowers your count on the same day. No waiting for the billing cycle, no end-of-month reconciliation.

Example: delete 5,000 objects on Tuesday → your count drops by 5,000 that Tuesday. The dashboard updates within 15 minutes, and if you drop back below your allowance, any restrictions are lifted.

Assets objects work differently from the other metered capabilities. While Rovo, Automation, Customer Service Management AI agent resolutions, and Bitbucket meters use cumulative counters (they tally actions over a billing period and reset monthly). Asset objects are gauges that measure a point-in-time count of active objects, such as hardware, software licenses, configuration items, etc., stored in your instance at any given moment.

What this means:

• No monthly reset: Assets objects persist until deleted, so your count doesn't go back to zero each cycle.

• Usage trend reflects total inventory: The Platform usage dashboard shows how your Assets objects count is growing or shrinking over time, rather than how many you've "consumed" this period.

• Allowance comparison is against your current count: You're measured on how many Assets objects you have stored right now vs. your included allowance, not how many you've created this month.

The Platform usage dashboard will surface Assets alongside other usage-based pricing meters in the same centralized view, but the visual representation reflects this gauge nature, showing your current object count relative to your allowance threshold, rather than a cumulative usage bar that fills over the billing period.

Assets works differently from the other metered capabilities. While Rovo, Automation, Customer Service Management, and Bitbucket use cumulative counters (they tally actions over a billing period and reset monthly), Assets is a gauge meter, and measures a point-in-time count of active objects like hardware, software licenses, configuration items, etc. stored in your instance at any given moment.

What this means:

• No monthly reset: Assets objects persist until deleted, so your count doesn't go back to zero each cycle.

• Usage trend reflects total inventory: The Platform usage dashboard shows how your Assets objects count is growing or shrinking over time, rather than how many you've "consumed" this period.

• Allowance comparison is against your current count: You're measured on how many Assets objects you have stored right now vs. your included allowance, not how many you've created this month.

The Platform usage dashboard will surface Assets alongside other usage-based pricing meters in the same centralized view, but the visual representation reflects this gauge nature, showing your current object count relative to your allowance threshold, rather than a cumulative usage bar that fills over the billing period.

Yes, it all goes into one shared pool. It doesn't matter how many schemas (folders) you have or how objects are spread across them; they're all counted against a single site-level allowance.

• Across products: allowances stack at the org level. Example: Jira Service Management Premium (50K) + Jira Standard (1K) = 51,000 total.

For customers on multiple sites: talk to your account team — full support coming soon.

You can calculate and forecast your usage and cost at any time. Specifically, your organization and billing admins can:

• View your organization-wide allowance: by subscriptions (e.g., Jira Service Management Premium 50K + Jira Standard 1K = 51K).

• Monitor usage: the Platform usage dashboard (Administration → Insights → Platform usage → Assets objects) shows the current objects count in near real-time.

• Usage limits: Set and adjust extra usage limits as needed to cap spending.

• Get alerted: automatic notifications at 80% and 100% of your allowance and any extra usage limit you set.

• Forecast & control cost: built-in 90-day lookback forecasting*

Any single bulk import to Assets will impact forecasting.

If you reach your included Assets objects allowance, additional usage is automatically turned on, and you will be able to add new objects without interruption.

If you reach your included allowance and haven’t purchased usage packs, and extra usage is turned off, you won't be able to add new objects until you free up capacity by deleting objects or purchasing additional usage.

Specifically, these capabilities will be paused:

• Creating new objects manually

• Imports and syncs (including Discovery) that would add objects

• Automation rules that create objects

What keeps working: all existing objects remain fully usable; you can still view, edit, and report on them. 

We've put together resources to help you understand Assets, manage your usage, and get support when needed.

Product documentation & getting started:

• What is Assets? — Overview of capabilities and how to get started

• Assets usage and how it works — How object allowances and usage tracking work

• Manage the usage limit for Assets — How to set limits and purchase additional objects

• Assets documentation hub — Full product documentation

Usage management & admin tools:

Get help:

If you don't have a dedicated Customer Success Manager or Account Executive:
Start with Atlassian Support or the Atlassian Community for personalized guidance on usage planning, concessions, or migration support

If you have a dedicated Customer Success Manager or Account Executive:  You can reach out for questions about usage-based pricing, allowances, or commercial options