Audit events

Gain visibility into who did what, when, and where for all user activity on YepCode Platform.

When you and your team mates perform actions over YepCode resources, like for example creating a new process, invoking a webhook or updating a credential, these events are stored. Then, they can be analyzed to see the changes in your data. This feature helps with security because they provide records of all activity, including possible suspicious activity.

The possibility to track and see audit events is allowed for some of our paid plans. For teams with one of these plans, the team admins can access the audit events page, in which they can see a table with all audit events.

The table columns are:

• User → The user who performed the action. For execution events can also appear @webhook or @scheduler, depending on how the execution was launched.
• IP → The IP address of the user.
• ID → The ID of the entity that was affected.
• Type → The type of the entity that was affected.
• Event → The event that was performed.
• Time → The time when the event was performed.

Each table row can also have a content, depending on the type of the event that was performed. If the audit event has content, then the row will have an arrow to uncollapse the content.

For source code changes, you have a diff editor to see the changes in a very easy and clear way.

Export audit events

You can also export the audit events to a JSON file. For this, you need to click on the export button, at the top rigth of the screen, and the file download will start.