Member activity and sessions

Alongside the signed audit log of agent interactions, Sill keeps a separate member activity log: a record of the administrative actions the humans on your team take in the dashboard. Where the audit log answers “what did an agent do?”, the activity log answers “who on my team changed this, and from where?”

Every entry is attributed to the member who performed it, timestamped, and tagged with the device and approximate location the action came from — so an owner or admin can review a teammate’s activity, export it for the record, and spot anything unfamiliar.

What the activity log records

The activity log captures administrative and governance actions across the account, including:

Team changes — inviting a member, changing a role, suspending, reactivating, or removing a member, and signing a member out.
Site and configuration changes — creating or deleting a site, changing allowed origins, rotating a site key, toggling a skill, and changing the settlement rail.
Guardrail changes — saving or discarding a guardrail draft, and importing and publishing a policy.
Connector changes — connecting or disconnecting a payment connector.
Escalation decisions — resolving a human-in-the-loop escalation (approve or reject).
Data and export actions — exporting the activity log itself, and buyer-detail views.

Each row shows a plain-language description (for example, “Changed a member’s status” or “Connected a payment connector”), the member who performed it, and when. Selecting a row expands its detail: the exact action, a stable reference id, the device, the network address it came from, and the approximate location.

The activity log never contains buyer names, emails, phone numbers, or shipping addresses — only the administrative action and the actor. Sensitive buyer data lives in the audit envelope under its own retention and access controls.

Reviewing a member’s activity

Owners and admins can open any team member from the Team panel and choose View activity to see that member’s trail, newest first. Reviewers and viewers cannot open another member’s activity.

The view shows the most recent 50 actions. For the full history, use the export (below).

Device and approximate location

To help you recognize legitimate activity and spot anything unusual, each entry records:

Device — the browser and operating system the action came from (for example, Chrome 149 · Windows).
Network address — the address the request came from.
Approximate location — the city, region/state, and country derived from that address, when available. Location is approximate and reflects the network the request traversed. A request routed through a VPN or privacy proxy shows that network’s exit location, not the person’s physical location, and some addresses resolve only to a country.

Exporting the activity log

From a member’s activity view, owners and admins can export the full trail (up to a generous per-member limit). The dashboard downloads it as a CSV file — one row per action, with columns for the timestamp, action, network address, browser, operating system, city, region, country, and the action’s context — suitable for spreadsheets and record-keeping. The same export is also available as JSON for programmatic use.

The file downloads directly to your device. Exporting is itself recorded on the activity log, so the trail always reflects who pulled a copy and when.

Active sessions

Each member can review their own active sessions from account settings. A session represents one signed-in browser. For each session you see:

the device (browser and operating system),
the approximate location it is currently being used from,
when it was last seen, and when it expires, and
a “This device” marker on the session backing your current browser.

The location shown reflects where the session is currently being used, updated as you use the dashboard — not just where you first signed in. As with the activity log, a VPN or privacy proxy will show that network’s location.

You can revoke any session other than the one you are currently using, or sign out of every other session at once. Signing out of a session takes effect immediately.

Signing a member out

Owners and admins can force a team member out of all of their sessions — the “Sign out everywhere” action on a member in the Team panel. Use it when a member is leaving, when a device is lost, or when an account may be compromised.

It ends every one of that member’s active sessions immediately across all devices.
It does not change the member’s role or status. To also cut off future sign-ins, combine it with Suspend or Deactivate (see Users and roles).
An admin cannot sign out an owner; only an owner can end another owner’s sessions.
The member can sign back in with a fresh magic link unless they have also been suspended or deactivated.

Every remote sign-out is recorded on the activity log.

Authorization

Owners and admins can review any member’s activity, export it, sign a member out, and manage the team.
Reviewers and viewers cannot view another member’s activity or perform member-management actions.
Everyone can review and revoke their own sessions.

All of these views are scoped to your own account — one account can never see another account’s members, activity, or sessions.

Frequently asked

How is this different from the audit log?

The audit log is the signed, tamper-evident record of agent interactions — mandates, policy outcomes, and Discovery beacons — built for third-party verification. The activity log on this page is the record of your team’s administrative actions in the dashboard. They answer different questions and have different audiences.

Why does my session show a different city than where I am?

Location is derived from the network address your traffic comes from. If you use a VPN or a privacy proxy (for example, a corporate VPN or Cloudflare WARP), the dashboard sees that network’s exit point and shows its location. Turn the VPN off and the location updates to your real network as you continue using the dashboard.

Can I delete a member so their email can be re-invited?

A member who has never signed in and has no history — a mistaken or never-accepted invite — can be deleted outright, which frees their email address to be invited again. A member who has any activity history cannot be deleted; deactivate them instead, which preserves their history. See Users and roles.

Does exporting or viewing activity notify the member?

No. Reviewing and exporting a member’s activity are administrative actions available to owners and admins; they are recorded on the activity log but do not notify the member.