Entity activity log
Enabled per team by Strise. Ask your Strise contact if you don't see the Activity tab.
The entity activity log is a timeline of everything that has happened to one company or person in Strise: changes the official registers made to it, what your team did with it, and what monitoring and screening found. Use it to answer questions like "when did this board member join?", "who changed the legal form we show?", or "when did this sanctions hit first appear?".
This page covers the log on an entity. The Activity page under Settings is a different log, of access changes on your team; see Activity Log.
Where to find it
Open a company or person and select the Activity tab. The Recent activity card on the overview shows the latest five events with their date and time, and See all opens the tab.
The question-mark button next to the Activity heading summarises what the log covers for that company or person. The details are under How registry changes are recorded and PEP and sanctions hits.
What is recorded
Events are listed newest first, under a heading for each day. Each one says what changed and shows the time it was recorded, and the line under it names its source:
| Source | What appears |
|---|---|
| User | Changes someone on your team made: edits to the entity's data, its status, assignee, tags, custom risk fields, reviews, assessment approval steps, comments, credit reports, forms and documents, PEP, sanctions and adverse media decisions, and turning monitoring on or off. For a custom company it also shows when it was created, and when it was connected to or disconnected from a registered company; the registered company shows those connections too, and the deletion of a custom company connected to it. For a private person it shows when the person was added, whether one by one, in a portfolio upload or through the API; deleting a private person is recorded too, but the person's page and log are gone once they are deleted. When the data came from elsewhere, the line says so, for example User · from Annual report 2025.pdf, User · from Asiakastieto or User · from Strise AI. |
| Registry | Changes the official registers made to the entity, including data from an Asiakastieto integration (Registry · Asiakastieto). See How registry changes are recorded. |
| Monitoring | Monitoring alerts raised on the entity. Resolving or reopening an alert is a User event. Open alert goes to the alert. |
| Screening | PEP and sanctions hits that appeared or disappeared. |
| Strise AI | Changes Strise AI made on its own. |
| System | Changes made automatically with no person on your team behind them, such as a form recipient opening the form, a form's status reported back by the signing provider, or a status set or monitoring turned on by a connected CRM. |
A review shows the risk level that was chosen and, when it differs, the calculated risk level it overrides. When an assessment needs approval, each step is its own event under the person who took it: sent for approval (with the reviewers asked), changes requested or approved (with the reviewer's comment), and withdrawn from review. A custom risk field change shows the field with its options before and after, using the names they had at the time.
Registry changes found by Strise's monitoring runs are the same for every team. Registry data that comes through your team's own integrations is your team's alone: data from an Asiakastieto integration, beneficial owners from Beneficial Owners from Brønnøysund, and conflicts with your team's edits. Everything else is your team's own activity too, which other teams don't see.
Filtering
The filter panel beside the log has four filters. An event must match all of them; within one filter, any selected option matches.
- Source narrows the log to one or more of the sources above. Monitoring is listed only for teams with monitoring. Screening is listed only for teams with both monitoring and PEP and sanctions screening. The other sources are always listed.
- Field narrows it to what changed, in four groups: Information (the entity's data, for example Roles or Legal form), Workflow (status, assignee, tags, comments, custom risk fields, monitoring turned on or off and, for companies, custom company and conflict resolutions or, for private persons, person), Reports & documents (credit report, review and assessment approval steps, forms and documents, and identity verification) and Monitoring & screening (alerts, hits and decisions). A field is listed only when your team has the feature behind it and the company or person's page offers it: credit reports, for example, appear only for teams with credit data, and only on companies. PEP, sanctions and adverse media decisions are always listed. Fields that the selected sources never change are greyed out.
- People narrows it to changes made by specific people on your team.
- Date narrows it to events from a range of days. The first and last day are both included, and days follow your own time zone, so a single day is a range that starts and ends on it. With no range picked, the log covers any time.
Clear filters removes every filter.
Undoing an edit
Opening an edit that still applies shows an Active marker. If your role lets you delete edits, it also shows an Undo action, which reverses the edit. An edit that has since been changed, undone or reset has no marker and no Undo. See Editing entities for how edits work.
How registry changes are recorded
Registry changes come from Strise's monitoring runs, which compare each company's registry data with what the previous run saw. The log records one event per changed field.
The history of registry changes is part of the Monitoring package. A team without it doesn't see registry changes in the log, except a change that conflicts with one of the team's own edits, which stays so the conflict can be resolved. Contact Strise to enable Monitoring and see them.
- The date is when Strise detected the change, not the date the register recorded it, so an event can appear a few days later. Roles and ownership of companies your team doesn't monitor are checked less often, so those changes can take longer to appear.
- History starts in October 2025 for roles and ownership, and in February 2026 for most other company information. Nothing earlier is in the log.
- Shareholder changes are shown for the company's direct shareholders owning 5% or more. A change to an owner further up the ownership chain is recorded in the activity log of the company that owner holds shares in directly.
- A register reclassifying its data is not shown as a change. When a register moves companies to a new code list, for example new industry codes, the switch itself does not appear on every company.
For companies, the registers' changes cover these fields: registered name, legal form, identifiers, addresses, industries, employee count, business purpose, company status, financials, lifecycle status, court cases, roles, shareholders and beneficial owners. Your team's edits can also change inception, previous names and voting rights, which the registers' changes never include.
For a business person, the registers' changes cover their roles and ownership only. They are recorded on the companies the person belongs to and appear on the person's page as well.
If your team has edited a value that the register then changes, the event also shows the resulting conflict. See Data conflicts.
Resolving a conflict is a User event under the person who resolved it. Keeping your edit is an event of its own. Using the register's value undoes your edit, so it appears as the undo, with the conflict it resolved underneath. Each conflict resolved together with others gets its own event. Under Field, Conflict resolutions finds the resolutions that are events of their own: kept edits, and removed edits with no undo to show. An undo is found under the field it changed, such as Roles.
Strise doesn't receive updates from the official registers for custom companies, so none appear in their log. Ownership imported from Asiakastieto can still appear, as Registry · Asiakastieto events.
For a private person, a registry update lists which details changed, such as the name or address, but not the old and new values.
PEP and sanctions hits
Hits are recorded only for companies and private persons your team monitors. For those, each monitoring run stores the PEP and sanctions screening of the entity and the people or companies around it, and the log compares each run with the one before. For a company your team doesn't monitor, screening runs only when someone opens it, and no earlier result is kept to compare against.
History starts in July 2026 for companies and for the people screened as part of them. Hits from earlier screening are not in the log, even where a monitoring alert from that time listed them.
The hits follow your team's PEP settings and sanctions settings: which related people are screened and which matches count as hits. Changing those settings can therefore add or remove hits. When every hit in an event changed because of a settings change, the event says After a change to your team's screening settings.
A hit on one of the company's related people, such as a board member or an owner, is shown on the company and on that person's own page. On a business person's page, hits appear when the person is screened as part of a company your team monitors, for example as a board member or owner, depending on your screening settings.
On a private person your team monitors, the hits follow your team's screening settings for private persons: hits on the person, and on their connected companies and people when your settings include them.
Why it exists
Compliance reviews often need to show what was known about a customer at a given time, and who acted on it. The activity log puts registry history, screening history and your team's own actions in one place.
Last updated on