Issue Summary

Users who have only the Site admin role (and are not organization admins) are unable to use several filters/tabs in the site‑level audit logs. Specifically, the Activities, IP addresses, and Location tabs in the site‑level audit log UI fail to load for site admins, while they work correctly for organization admins.

Affected Users / Roles

• Affected: Users with Site admin role on a site, but no Organization admin role.

• Not affected: Users who are Organization admins (regardless of site admin role).

Steps to Reproduce

1. In an Atlassian organization, assign a user the Site admin role for a specific site.
   • Do not grant this user Organization admin permissions.
2. Have the user log in to https://admin.atlassian.com.
3. Select the assigned site.
4. Navigate to:
   Site settings → Audit log
   (URL pattern: https://admin.atlassian.com/s/<SITEID>/audit-log)

5. In the audit log page, attempt to use the:

• • Activities tab/filter
  • IP addresses tab/filter
  • Location tab/filter

Expected Results

• A user who is Site admin for a site, but not an Organization admin, should be able to:
  • View the site‑level audit logs, and
  • Use the Activities, IP addresses, and Location tabs/filters for that site.
• The UI should load data for these tabs without errors, as long as the user has the appropriate site‑level admin role.

Actual Results

• For users with Site admin only:
  • The Activities, IP addresses, and Location tabs under site‑level audit logs do not load any results.
  • The UI appears to be “stuck loading” or simply shows no data.

• Network/HAR inspection shows 403 Forbidden responses from org‑level admin APIs invoked by these tabs.

Example errors (for a site admin user):

Activities tab

Request URL:https://admin.atlassian.com/gateway/api/admin/v1/orgs/<orgid>/event-actionsRequest Method: GETStatus Code: 403 Forbidden

{ "timestamp": "2026-02-27T11:35:41.475+00:00", "path": "/api/admin/v1/orgs/<orgid>/event-actions", "status": 403, "error": "Forbidden", "requestId": "f62cb669-965683", "message": "User has no permission to access resource."}

IP addresses tab

Request URL:https://admin.atlassian.com/gateway/api/admin/v1/orgs/<orgid>/ip-addressesRequest Method: GETStatus Code: 403 Forbidden
 
{ "timestamp": "2026-02-27T11:37:35.131+00:00", "path": "/api/admin/v1/orgs/<orgid>/ip-addresses", "status": 403, "error": "Forbidden", "requestId": "870674f8-968059", "message": "User has no permission to access resource."}

 
Location tab

Request URL:https://admin.atlassian.com/gateway/api/admin/v1/orgs/<orgid>/locationsRequest Method: GETStatus Code: 403 Forbidden
    
{ "timestamp": "2026-02-27T11:37:11.417+00:00", "path": "/api/admin/v1/orgs/<orgid>/locations", "status": 403, "error": "Forbidden", "requestId": "c9bb03a2-967512", "message": "User has no permission to access resource."}  
 

For Organization admins, the same UI and API calls succeed (HTTP 200) and data is displayed correctly.

Workaround

Site admins to work with their org admins to pull the site-level audit details.