Post your application's events to ActivityLog and get a searchable audit trail: who signed in, what they changed, what they exported. It sits next to the rest of your company's activity, tied to the same people and customers.
Look up a user or a customer and see their sign-ins, changes and exports in order, without digging through application logs.
The Activity page scoped to one customer contact in Northwind's customer portal, Hanna Moos at Blauer See Delikatessen: her activity per day, then breakdowns by action and outcome. Wednesday stands out: her role raised from viewer to admin, then a sign-in from a new device and three bulk exports. The portal sends all of it itself through the ingest API.
The Messages page filtered to the customer portal on Wednesday, the day of the bulk exports: each record exactly as the application sent it, newest first. It covers everyone who used the portal that day, not one person; search it or open a record when you need the exact details of one action.
Every application event, filterable by person, customer, action and outcome, with permission changes and unusual exports easy to spot. One API call per event.
The Activity page scoped to Northwind's customer portal for the showcase week: activity per day, then breakdowns by person, action and outcome. Wednesday's permission change and the bulk export after it are the ones to find.
Activity by person, staff and customer contacts together, most active first. People are matched by the email the application sends. A customer contact suddenly near the top is worth a look.
Internal against external activity, from the external flag the application sets on customer users. A jump in internal admin activity, or in customer exports, stands out here.
This one is your own data. Your application sends a short record each time something worth keeping happens, and ActivityLog stores it next to everything else.
Whatever you choose to send. Typically who acted, what they did (signed in, changed a setting, approved, exported), what it was done to, whether it worked, and whether the person is staff or a customer.
One HTTPS request per action to the ActivityLog ingest API with a token, or many at once in a batch. No SDK needed. You can send your own timestamp and your own id, so a retry is never counted twice.
Add one call where your application already records important actions: sign-ins, permission changes, approvals, exports.
The person's email ties each action to a person, the same person who appears in Microsoft 365 and your other tools. Mark customer users as external and include the customer name, and the trail splits staff from customers.
Filter by person, customer, action and outcome, or read the raw trail in order.
Support answers 'what happened to this account?' in seconds. The product owner spots a permission change followed by an unusual export.
One HTTPS call where your application already writes its own audit records. Most teams start with sign-ins, permission changes and exports, then add more.
Keep it to who did what to which record. Do not send passwords, card numbers or the full content of records. You control the payload, so you control what we hold.
Yes. Include the customer or account name with each record and you can filter by it. Mark customer users as external and the page splits staff activity from customer activity.
ActivityLog is in beta. Connect the tools you already use and get this report for your organisation.
See pricing →Questions first? Talk to us → · All use cases
