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.
I installed pre action plugin but unable to setup workflow. I tried the docs to but it says it need to update the documentations.
Kindly support us to setup up pre-action and post-action event to capture data.
I’m sorry, I didn’t understand your specific question. The Pre-action event has been added in the screenshot, which means that this workflow will be triggered before the order is updated. What to do after the trigger needs to be arranged in the workflow.
If you want to implement data history records in this way, you need to design a reasonable data structure and workflow for it. However, this can only achieve the function similar to the built-in data history records of NocoBase to a certain extent and in some scenarios, and it cannot be fully realized. And the implementation process is more complicated.
Dear @support @shleyZ,
We need your guidance on how to implement a solution for tracking changes in records. Many users are facing this issue—when something is modified in the database, we can’t identify who made the change or what was updated, even if it was accidental.
I attempted to create a trigger in the PostgreSQL database, which works in some cases. However, we can’t grant database access to managers or team leaders, so this isn’t a scalable solution.
Our goal is to track specific fields (e.g., order items) to monitor changes. I also experimented with pre- and post-action workflows in Nocobase, but my expertise in this area is limited.
If there’s a paid plugin available that can address this need, we’d be more than happy to purchase it. Change tracking is a critical requirement for our team, and we’d greatly appreciate your support in finding a viable solution.
Looking forward to your suggestions.
Best regards,
