Reviewing the audit log for your organization

The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.

In this article

Accessing the audit log

The audit log lists actions performed within the last 90 days. Only owners can access an organization's audit log.

  1. In the top right corner of GitHub, click your profile photo, then click Your profile.

    Profile photo

  2. On the left side of your profile page, under "Organizations", click the icon for your organization.

    organization icons

  3. Under your organization name, click Settings.

    Organization settings button

  4. In the Settings sidebar, click Audit log.

    Org audit log settings in sidebar

Searching the audit log

The log lists the following information about each action:

  • Which repository an action was performed in
  • The user that performed the action
  • The action that was performed
  • Which country the action took place in
  • The date and time the action occurred

Note that you cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as -, >, or <, match the same format as searching across GitHub. For more information, see "Searching on GitHub."

Search based on operation

Use the operation qualifier to limit actions to specific types of operations. For example:

  • operation:access finds all events where a resource was accessed.
  • operation:authentication finds all events where an authentication event was performed.
  • operation:create finds all events where a resource was created.
  • operation:modify finds all events where an existing resource was modified.
  • operation:remove finds all events where an existing resource was removed.
  • operation:restore finds all events where an existing resource was restored.
  • operation:transfer finds all events where an existing resource was transferred.

Search based on repository

Use the repo qualifier to limit actions to a specific repository. For example:

  • repo:my-org/our-repo finds all events that occurred for the our-repo repository in the my-org organization.
  • repo:my-org/our-repo repo:my-org/another-repo finds all events that occurred for both the our-repo and another-repo repositories in the my-org organization.
  • -repo:my-org/not-this-repo excludes all events that occurred for the not-this-repo repository in the my-org organization.

Note that you must include the account name within the repo qualifier; searching for just repo:our-repo will not work.

Search based on the user

The actor qualifier can scope events based on who performed the action. For example:

  • actor:octocat finds all events performed by octocat.
  • actor:octocat actor:hubot finds all events performed by both octocat and hubot.
  • -actor:hubot excludes all events performed by hubot.

Note that you can only use a GitHub username, not an individual's real name.

Search based on the action performed

To search for specific events, use the action qualifier in your query. Actions listed in the audit log are grouped within the following categories:

Category Name Description
account Contains all activities related to your organization account.
billing Contains all activities related to your organization's billing.
discussion_post Contains all activities related to discussions posted to a team page.
discussion_post_reply Contains all activities related to replies to discussions posted to a team page.
hook Contains all activities related to webhooks.
integration_installation_request Contains all activities related to organization member requests for owners to approve integrations for use in the organization.
marketplace_agreement_signature Contains all activities related to signing the GitHub Marketplace Developer Agreement.
marketplace_listing Contains all activities related to listing apps in GitHub Marketplace.
org Contains all activities related to organization membership
organization_label Contains all activities related to default labels for repositories in your organization.
payment_method Contains all activities related to how your organization pays for GitHub.
profile_picture Contains all activities related to your organization's profile picture.
project Contains all activities related to project boards.
protected_branch Contains all activities related to protected branches.
repo Contains all activities related to the repositories owned by your organization.
repository_content_analysis Contains all activities related to enabling or disabling data use for a private repository.
repository_dependency_graph Contains all activities related to enabling or disabling the dependency graph for a private repository.
repository_vulnerability_alert Contains all activities related to security alerts for vulnerable dependencies.
sponsors Contains all events related to sponsor buttons (see "Displaying a sponsor button in your repository")
team_discussions Contains activities related to managing team discussions for an organization.

You can search for specific sets of actions using these terms. For example:

  • action:team finds all events grouped within the team category.
  • -action:hook excludes all events in the webhook category.

Each category has a set of associated events that you can filter on. For example:

  • action:team.create finds all events where a team was created.
  • -action:hook.events_changed excludes all events where the events on a webhook have been altered.

This list describes the available categories and associated events:

