James Anderson Contributor

This is a real concern because access rarely gets the same attention after it's granted as it does during approval. Someone changes roles, moves to another department, or leaves the company, but their old permissions may still be active. Over time, these forgotten permissions can accumulate, giving people access to…

@Aditya_miniOrange This is a really important distinction: access automation answers "how", while access governance answers "what, why, and under what conditions." And I think there is one more piece that becomes interesting here: context shouldn't just be used to make the initial provisioning decision. It should become an…

Hi @Elena_Elevatic Absolutely. The mover case is where access provisioning really becomes access governance. A department or role change shouldn't simply trigger additional access. It should trigger a re-evaluation of the user's existing access against the new role, so the system can determine what should be added,…

Hi, I agree with the core point that context should come before automation, but I wouldn't make Jira Assets a prerequisite for safe access provisioning. Assets can be a valuable context and relationship layer, but the more important question is where the authoritative data comes from and how the access decision is…

Hi @Matteo Vecchiato Have you implemented this yourself or seen anyone implement it? If so, could you please share how it was achieved and what you consider the best approach? That would be really helpful.

One thing I’d also be interested in exploring here is what happens after the initial provisioning. For example, if someone gets access to an Entra group or application today, how do you make sure that access is still appropriate six months later? Especially for temporary or elevated access, I think the workflow needs to…

Hi @Emma Phillips Exactly. Provisioning someone’s access is usually the easy part. The harder question is what happens a few months later. Was the access ever reviewed? Does the person still need it? Was it removed when their role changed or when they left? That’s where periodic reviews and a proper audit trail become…

 @Marc -Devoteam- That's a good point. Using Assets as the source of truth for employee attributes makes the automation much easier to manage. One thing I'd add is that department changes often require both provisioning and deprovisioning. It's not just about granting access to the new department, but also ensuring access…

I like this approach. Have you seen teams use the same pattern for permanent employees who change roles or departments? In my experience, the end date works well for contractors, but role changes are often harder to track because there's no predefined expiration date.

Hi, Just checking in to see if you found a solution for this. I'm curious because we're seeing more teams trying to manage employee onboarding through Jira Service Management, especially when HR, IT, and application owners are all involved. Did you end up using native JSM automation, a Marketplace app, or did you build a…

For us, creating the employee record in our HRMS isn't the hard part. The real challenge is coordinating IT, Admin, and other teams while keeping approvals, tasks, and audit trails in sync. The employee lifecycle is another challenge. During onboarding, we need to ensure new hires receive the right accounts, devices, and…