Learn about permissions in hardware asset management

Hardware asset management is available with Jira Service Management Premium and Enterprise.

To set it up, you must be a Jira admin and an Assets admin.

Access to hardware asset management works in layers, and most tasks draw on more than one. Each person needs to clear the broader layers before the more specific ones apply, so it helps to read them from the outside in:

A hardware role lets a person into the hardware area and — for administrators — into Hardware settings. You assign roles in Hardware settings > Access. To learn how, see Manage who can access hardware.
Space membership lets a person see and work the hardware requests in a service project — they must be a member of the space a request belongs to.
Jira project permissions control what a person can do to the work items themselves — view, edit, and move them through their workflow.
Assets permissions control what a person can do to the underlying hardware data — view, add, edit, or delete the hardware objects, models, and stockrooms. Your hardware is stored as objects in Assets, so what a person can see and change always depends on their permissions on the hardware assets schema.

The Permissions in hardware asset managment table further down lists every hardware task and the exact permissions it needs, from the broadest scope to the most specific.

A hardware role isn't the whole picture. Giving someone the Administrator or User role grants access to hardware asset management but does not allow them to change work items or hardware data. They also need the corresponding Jira Service Management, Assets or space permission.

Permissions in hardware asset management

This table lists every hardware task and the permissions it needs. Where a task needs more than one, they're listed from the broadest scope to the most specific. Tasks are grouped by the kind of work they involve.

Task	Required permissions (broad to specific)
Viewing hardware
Open the Hardware overview	Hardware role (User), then Assets view on the hardware schema (data shows only what they can see)
View a hardware object, model, or stockroom	Hardware role (User), then Assets view on the hardware schema.Users without Hardware role (User) can still view objects within the Hardware assets schema in Assets.
View a hardware request or work item	Membership of the service space, then Jira project view permission
Raising requests
Report broken hardware, or request new hardware, a repair, a configuration, or a refresh	Membership of the service space, then permission to create that request
Working and fulfilling requests
Progress a request that doesn't change hardware data — edit it, comment, move it through its workflow (for example, an audit)	Membership of the service space, then Jira project edit/transition permission
Fulfil a request that changes hardware data — assign, ship, collect, transfer, dispose, or receive hardware	Membership of the service space, then Jira project edit/transition permission, and finally Assets create/edit/delete on the hardware schema
Managing hardware data
Add, edit, or delete a hardware object or model directly	Hardware role (to reach the view), then Assets create/edit/delete on the hardware schema
Add or update a stockroom	Hardware role (to reach the view), then Assets create/edit on the hardware schema
Import hardware data	Hardware role (Administrator), then Assets create/import on the hardware schema
Configuring settings (administrators)
Open Hardware settings	Hardware role (Administrator)
Assign hardware roles (manage who has access)	Hardware role (Administrator)
Configure hardware types and model types (tracking)	Hardware role (Administrator)
Set up stock rules	Hardware role (Administrator), then Assets edit on the stock objects
Set up depreciation rules	Hardware role (Administrator)
Enable or configure Rovo hardware skills	Hardware role (Administrator)
Add or change a request type	Hardware role (Administrator), then membership of the space you're adding it to
Disable or re-enable hardware asset management	Hardware role (Administrator)
Automations
Turn on or build an automation — create work items, stock replenishment, compliance and expiry checks, notifications, or bulk actions	Hardware role (Administrator), to reach the Hardware Automation view, then permission to manage automations for that space or globally, and, when the rule changes hardware data, Assets edit permissions for the Hardware assets schema.
Rovo skills
Use /search-hardware or /get-hardware-insights to find hardware and see insights	Hardware role (User), then Assets view on the hardware schema (results show only what they can see)
Use /hardware-setup or /hardware-configuration to set up or configure hardware	Hardware role (Administrator), then the same permissions as the settings task being performed
First-time setup
Set up hardware asset management for the first time	Jira admin and Assets admin.

Roles get people in; foundational permissions let them act. After you give someone a hardware role, check they also have the right permission for the task:

to view or change hardware data, the right Assets permissions on the hardware assets schema;
to raise or work requests, membership of the service space and the matching Jira project permission;
to manage automations or request types, the relevant space or global settings permission.

Was this helpful?

It wasn't accurateIt wasn't clearIt wasn't relevant

Still need help?

The Atlassian Community is here for you.

Ask the Community