We currently audit key user actions and resource creation within our dashboard. As we are introducing the concept of organizations into Coder, we should create an org-scoped audit view so that users can identify changes relevant to a specific org.

Note that ideally, we would like to de-duplicate audit log views rather than having two (our existing audit log view and the new org-scoped audit log view laid out in this ticket). We will revisit design and find a way to consolidate views after orgs is in experimental. We ended up consolidating audit views and the below criteria has been updated.

Requirements

• In our existing audit log page, add organization context to each audit log item, perhaps alongside the IP and OS detail. If space is constrained, consider responsive design in below comment.
• In our existing audit log view, ensure that any audit log item (for example, template creation) correctly displays the org in the diff (we should get this for free), e.g. in the below image, org id or org name should be included only if there is an actual diff resources cannot move to a different organization
• Move our existing audit log view to deployment/audit and update sidebar to reflect new menu item
• Match the design laid out in the below comment
• Add "Auditing" link under each organization sidebar item that redirects to deployment/audit with org filter applied and org query applied.
• Org filter should be editable so users do not have to scroll back down to organizations to filter by a different organization
• Add an 'All Organzations' dropdown filter to the audit log view
• Add Jest tests for basic functionality
• Add storybooks
• Create a separate issue to encapsulate the work required to consolidate our two audit log views so that we can get started on this refactor after orgs is available as an experiment (and make sure to add this to the milestone!) added here