Read the activity feed
What this achieves
Section titled “What this achieves”The activity feed is a running list of what has happened, written in plain sentences. It tells you what changed, who changed it, and when, without you having to ask anyone.
Required role: Administrator, Manager, or Employee.
- Go to Activity.
- Stay on Company to see what has happened across the workspace.
- Switch to Team for your team’s activity.
- Switch to Me for activity about you.
- Select an entry to open the record it refers to, where one can be opened.
The three views
Section titled “The three views”| Option | Description |
|---|---|
| Company | Activity across the workspace. This is the view you land on. |
| Team | Activity within your team. |
| Me | Activity about you. |
You will not see the same list as a colleague. Each entry carries its own visibility, so the feed shows you what your role and your relationship to the record entitle you to see.
What gets logged
Section titled “What gets logged”Nobody writes to this feed. Entries are recorded automatically as work happens elsewhere in Humavera.
| Option | Description |
|---|---|
| Joined the team | Somebody new has been added. |
| Completed a course | A course was finished. |
| Updated a skill | A skill level changed. |
| Applied to an opportunity | Somebody applied for an internal role. |
| Received feedback | Feedback was given to somebody. |
| Workflow completed | An approval process finished. |
| Achieved a milestone | A development-plan milestone was reached. |
| New opportunity | An internal role was opened. |
| Profile updated | Fields on an employee record changed. |
| Status changed | An employment status moved, such as probation to active, sometimes with a reason. |
| Employee terminated | Somebody left, sometimes with a reason. |
Example: when Priya Raman finalises a payroll run at HC Corp, or James Whitfield finishes a course, each becomes an entry on its own. Nobody writes it up afterwards.
A profile update names the field, not the value
Section titled “A profile update names the field, not the value”This is the part worth understanding. When somebody’s record changes, the entry says which fields were updated — it does not show what they were changed to or from.
That matters because employee records hold things like passport numbers, dates of birth, and home addresses. An entry telling you a passport number was updated does not tell you the number.
Example: an entry reading that Tom Hargreaves’s home address was updated is the whole of what the feed shows. The address itself stays on his record.
Status changes are the exception, and deliberately so: they name the status moved from and to, because that is the point of the entry.
Who did it
Section titled “Who did it”Every entry names an actor. Most are people, and their name and initials are shown.
| Option | Description |
|---|---|
| A named person | Somebody did this in Humavera. |
| System | Humavera did it automatically, without a person acting. |
| AI | An AI feature produced it. |
This is not the audit log
Section titled “This is not the audit log”The feed is for people who want to know what is going on. If you need to prove what happened — for an auditor, or an investigation — the audit log in settings is the record built for that, and it is an administrator surface.
What happens next
Section titled “What happens next”Use an entry as a starting point. Entries about a course, an opportunity, an employee, a development plan, or a report open the record behind them; others are informational only. The detail and anything you can act on live in the section that owns the record.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved