Actor × Project Coverage Matrix(5.6.8)

This matrix gives you a complete picture of who has been active in which projects during the selected period. An actor active in every project simultaneously — especially a new actor — is an anomalous access pattern worth investigating. An actor active in only one or two projects is operating within an expected scope.

For access reviews and role-based access audits, this matrix is the most direct evidence of what each person is actually doing versus what their role permits.

What you can conclude

• An actor active in all projects (fully filled row) has the broadest operational footprint — verify that all project access is authorized.
• An actor newly active in projects they had no prior involvement in should be investigated — was this a legitimate access grant or an unexpected expansion?
• Empty cells (no activity in a project) for an actor who supposedly has access may indicate that access was granted but is not being used — a candidate for access revocation.

How this chart works

Binary heatmap showing whether each actor has any events in each project in the selected period. Date filter only — project filter does not apply to this visual, as it shows cross-project coverage by design. Each row carries the type of account Jira reports for the actor: person, app, customer, unknown when Jira returned no type, or erased.

Some activity belongs to no project at all — issue type, filter, board and sprint administration. It is grouped in a column named Site-level, placed after the project columns. User-account and field changes belong to no project either, but the events Jira sends for them name no actor, so they do not appear in this matrix. An actor whose only marks sit in that column is working at the site level rather than inside any project, which is worth comparing against what their role is meant to cover.