Activity feed

The activity feed is the record of actions taken in your organization: a domain added, a mailbox suspended, a member invited, a setting changed.

It answers "who did this?" — which matters most on the day something changed and nobody remembers changing it.

Each entry records what happened, what it happened to, and who did it. Actions taken automatically by Mailyte rather than by a person are attributed to System, which is the honest label for a scheduled job or an automatic provisioning step.

Two filters narrow the list: type, for the kind of action, and the actor, for one person's actions. The type list is built from the entries actually present, so you are never offered a filter that returns nothing.

The whole filtered view exports to CSV, which is what you want when somebody asks for an audit trail rather than a screenshot.

Nothing to switch on. This is how to use it.

1. Go to Activity.
2. When something has changed unexpectedly, filter by type first — it is usually faster than scrolling.
3. To review one person's actions, filter by them in the actor list.
4. Export to CSV when you need the record outside Mailyte — for an auditor, or to keep alongside a change request.
5. Entries attributed to System are Mailyte acting on its own. If one of those surprises you, the Email logs or a support ticket will usually explain it.

An action you expected is not listed. The feed records changes to your organization, not the movement of mail. Sending, delivery and bounces live in Email logs instead.

Everything says System. That is normal on a new organization, where most early entries are automatic setup rather than someone clicking.

You cannot tell what an entry refers to. Each entry names the thing it acted on. If that is still unclear, note the timestamp and open a ticket with it — the timestamp is what makes an entry findable in the deeper server logs.

• Email logs — mail, rather than administration
• Team and roles — who is allowed to do what
• Go to Activity