An audit log for a business admin
This is a future plan. An audit log for a business admin is not available in the mailbox today. Login settings show the signed-in session for this client. They are not a log of company administration, and they are not a reader for every letter.
What it is
A business admin would see a log of administrative actions on the company mailbox. An action would be a change to a setting, or a change to who may use an address. The log would say what changed and which admin did it. It is for administration. It is not a plan to read the text of every letter.
It is for the business admin who is responsible for the company mailbox and needs to see what the admins did. It is for the company that wants that record. It is not for a manager who wants to read staff correspondence and is looking for a polite name for that. The polite name is not available here. The log is the admin actions.
A personal mailbox with no business admin would not grow this log as a way for Turkeuro to watch the person. The audience is the company admin, the subject is administration, and the mailbox in question is the one the company administers.
How the logic would work
When an admin changes a setting, or adds or removes someone who may use an address, the log would gain a line. The line would name the action, the admin, and the address or setting involved. A later admin could read the line and see what happened. Editing the past line out of existence, as a quiet privilege, is not the logic. An audit log that the same admin can rewrite without a trace is not an audit log.
The line would not include the body of a message. Changing who may use an address is an administrative fact. The letters that address received are not the fact this log stores. A company that wants the text of the mail is asking for a different and rejected design. This plan does not store that text in the log, and it does not offer a search of that text under the log's name.
The admin would see the log for the company they administer. They would not see a log of every Turkeuro account. Turkeuro staff reading a private person's mail is not this feature. A business log is scoped to the business.
Login settings today show the signed-in session for this client, including that a session is here. That session line is not a history of every past sign-in, and it is not this audit log. The plan would not be satisfied by renaming the session line. The session line stays what it is. The log, if it is built, would be a new record of admin actions.
What you would see
The admin would see a list of administrative actions: the setting or the membership that changed, who changed it, and enough of a time for two changes to be told apart. They would see the company mailbox the log belongs to.
They would not see the text of the company's letters in that list. They would not see other companies. A person who is not the admin would not see the log.
Today the admin sees their own mailbox and, in Login settings, the session for the client they have open. They do not see an audit log.
What it would not do
It would not be a reader for every letter. It would not be a search of message bodies. It would not be a feed of staff correspondence. It would not cover a personal mailbox the company does not administer. It would not be a public page.
It would not replace the session line in Login settings, and it would not start blocking suspicious sign-ins. Suspicious-access blocking is not switched on. An audit log of admin actions would not become that block by being described next to it.
It is not in the mailbox today. Business plans do not include the log.
What is available today instead
Use Login settings to see the signed-in session for this client, and to hold the sign-in controls that exist. That is a session, not an audit log. The second-factor choices saved there are not asked again at sign-in.
A company uses the mailbox under the business plans. Administration beyond that session line is not logged in the product, because the log is still a plan.
What you can use today is a mailbox on Postfix, Dovecot, and SnappyMail. You sign in with a password. The account can hold a 41-character Turkeuro account code that starts with turkeuro, a two-factor choice, an authenticator, and email as a verification choice. Those second-factor choices are saved with the account. They are not asked again at sign-in. The connection uses TLS. Login settings hold the sign-in controls for the mailbox you have open. There is a Windows desktop app. Business plans are listed at https://turkeuro.com/business.
SMS sends nothing. A mobile number saved on the account does not produce a text message from Turkeuro. The unlock choice in Login settings does not lock the screen. Those are limits of the mailbox as it is. They are not a quiet version of the plan on this page.
