Support Center / System Settings
Audit History — Who Changed What, and When
Every meaningful object — extensions, devices, routing, voicemail — keeps an audit history: what changed, when, and under which portal login. When Monday's calls route strangely, history usually answers "what changed Friday?" faster than any diagnostic.
What gets logged
Creates, updates, deletes, and configuration pushes, per object, with timestamps and the acting portal user. Provisioning fetches log too — useful for correlating "the phone updated itself at 9:02" with a complaint at 9:05.
Reading it well
- Start from the symptom's object: misrouted number → the number's history, then its destination route's history.
- Cross-reference the problem report's timestamp — the change immediately preceding the first bad call is your suspect.
- No relevant change in history? Now trust the diagnostic path instead; you've ruled out configuration in one minute.
Habits that make audit history valuable
- Individual portal logins, always. Shared admin accounts turn history into "someone did something."
- Scope admin roles so history entries imply intent (the person who can change routing is the person who does).
- Note-worthy changes (holiday routing, new menus) get an internal change note anyway — history tells you what, notes tell you why.
Related articles
Last reviewed August 6, 2026. Still stuck? Contact Signal Support from your portal — include what you expected, what happened instead, and one example phone number or extension.