loading
Preparing LoginRadius developer resources
Mission: Help enterprises accelerate digital transformation with our fully-managed Customer IAM technology.
Skip to main content
Documentation

Team Audit Logs

Team Audit Logs record every administrative action your Team Members take in the Admin Console, including configuration changes, role updates, and deployments. Each entry captures who made the change, what changed, and when, in a searchable, exportable log. Use it for forensics, compliance reporting, and to feed your SIEM.

Access: Admin Console → Tenant Settings → Team Audit Logs for admin activity. If the feature is not enabled on your tenant, contact support@loginradius.com.


Use cases

Team Audit Logs give you an administrative change history you can act on. Common ways teams put it to work:

Privileged-access monitoring

Detect risky admin behavior, such as a Team Member changing password policy or MFA settings, rotating signing keys, disabling security restrictions like IP and domain allowlists, or exporting data dumps. These are high-impact actions where a single change affects every end user, so surface them for review.

Change accountability and attribution

Every configuration change is tied to the specific Team Member, so you can answer who changed a setting and when. When a login flow, SSO client, or role starts behaving differently, the log attributes it to a person and a timestamp, with no guessing.

Compliance and administrative access trail

SOC 2 and ISO 27001 require a record of who holds administrative access and what they did with it. Team Audit Logs give auditors a defensible change history, covering role and permission grants, secret rotations, and policy edits, each stamped with actor, timestamp, and IP.

Configuration incident forensics

When something breaks after a config change, such as a broken OIDC client, a bad email template, or a webhook that stopped firing, trace the exact sequence of admin changes leading up to it to find the offending edit and what to revert.

Segregation of duties and least-privilege review

Review the log periodically to confirm Team Members touch only the resources their role justifies, for example that only the right people change OAuth 2.0 credentials or B2B organization connections. Spot over-privileged accounts and access that should be revoked.


What gets logged

Team Audit Logs record administrative actions your Team Members take in the Admin Console. Each entry captures who performed the action, what they changed, the resource affected, and the exact time.

Typical entries include:
  • Configuration changes: tenant and application settings, login methods, and security policies.
  • Authentication app setup: OIDC, OAuth 2.0, SAML, and JWT client configuration.
  • Roles and permissions: role, permission, and default-role changes.
  • Keys and secrets: signing-key and secret rotations.
  • Messaging: email and SMS templates and delivery settings.
  • Extensibility: webhooks, workflows, forms, and custom fields or objects.

Use the logs to review recent changes, investigate an unexpected setting, attribute a change to a specific Team Member, or produce an access trail for security and compliance audits.

Retention: Team Audit Logs are kept for 90 days. The view shows activity from the last 90 days only.

Sample rows from the Team Audit Logs view:
TimeUIDActor TypeEventTargetStatus
2026-05-19 10:16:152b817d…60f4f6dashboardmodifyoptional_captcha.config200
2026-05-19 10:15:582b817d…60f4f6dashboardmodifyforms.registration200
2026-05-19 09:21:029c1f4a…d7e218dashboardcreatewebhook201
2026-05-18 17:02:189c1f4a…d7e218dashboarddeletewebhook204

Column reference

Every row in the audit logs has four key columns. Pick a tab to learn what its values mean.
The channel an action came through.
dashboard
A Team Member performing an action from the Admin Console.
api_key_secret
Action authenticated with an API key + secret pair (server-to-server).
api_key
Action authenticated with only an API key (public-side calls).
api_secret
Action authenticated with only an API secret.
m2m
A machine-to-machine call from a registered client.
oidc_client
An OIDC client driving the action — typically a federated app.
domain
A request from a registered Hub Domain or Custom Domain (browser-side).
org_user
An organization-scoped user acting within their org.

Filtering & searching

Both views share the same toolbar above the table. Pick a tab to see how each control works.
Combine any column with an operator (contains, equal, not equals) and a value. Click the + to add another rule — rules are combined with AND.
FiltersSearch by UIDSelect RuleSelect OperatorEnter valueCancelApplyATTRIBUTEOPERATORVALUEColumn to filter byHow to compareMatch value
Click Filters in the toolbar to open the rule builder.

Examples

See what an admin changed yesterday
  1. Open the Team Audit Logs view.
  2. Set the Date range to yesterday's window.
  3. Add filter: Actor Type · equal · dashboard.
  4. Add filter: Event · equal · modify.
  5. Apply. The table now shows every Admin Console change made yesterday.

Exporting logs

Click the Export button at the top right of the table to download the filtered result as a CSV — up to 10,000 rows per export. The file reflects the active filters and date range, so what you see is what you get.

Export
The Export button sits at the top right of the audit logs table.
Want to go further than the 90-day view?Stream Team Audit Logs straight into your own SIEM with Audit Log Integration. You get every record in real time, with no 10,000-row export cap and retention for as long as you keep it.Explore Audit Log Integration →