With Audit Logs, your cybersecurity and compliance teams can:
💡 Get usage insights faster. Download a timeline of every action taken in Crossbeam and understand implications for partners and users.
✅ Scale compliance as your partner ecosystem grows. Access the data needed to keep your organization in compliance as more users and partners join Crossbeam.
🔒 Maintain data governance. Monitor historical changes to data sources, data sharing, partnerships, populations, team invites, and user roles.
Note: Audit Logs is a paid feature available in our Supernode pricing plan. Interested in upgrading? Visit your billing page to learn more or contact us here.
In this article:
How to Export Your Audit Logs
Prefer to watch instead? We got you.
From your Dashboard, select your user avatar in the top right corner of the page and navigate to your settings.
Select a date range for your Audit Log export. Then, click the ‘Export CSV’ button.
🔔 Note: You can export historical actions that have occurred since May 28th, 2021 to a CSV file. The following fields may be missing in audit log exports because Crossbeam didn’t start tracking this data until May 11, 2022: metadata, previous state, users impacted, organizations impacted, IP address.
You’ll receive an email to download a CSV file of your audit history for the date range you've selected.
Once you've downloaded your CSV export, you can drop it in Google Sheets or Excel to review your audit history.
Audit Log Data
Data source connection(s) changes
Removed a data source
Synced additional fields
Connected a data source
Removed fields being synced
Connection status changes
Update frequency changes
Established connection was reauthorized
Data sharing defaults/settings changes
Which population was affected
Which partners were impacted by the change
Date/time the change was made
What the sharing default/setting was before and what it is now
Who made the change (User or system account associated with an event)
Partnership invites
Date/time invite was accepted/sent
Who made the change (User or system account associated with an event)
Population changes
What field(s) was previously included/excluded
Date/time the change was made
Which partners were impacted by this change
Who made the change (User or system account associated with an event)
Integrations Activity
Who installed, updated, or removed an integration
Date/time the integration was installed, updated, or removed
What action was taken: installed, updated, or removed
Which integration was impacted
User role changes
If the role was updated
What were the changes made
Date/time the change was made/role was created
Who made the change (User or system account associated with an event)
Team invites and users
Date/time invite was sent or user was deleted
Who sent the invite or deleted the user (User or system account associated with an event)
Additional data:
Activity Date - the date and time the action took place (times will be in UTC)
IP Address
User - the name of the user who completed the action
User Email Address - the email address of the user who completed the action
Metadata - specific details about the completed action
(i.e. If a user created a population, the metadata will tell you the population name, the data source it's pulling from, and what filters are applied)
Previous State - what the data was before a user changed it
Partner(s) Impacted - the names of the partner(s) impacted
User(s) Impacted - The ID, name, and email of user(s) impacted by changes to user roles or permissions and new users/removed users on the Team page.
FAQs
Can you revert changes or restore a “previous version” of an action?
NoCan I export my audit log data into other tools via API access?
We do not offer that capability at this time.Who can view Audit Logs?
Admins or users with the “View Audit Logs” permission in Crossbeam.How much historical data can I export?
You can export historical actions that have occurred since May 28th, 2021 to a CSV file. The following fields may be missing in audit log exports because Crossbeam didn’t start tracking this data until May 11, 2022.metadata (specific details about actions taken in Crossbeam)
previous_state
users_impacted
organizations_impacted
ip_address