The account category
Action Description
billing_plan_change Triggered when an organization's billing cycle changes.
plan_change Triggered when an organization's subscription changes.
pending_plan_change Triggered when an organization owner or billing manager cancels or downgrades a paid subscription.
pending_subscription_change Triggered when a GitHub Marketplace free trial starts or expires.
The billing category
Action Description
change_billing_type Triggered when your organization changes how it pays for GitHub.
change_email Triggered when your organization's billing email address changes.
The discussion_post category
Action Description
update Triggered when a team discussion post is edited.
destroy Triggered when a team discussion post is deleted.
The discussion_post_reply category
Action Description
update Triggered when a reply to a team discussion post is edited.
destroy Triggered when a reply to a team discussion post is deleted.
The hook category
Action Description
create Triggered when a new hook was added to a repository owned by your organization.
config_changed Triggered when an existing hook has its configuration altered.
destroy Triggered when an existing hook was removed from a repository.
events_changed Triggered when the events on a hook have been altered.
The integration_installation_request category
Action Description
create Triggered when an organization member requests that an organization owner install an integration for use in the organization.
close Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request.
The issue category
Action Description
destroy Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository.
The marketplace_agreement_signature category
Action Description
create Triggered when you sign the GitHub Marketplace Developer Agreement.
The marketplace_listing category
Action Description
approve Triggered when your listing is approved for inclusion in GitHub Marketplace.
create Triggered when you create a listing for your app in GitHub Marketplace.
delist Triggered when your listing is removed from GitHub Marketplace.
redraft Triggered when your listing is sent back to draft state.
reject Triggered when your listing is not accepted for inclusion in GitHub Marketplace.
The org category
Action Description
audit_log_export Triggered when an organization admin creates an export of the organization audit log. If the export included a query, the log will list the query used and the number of audit log entries matching that query.
block_user Triggered when an organization owner blocks a user from accessing the organization's repositories.
cancel_invitation Triggered when an organization invitation has been revoked.
disable_oauth_app_restrictions Triggered when an owner disables OAuth App access restrictions for your organization.
disable_saml Triggered when an organization admin disables SAML single sign-on for an organization.
disable_member_team_creation_permission Triggered when an organization owner limits team creation to owners. For more information, see "Setting team creation permissions in your organization."
disable_two_factor_requirement Triggered when an owner disables a two-factor authentication requirement for all members, billing managers, and outside collaborators in an organization.
enable_oauth_app_restrictions Triggered when an owner enables OAuth App access restrictions for your organization.
enable_saml Triggered when an organization admin enables SAML single sign-on for an organization.
enable_member_team_creation_permission Triggered when an organization owner allows members to create teams. For more information, see "Setting team creation permissions in your organization."
enable_two_factor_requirement Triggered when an owner requires two-factor authentication for all members, billing managers, and outside collaborators in an organization.
invite_member Triggered when a new user was invited to join your organization.
oauth_app_access_approved Triggered when an owner grants organization access to an OAuth App.
oauth_app_access_denied Triggered when an owner disables a previously approved OAuth App's access to your organization.
oauth_app_access_requested Triggered when an organization member requests that an owner grant an OAuth App access to your organization.
remove_billing_manager Triggered when an owner removes a billing manager from an organization or when two-factor authentication is required in an organization and a billing manager doesn't use 2FA or disables 2FA.
remove_member Triggered when an owner removes a member from an organization or when two-factor authentication is required in an organization and an organization member doesn't use 2FA or disables 2FA. Also triggered when an organization member removes themselves from an organization.
remove_outside_collaborator Triggered when an owner removes an outside collaborator from an organization or when two-factor authentication is required in an organization and an outside collaborator does not use 2FA or disables 2FA.
unblock_user Triggered when an organization owner unblocks a user from an organization.
update_default_repository_permission Triggered when an owner changes the default repository permission level for organization members.
update_member Triggered when an owner changes a person's role from owner to member or member to owner.
update_member_repository_creation_permission Triggered when an owner changes the create repository permission for organization members.
update_saml_provider_settings Triggered when an organization's SAML provider settings are updated.
update_terms_of_service Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "Upgrading to the Corporate Terms of Service."
The organization_label category
Action Description
create Triggered when a default label is created.
update Triggered when a default label is edited.
destroy Triggered when a default label is deleted.
The oauth_application category
Action Description
create Triggered when a new OAuth App is created.
destroy Triggered when an existing OAuth App is deleted.
reset_secret Triggered when an OAuth App's client secret is reset.
revoke_tokens Triggered when an OAuth App's user tokens are revoked.
transfer Triggered when an existing OAuth App is transferred to a new organization.
The payment_method category
Action Description
clear Triggered when a payment method on file is removed.
create Triggered when a new payment method is added, such as a new credit card or PayPal account.
update Triggered when an existing payment method is updated.
The profile_picture category
Action Description
update Triggered when you set or update your organization's profile picture.
The project category
Action Description
create Triggered when a project board is created.
link Triggered when a repository is linked to a project board.
rename Triggered when a project board is renamed.
update Triggered when a project board is updated.
delete Triggered when a project board is deleted.
unlink Triggered when a repository is unlinked from a project board.
update_org_permission Triggered when the base-level permission for all organization members is changed or removed.
update_team_permission Triggered when a team's project board permission level is changed or when a team is added or removed from a project board.
update_user_permission Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.
The protected_branch category
Action Description
create Triggered when branch protection is enabled on a branch.
destroy Triggered when branch protection is disabled on a branch.
update_admin_enforced Triggered when branch protection is enforced for repository administrators.
update_require_code_owner_review Triggered when enforcement of required Code Owner review is updated on a branch.
dismiss_stale_reviews Triggered when enforcement of dismissing stale pull requests is updated on a branch.
update_signature_requirement_enforcement_level Triggered when enforcement of required commit signing is updated on a branch.
update_pull_request_reviews_enforcement_level Triggered when enforcement of required pull request reviews is updated on a branch.
update_required_status_checks_enforcement_level Triggered when enforcement of required status checks is updated on a branch.
rejected_ref_update Triggered when a branch update attempt is rejected.
policy_override Triggered when a branch protection requirement is overridden by a repository administrator.
update_allow_force_pushes_enforcement_level Triggered when force pushes are enabled or disabled for a protected branch.
update_allow_deletions_enforcement_level Triggered when branch deletion is enabled or disabled for a protected branch.
update_linear_history_requirement_enforcement_level Triggered when required linear commit history is enabled or disabled for a protected branch.
The repo category
Action Description
access Triggered when a repository owned by an organization is switched from "private" to "public" (or vice versa).
add_member Triggered when a user accepts an invitation to have collaboration access to a repository.
add_topic Triggered when a repository admin adds a topic to a repository.
archived Triggered when a repository admin archives a repository.
create Triggered when a new repository is created.
destroy Triggered when a repository is deleted.
disable Triggered when a repository is disabled (e.g., for insufficient funds).
enable Triggered when a repository is reenabled.
remove_member Triggered when a user is removed from a repository as a collaborator.
remove_topic Triggered when a repository admin removes a topic from a repository.
rename Triggered when a repository is renamed.
transfer Triggered when a repository is transferred.
transfer_start Triggered when a repository transfer is about to occur.
unarchived Triggered when a repository admin unarchives a repository.
The repository_content_analysis category
Action Description
enable Triggered when an organization owner or person with admin access to the repository opts in to data use for a private repository.
disable Triggered when an organization owner or person with admin access to the repository opts out of data use for a private repository.
The repository_dependency_graph category
Action Description
enable Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a private repository.
disable Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a private repository.
The repository_vulnerability_alert category
Action Description
create Triggered when GitHub creates a security alert for a vulnerable dependency in a particular repository.
resolve Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency.
dismiss Triggered when an organization owner or person with admin access to the repository dismisses a security alert about a vulnerable dependency.
authorized_users_teams Triggered when an organization owner or a member with admin permissions to the repository updates the list of people or teams authorized to receive security alerts for vulnerable dependencies in the repository.

