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 members of the Owners team can access an organization's audit log.

  1. In the top right corner of any page, click your username. highlighted username

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

  3. On the right side of the organization profile page, click Audit log. Audit log on the organization page

Searching the audit log

The audit log lists the following information about actions made within your organization:

  • 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 audit entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the audit log—such as -, >, or < —match the same format as searching across GitHub Enterprise.

Search based on repository

Use the repo qualifier to limit actions to a specific repository owned by your organization. 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 your organization's 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 the member of your organization that 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 Enterprise 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.
hook Contains all activities related to webhooks.
org Contains all activities related organization membership
payment_method Contains all activities related to how your organization pays for GitHub.
repo Contains all activities related to the repositories owned by your organization.
team Contains all activities related to teams in your 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:billing excludes all events in the billing 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:billing.change_email excludes all events where the billing email was changed.

This list describes the available categories and associated events:

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 org category
Action Description
cancel_invitation Triggered when an organization invitation has been revoked.
invite_member Triggered when a new user was invited to join your organization.
The oauth_application category
Action Description
create Triggered when a new OAuth application is created.
destroy Triggered when an existing OAuth application is deleted.
reset_secret Triggered when an OAuth application's client secret of is reset.
revoke_tokens Triggered when an OAuth application's user tokens are revoked.
transfer Triggered when an existing OAuth application is transferred to a new organization.
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 is given collaboration access to a repository.
create Triggered when a new repository is created.
destroy Triggered when a repository is deleted.
enable Triggered when a repository is reenabled.
remove_member Triggered when a user is removed from a repository as a collaborator.
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.
The team category
Action Description
add_member Triggered when a member of an organization is added to a team.
add_repository Triggered when a team is given control of a repository.
create Triggered when a new team is created.
destroy Triggered when a team is deleted from the organization.
remove_member Triggered when a member of an organization is removed from a team.
remove_repository Triggered when a repository is no longer under a team's control.

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--that's year-month-day. You may also add some optional time information, formatted as THH:MM:SS+07:00--that's hour-minutes-seconds (HH:MM:SS), followed by a UTC offset (+07: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.

Further reading