Skip to content

🔎 Documentation: Audit

Sign-ins, actions, errors and events. What it is, how it works and how to use it — explained step by step.

🔎 Definition — Audit

The audit records who did what and when in the system: sign-ins (logins and logouts), actions, errors and events. It supports security, compliance and investigation.

🔑
Sign-insPortal logins: user, date, IP and result.
📝
ActionsChanges and operations performed in the system.
⚠️
Errors and eventsProblems and important system events.
🔎
Search and filtersBy user, date and record type.

🗺️ Diagram

Every action leaves a trail; UCaaS stores it in the log and you review it with filters.

🧑Useraction / sign-inlogs🏢UCaaSaudit logstores📚Recordwho / what / whenreview🔎Reviewfilters

Helps detect unusual sign-ins, review what changed and prove compliance.

📘 Explanation (step by step)

  1. Every sign-in, action, error and event is logged automatically.
  2. In Audit you review the log with filters (user, date, type).
  3. Use it for security (detect suspicious sign-ins) and compliance.

🖥️ What you see on screen

🔐
Portal sign-insUser, date and time, IP, browser and whether the sign-in succeeded or failed. Repeated failed attempts stand out.
📝
Activity per moduleWhat was created, changed or deleted in each module, with the user responsible.
💻
Trusted devicesDevices where the second verification step was remembered. The administrator can revoke them.
🟢
Active usersWho is working in the portal right now and in which section.

✅ How to use it in practice

  1. Review sign-ins once a week. Look for sign-ins outside business hours, from countries where you do not operate, or with many failed attempts.
  2. When something changed and nobody knows who. Filter by date and module: the log shows the user and the exact moment.
  3. When someone leaves the company. Deactivate the user and revoke their trusted devices; the history of what they did is kept.
  4. When a customer or an auditor asks. The log serves as evidence of who accessed what information and when.

What the audit does not do: it does not store the content of calls or messages. That is what call recording and the messaging inboxes are for, each with its own permissions.

❓ Frequently asked questions

❓
How long are the records kept?The log is kept according to what was agreed with your company; sign-ins and actions are not deleted when a session ends.
❓
Can a user delete their own trail?No. The record is written by the system and users cannot edit or delete it from the portal.
❓
Can we see who played a recording or opened a conversation?Yes. Access to recordings and inboxes is logged just like any other action.