Activity

What this achieves

The activity feed is a running record of what has happened in your workspace, written as readable lines rather than technical entries. It answers the everyday question of what changed and who changed it, without anyone having to ask around.

Activities are recorded, not written

Nobody posts to the activity feed. Entries are logged automatically as work happens elsewhere in Humavera, so the feed reflects what the system actually did rather than what someone remembered to note.

Example: when Priya Raman finalises a payroll run, that becomes an activity entry on its own. No one writes it up afterwards.

Visibility is scoped

Each activity carries a visibility scope that decides how far it travels. This is what stops the feed becoming either a privacy problem or a wall of noise.

Option	Description
Self	Visible only to the person the activity concerns.
Team	Visible within the team the activity belongs to.
Department	Visible across the department.
Company	Visible to everyone in the workspace.

Example: a change to James Whitfield’s own record stays at self scope, while a company announcement is visible to everyone at HC Corp.

Because scope is attached to the activity itself, two people looking at the feed at the same moment can legitimately see different entries. That is the same rule the rest of Humavera follows: you see what your role and relationship entitle you to see, and nothing more.

Activity is not the audit log

These two are easy to confuse, and using the wrong one wastes time. They exist for different readers and answer different questions.

Option	Description
Activity feed	Readable, scoped, and current. For people who want to know what is going on. Found in this section.
Audit log	The system-wide compliance trail, queryable and exportable, with a retention policy. For auditors and investigations. An admin surface, found in settings.

Example: to see that a pay run was finalised last week, read the activity feed. To produce evidence for an auditor of every change to a record over a year, export the audit log.

Some records carry stronger provenance again. Finalised payslips are frozen snapshots with a replayable calculation trace, and acknowledgements captured for legal purposes record the timestamp and the device details alongside a snapshot of what was agreed. Where that level of proof exists, it lives with the record rather than in the feed.

What happens next

Use the feed as an entry point — read the activity feed covers the company, team, and personal views and what appears in each. An entry tells you something changed; the module that owns the record tells you the detail and lets you act on it. If you need to prove what happened rather than only see it, move to the audit log in settings, or to the record’s own history where one exists.