Event log for the administrator

How can I see, which changes have been made in CleanManager as an administrator?

If you have access to CleanManager as an administrator, then you have the option to see the changes made in the CleanManager account. You can see changes made by yourself, supervisors, and employees.

An administrator can see general events in connection to administrative changes, and employees' log-ins at tasks, but also see when codes were accessed by employees or when e-mails and SMS were sent from the system.

You can also see changes made in regard to integrations with other software.

The event log only showcases a limited amount of data. This means, that if many changes have been made to your tasks, your customers, and your products, then there is a chance, that you will not be able to see all changes when going too far back in time. 

The event log can show only a limited amount of data. This means that if you have made many changes to tasks, customers, and products, it could happen that changes will stop being shown when going long enough back in time.

Your CleanManager account always has a full event log saved internally, with all registered events. For more information regarding this, go to the article: Exporting the event log

In this article, you will read about how you access different information in the event log:

• How do I access the event log?

• How can I see if employees have accessed codes?

• How can I get an overview of the messages that have been sent?

• How can I see events that happen in regard to my integrations?

---

This is how you access the event log

	Log in to the administrator account
	In the menu, go to Event log
	In the list, you can see the changes made in CleanManager
	Time: Time and date of the change made Event: Description of the change made Performed by: The Administrator, a supervisor, or an employee
	Click on an event, in this case, the system language has been edited
	You will then be sent to the part of the system, where the change took place. In this case, My data > Company data on the day the change has been made.

INFO:

A quick way to find the information you are looking for is to click on Ctrl + F (PC) or Command + F (Mac) to search in the browser.

By doing this, all results of your search will be shown in the event log.

---

This is how you can see if employees have accessed codes

	In the menu, go to Event log
	Click on Codes to see all events related to codes
	In the list, you will see events, where employees have accessed codes from customers
	Time: Date and time when the event occurred Event: Description of the event, as well as which employee has accessed the code Key ring: Which key ring has been accessed Customer: The customer to whom the key ring is assigned to
	Click on an event to be sent to Keys > Overview

---

This is how you can get an overview of the messages that have been sent

In the menu, go to Event log

Click on Communications to see the e-mails and SMS sent from the system

In the list, you can see all events related to messages

1. Time: Time and date when the message was sent
   
2. Sender: The employee that sent the message
3. Receiver: The name of the receiver. If you click on it, it will either show the e-mail address or the phone number of the receiver
   
4. Subject: Description of the content of an automated message
   
5. Type: Description of the way the message was sent (e-mail or SMS) and if it has been sent manually by a user or if it is an automated message from the system
   
6. Status: Verification that the message is being delivered or has been received by the receiver

For a further explanation of the different status options, read the following table

Status when sending to a singular receiver

Status	Explanation
Sent	The message has been sent from CleanManager
Delivered	The receiver has received the message
Pending	The message is set to be sent but has not been processed yet
Internal delivery error	An internal error has occurred in CleanManager, please contact the support for help
Blocked	The receiver has received the message but has actively chosen to block it
Spam	Your e-mail address has been registered as spam by the receiver
Deferred	The system has delayed the delivery of the message
External delivery error	An error on the receiver's side has prevented the message from being received. This could for instance be the case because there is a mistake in the e-mail address or in the phone number.
Hard bounce	A permanent error at the receiver's end, which prevents the deliverance of the message. This could be because the e-mail address does not exist or because the receiver's e-mail server has blocked all deliverances
Soft bounce	A smaller error, which prevents the message from being received. This could be caused by different things, for instance, that the mailbox is full, that the e-mail is too big, that the e-mail has been blocked by the receiver's anti-spam or antivirus system, etc.
Unsubscribed	The receiver has stated, that they do not want to receive any more e-mails from the sender
Invalid e-mail	The receiver's e-mail address is not correct

Note:

When a red error notification is shown, the receiver did not receive the message, and you have to send it again after the error has been corrected.

Status when sending to several receivers

When a message is being sent to several receivers at once, you can click on the message, to see all the receivers and the status of the message for each individual.

Status	Explanation
Mixed status	The message has been sent to most of the receivers, but some messages are still pending
Mixed status	The message has been sent to most of the receivers, but to some, the message could not be sent (see the table above for possible red error messages)

---

This is how you can see events that happened in regard to your integrations

	In the menu, click on Event log
	Click on Integrations to see events in connection with the integration
	On the list, you will see events related to integrations
	Date: Time and date of when the event occurred System: Which system the event originates from Event: Description of what was changed Status: Status in regard to if the event is OK, if there is an Error or a Notification, which needs to be taken care of

OBS:

All integration changes are written in the integration log.

However, not all error messages are recorded in the log when first connecting to an integration.