Guide: institution audit and history
“Who enrolled this person?”, “when was this domain authorized?”, “what did the HR system change yesterday?” - the platform records administrative actions, and each question has a right place to be answered.
The map of trails
Section titled “The map of trails”| Question | Where the trail is |
|---|---|
| Who received or lost an administrative role? | The institution’s audit history - every role assignment and removal is recorded |
| Who changed the authorized email domains? | The same history - every change to the list is recorded |
| Why did this person’s enrollment change state? | The enrollment history records the state transitions - including transfers between classes, with origin, destination, and date |
| What did an external system do through the API? | The platform logs every call with the token used; the log has no screen of its own - ask Eduvem support for the lookup |
| Is this certificate legitimate? | Completion records a snapshot of the participant’s data at the moment of approval - the issuance is verifiable |
| Who deleted a message from the class chat? | Message deletions record the author of the action - see Chat and support channels |
Three habits worth the cost
Section titled “Three habits worth the cost”- One API token per integrated system - the call history only answers “which system did this” if each system has its own identity.
- Minimal roles - the smaller the circle of administrators, the shorter the questioning when something changes unexpectedly.
- Note the why outside the platform when the change is sensitive (domain authorization, new role): the trail says who and when; your internal record says why.