The sponsors category

Action Description
repo_funding_link_button_toggle Triggered when you enable or disable a sponsor button in your repository (see "Displaying a sponsor button in your repository")
repo_funding_links_file_action Triggered when you change the FUNDING file in your repository (see "Displaying a sponsor button in your repository")
The team_discussions category
Action Description
disable Triggered when an organization owner disables team discussions for an organization. For more information, see "Disabling team discussions for your organization."
enable Triggered when an organization owner enables team discussions for an organization.

Search based on time of action

Use the created qualifier to filter actions in the audit log based on when they occurred. Date formatting must follow the ISO8601 standard, which is YYYY-MM-DD (year-month-day). You can also add optional time information THH:MM:SS+00:00 after the date, to search by the hour, minute, and second. That's T, followed by HH:MM:SS (hour-minutes-seconds), and a UTC offset (+00:00).

Dates support greater than, less than, and range qualifiers. For example:

  • created:2014-07-08 finds all events that occurred on July 8th, 2014.
  • created:>=2014-07-08 finds all events that occurred on or after July 8th, 2014.
  • created:<=2014-07-08 finds all events that occurred on or before July 8th, 2014.
  • created:2014-07-01..2014-07-31 finds all events that occurred in the month of July 2014.

The audit log contains data for the past 90 days, but you can use the created qualifier to search for events earlier than that.

Search based on location

Using the qualifier country, you can filter actions in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example:

  • country:de finds all events that occurred in Germany.
  • country:Mexico finds all events that occurred in Mexico.
  • country:"United States" all finds events that occurred in the United States.

Exporting the audit log

You can export the log as JSON data or a comma-separated value (CSV) file.

Export button

To filter the results in your export, search by one or more of these supported fields before using the Export drop-down menu.

Key Example value
action team.create
actor octocat
user codertocat
org octo-org
repo octo-org/documentation
created_at 1429548104000 (Timestamp shows the time since Epoch with milliseconds.)
data.hook_id 245
data.events [ "issues", "issue_comment", "pull_request", "pull_request_review_comment" ]
data.events_were [ "push", "pull_request", "issues" ]
data.target_login octocat
data.old_user hubot
data.team octo-org/engineering

Using the Audit log API

Note: The Audit log API is available for organizations using GitHub Enterprise. For more information, see "GitHub's products."

To ensure a secure IP and maintain compliance for your organization, you can use the Audit log API to keep copies of your audit log data and monitor:

  • Access to your organization or repository settings.
  • Changes in permissions.
  • Added or removed users in an organization, repository, or team.
  • Users being promoted to admin.
  • Changes to permissions of a GitHub App.

The GraphQL response can include data for up to 90 to 120 days.

For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "GraphQL API Audit Log" in the GitHub Developer documentation.

Further reading

Ask a human

Can't find what you're looking for?

Contact us