Audit logs allow realm admins greater visibility into how users access their apps and the types of changes made to data and structure within those apps. Using audit logs, realm admins can ensure adherence to their organization’s security standards and compliance policies.
Note: Audit logs are included on all plans. Data retention (how long audit data is stored and accessible for compliance or business purposes) varies by plan. Visit the Quickbase Plans and Pricing page for more details.
Types of audit logs
The table below gives an overview of the types of activities tracked by audit logs. To view all existing audit logs and how they appear in Quickbase, visit the Audit Log Library.
| Activities |
Types |
| Data access and changes |
- App and table searches
- App and table home page access
- App settings access
- Code page access
- Custom email creation, updates, and deletion
- Dashboard creation, updates, access, and deletion
- Document template creation, updates, and deletion
- Embedded reports access
- Form creation, updates, access, and deletion
- Form activity through a URL redirect
- Form properties access
- Field properties access
- Field list access
- Record access, creation, modification, or deletion
- Report access, including through a URL redirect
- Rich text page access
- Table settings access
- Downloading all forms and users in app when going offline in mobile
- Calls to API_DoQueryCount, a call which counts the number of records in a table that match a set of criteria
- Calls to API_DoQuery, a call which queries records in a table that match a set of criteria
- User accessed data in a table in the app
- User accessed data in a table in the app via an API
- Searches at the app level, including the number of tables searched
|
| Group and email domain events |
- User added to a group
- User removed from a group
- Access for an email domain granted, updated, and revoked
|
| Login failures |
- Login failure due to invalid credentials. For example:
- Username does not exist
- Password is incorrect
- User has been deactivated
- Login failure due to an invalid ticket. For example:
- Ticket cannot be authenticated
- Ticket is expired
- Ticket is not authorized for the specific table or app someone is trying to access
- Login failure due to an invalid user token
|
| Pipeline events |
- Pipeline created/deleted/edited
- Pipeline manually enabled/disabled
- Pipeline disabled due to editing
- Prompt sent to Pipelines Smart Builder
|
| Plugin events |
- Plugin is installed
- Plugin is launched
- Plugin is removed from an application
- When the configuration settings for a plugin are changed
|
| Role events |
- Create a role
- Delete a role
- Update the name of a role
- Allow/disallow a user to add records in a table
- Allow/disallow a user to save public views in a table
- Allow/disallow a user to delete records in a table
- Allow/disallow a user to edit field properties in a table
- Grant permission to manage users and share the app
- Grant permission to edit app structure and permissions
- Grant permissions to disable access to app for users in the role
|
| Schema changes |
- App creation and deletion
- Table creation and deletion
- Relationship creation and deletion
- Field creation and deletion
- Enabling and disabling offline mode
- Dashboard creation and deletion
- Dashboard updates
|
| Solution events |
- Solution creation and deletion
- Apps: add/delete from a solution
- Pipelines: add/delete from a solution
- Contributors: add/delete from a solution
- Version creation and deletion
- Version rollback
- Solution exported via Solution API
- Solution created via Solution API
- Solution updated via Solution API
- List of changes to a solution generated via Solution API
|
| User events |
- User creation
- User token creation, deletion, activation, deactivation, and transfer
- All successful log-ins and log-outs
- User invited to an app
- User granted access to an app
- Update a user's role
- Remove a user from an app
- User switched to and from a service account
- User assigned and unassigned super user permissions
|
Using audit logs