Log retention and access

Step by step

Give a role access to the log

The permission is called Audit Log in roles. It is in English because this permission label is not translated.

1. Side menu → Team and access → Roles and permissions tab.
2. Find the role in the Company roles list and click its pencil icon (tooltip: Edit role; create a new role with Add role).
3. Stay on the Module permissions tab. The Module access table has Module, Read, Write, and Create columns.
4. Find the Audit Log row and check Read. Nothing else is needed to read the log or field histories.
5. Click Update role to save (or Create role for a new one).
6. Changing a role is a sensitive operation. The system asks for confirmation in the 2FA verification required window: “This is a sensitive action — confirm your identity with a code from your authenticator app.” Enter the Verification code and click Confirm. You will not be asked again for the next 15 minutes.
7. If 2FA is not enabled, you will see Two-step verification required and an Go to 2FA settings button. You cannot save the role until 2FA is enabled.

Ask the user to reload the page. They should see Audit Log in the side menu, and field history windows should start filling in.

Check how far back the log goes

The retention period is not shown anywhere in the app — neither in Settings nor on the company card. You can check it indirectly by finding the oldest entry:

1. Side menu → Audit Log.
2. Enter a date one year and two weeks ago in Date from; leave Date to blank.
3. Check the last row in the Date column. If there is nothing older, cleanup has run and older entries no longer exist; they cannot be recovered.

To extend the period, contact the person who manages the deployment and specify the company field changelog_retention_days, which defaults to 365; 0 means retain indefinitely. Cleanup runs daily as ChangeLog: Cleanup old entries (daily).

Retention

The default is 365 days. Cleanup runs once per day.

A value of 0 means “retain indefinitely.”

You cannot change retention from this screen. If your organization requires a longer history, contact NOXTI support before older entries are deleted.

Deleted entries cannot be restored.

Permissions

The log is protected by a separate permission, listed in English as Audit Log.

No one received it when the feature was introduced. This is deliberate: the log contains data that should not be visible to everyone. A company administrator must explicitly grant it in roles (Module permissions — read, write, and create).

Superadministrators and company administrators have access without being granted the permission.

Field history uses the same permission

This is the most common surprise: field history uses the same permission. There is no separate icon; click the value itself, which is underlined with dots.

Without this permission, the history window will not load anywhere in the system — even on an order the user can otherwise fully access (Document tracking — files attached to orders).

Symptom: the user clicks an underlined value, but the window stays blank or shows an error.

Company scope

The log shows only changes in the active company. Someone who works in several companies must switch companies to see another company's history (My companies — active company and switching context).

Entries for which the company could not be determined are not saved at all.

What the log does not replace

• Login history — who signed in and from where (Live monitor, login history, and activity statistics).
• AI assistant log — changes made by the assistant (Can the assistant change data? Plans and approvals).
• Email settings audit — changes to accounts and templates (Message templates and webhook security).
• Automation execution history (Execution history — what really happened).

These are five independent records. When checking what happened, look in the log for the relevant area.