Best practices for multi-district data separation and permissions in Jira Assets

[Nick Daniel]

For some context, we are an organization that supports multiple school districts.

At first glance, using a separate schema or district-specific object types within a schema can seem like a simple way to manage permissions by isolating assets per district. However, this approach does not scale well and increases administrative overhead as the number of districts and asset types grows.

In an environment with multiple school districts that operate semi-independently, what is the recommended best-practice approach in Jira Assets for handling permissions and data separation while maintaining scalability, efficiency, and a clean data model?

Ideally, we would want only technicians from each district to access assets specific to their district (with no cross-district visibility because it simply is not necessary).

[Marc -Devoteam- · Accepted solution]

Hi @Nick Daniel 

The best is to have separate asset schemas, as this is the only way to guarantee that permissions are able to be set to specific. roles and groups in relation to the organization.

You could also start looking if Data Manager would be an option, to start with.

[Nick Daniel]

Thank you for taking the time to answer!

[Williams Welsh · Accepted solution]

Managing multi-district data in Jira Assets can be tricky because Jira doesn’t support true multi-tenancy. The best approach is to use separate asset schemas per district and control access with permissions, roles, and groups, ensuring each team only sees their data. For strict isolation or compliance needs, consider separate Jira instances for each district, though this adds admin overhead. Logical separation combined with careful permission management usually handles most multi-district setups effectively.

[Nick Daniel]

Thank you!