Nimbax
Services
MigrationImplementationTrainingAdministrationLicense Management
View all services →
WorkAboutBlogFAQ
FRLet's talk
Nimbax

Atlassian Gold Solution Partner. Migration, implementation and training.

Partenaire de solutions Atlassian Gold

Services

  • Migration
  • Tool Implementation
  • Atlassian Training
  • Administration & Support
  • License Management
  • All our services

Company

  • About us
  • Our work
  • Blog
  • FAQ

Contact

  • info@nimbax.com
  • +1 (581) 880-6046
  • Québec, Canada
  • Support portal
Contact us

© 2026 Nimbax Services Conseil Inc. All rights reserved.

PrivacyTermsCookies
Home›Our work›Governance & audit
Governance & audit

Who has the right to delete?

Governing critical permissions on an enterprise platform

Who has the right to delete?
In brief

Some permissions — like deleting issues — are irreversible. Granting them without a framework is a risk. Here's how to govern them.

The problem

On a large instance, sensitive permissions end up distributed widely "for convenience". But a permission like permanent deletion doesn't forgive, and the lack of traceability makes it impossible to know who did what.

Why it's hard

Restricting a permission that's already distributed creates political friction. And defining "who should have it" requires clarifying responsibilities nobody has ever formalized.

The approach

Define an explicit accountability framework, document the assignment rules, and validate it all with the relevant data owners — so the decision rests on governance, not habit.

The proof

Nimbax designed a governance framework of this kind for a critical permission on an enterprise instance, making responsibilities explicit and compliance stronger.

Takeaway

An irreversible permission deserves explicit governance. "It's simpler if everyone has it" is precisely the mistake to avoid.

Let's talk about your sensitive permissions

An Atlassian expert gets back to you directly.

← All workStart my project