Audit Logs provide visibility into team activity within Tines 3B. This article shows you how to monitor user actions directly in the product or forward them to external systems for compliance and reporting.
You can monitor team actions in real-time through the audit logs in your settings, like this:
The logs are presented in a table view, providing the following information for every action:
Time: The timestamp when the action occurred.
User: The name or email address of the person who performed the action.
Operation: A description of the action taken.
Source: The origin of the action.
Status: Indicates whether the action succeeded or failed. Failures are highlighted in red.
Error/Input/Request context: Click these columns to view specific technical details, such as error messages, input parameters, or the IP address and user agent associated with the request.
Search and filter logs
You can search and filter the audit logs table to find specific actions or narrow the view to a subset of activity.
Search. Enter text in the search box at the top of the table to filter by member name, operation name, or other text visible in the table. The search applies across all columns.
Filters. Click the filter button in the top-right corner of the table to open the filter menu.
You can filter by:
Status. Show only successful actions, only failed actions, or all actions (default).
Source. Filter by the origin of the action: UI, API, SCIM, JIT, MCP, Federation, Device, or Internal. You can select multiple sources.
Member. Show actions by a specific member, or actions with no member (system actions). Select 'All' to see actions by everyone.
Time range. Limit the view to the last 24 hours, last 7 days, last 30 days, or all time (default).
Active filters appear as pills at the bottom of the table. Click the x on a pill to remove that filter, or click 'clear all' to reset all filters at once.
Tip: Search and filters work together. For example, you can search for 'workflow' and filter by a specific member to see all workflow-related actions that member performed.
Forwarding logs to external destinations
To keep your logs for long-term storage or compliance, you can configure destinations to automatically forward audit logs to external systems (such as S3 buckets, webhooks, or other archives).
Setting up a new destination
In audit logs under the destinations tab, click the plus button to configure your destination settings:
Name: Give your destination a descriptive name (e.g., "Compliance Archive").
URL: Provide the destination URL (must start with
https://). Select your request method (PUT or POST). If you are using an object store like S3, you can use the {filename} placeholder to manage batching.Auth: Optionally, select a connected app or connector to provide the necessary credentials (such as AWS SigV4 or API keys). If your endpoint is public, you can leave this blank.
Managing destinations
Once configured, your destinations list will appear on the destinations tab. From here, you can:
Edit: Click a destination row to modify its configuration or review recent delivery errors.
Delete: Open the menu on a destination row and select delete destination. This stops the flow of logs but does not remove data that has already been delivered to your external system.