Dear NocoBase Team,
I’m resubmitting a feature request regarding audit logs functionality, which I noticed is currently only available in the Enterprise edition. As a small startup, we find this feature essential for:
- Tracking data changes
- Maintaining operational transparency
- Meeting basic compliance needs
While we understand the value of Enterprise features, our current scale makes the investment challenging. Would you consider either:
- Providing limited audit log support in the community edition (perhaps with basic tracking capabilities), or
- Offering this as a standalone paid plugin at a more accessible price point for small teams?
Additionally, if there’s any documentation or support available for implementing a basic audit system through:
- Automation rules
- Custom hooks/workflows
- Database triggers
We’d greatly appreciate guidance on interim solutions while this feature request is considered. Many in the community would benefit from such an approach.
an example from Nocodb
Hi @Sohail2949000 ,I’m sorry that the commercialization strategy for audit logs and records history has caused you trouble. They are not suitable for sale as independent plugins.
As a temporary measure, you can consider the following steps:
- Save a snapshot before the data changes.
- Save a snapshot after the data changes.
- Compare the differences before and after to generate a change record.
However, please note that this temporary measure is only suitable for scenarios with a small amount of data and infrequent operations.
@support Thank you for your suggestion on using snapshots as an interim solution for audit logging. To implement this effectively, I’d appreciate clarification on a few points:
- Snapshot Mechanism via Automation
- Could you elaborate on how to automate snapshots ?
- Are there templates or examples for capturing pre/post-change states?
- Scalability Limitations
- You mentioned this works best for “small amounts of data.” Could you define approximate thresholds (e.g., rows/table or frequency of changes)?
- What are the specific drawbacks with larger datasets (e.g., performance overhead, storage)?
- Alternative Approaches
- If snapshots aren’t scalable, are there other community-edition-friendly methods (e.g., logging only critical fields or leveraging database-native versioning)?
Simply put, use “Workflow - pre-action event” to capture and store the values before data changes; use “Workflow - after-action event” to capture and store the values after changes.
@support
Thank you for your previous response regarding the pre-action event plugin suggestion. I will purchase the plugin and try this out.
In the meantime, I’ve created a dedicated log table in my PostgreSQL database to track changes, which is working well. However, I’d like to integrate this table into the NocoBase interface for easier access and management.
Question: Is it possible to link or display this external PostgreSQL table within the NocoBase app? This would allow us to:
- View the audit logs directly in NocoBase
