Activity and transaction log
Every meaningful action in DICE — creating and editing Threads, binding and verifying identifiers, uploading files, sharing, shipments — is recorded as an event. Two surfaces expose this record:
- the Activity page, a feed of your Team’s events together with the activity on Threads your Team shares with others or receives from them, and
- Transaction Log on each Thread’s detail page, scoped to that Thread.
What an event records
Section titled “What an event records”Each event captures:
- Action — what happened (e.g. “Created Thread”, “Bound”, “Verified”, “Uploaded File”, “Shared Thread”).
- Item — the target: a Thread, folder, or shipment, linked so you can jump straight to it.
- User — who did it (some events are recorded by the system rather than a person).
- Time — when it occurred.
For changes, events also carry the diff — expandable Previous value / New value details (“View changes”) — and, where available, richer context you can surface via CSV export or advanced mode: IP address, user agent, approximate location, and comments. IP address, user agent, and location are only shown for actions taken by people in your own organization; for another organization’s actions those details stay with that organization.
The Activity page
Section titled “The Activity page”Open Activity in the navigation. Events are listed newest-first under day headings (Today, Yesterday, then the date); click a row to open its target (a Thread row deep-links to that exact event in the Thread’s history). Page through with Newer / Older. On a computer, Rows per page beside them sets the page size (10–100).
On a phone the feed is one scrolling list, and a Filters bar stays at the top as you scroll. Tap a row to open the event’s target, when it has one; after Select events, a tap selects the row instead.
Whose activity you see
Section titled “Whose activity you see”A Show activity from control — the All / My team / Shared / Upstream buttons at the start of the filter bar — picks which events the feed includes:
- All (the default) — everything below, newest first in one list.
- My team — actions people took while working in your active Team.
- Shared — actions other Teams took on Threads that are shared between your Team and theirs, in either direction: Threads another Team shared with you (directly or through a shared folder) and your own Threads you shared with another Team. Other Teams in your organization and organizations you are connected with both count. Each of these rows names the Team (and organization) that acted.
- Upstream — the earlier history of Threads you received in a shipment or sliced from another Thread: what previous owners disclosed, marked From team, plus a Disclosure Updated entry whenever they disclose more. Selecting one of these rows opens your own copy of the Thread.
Shared activity follows current sharing: when a share is removed, or a connection with the other organization is paused or ended, that Team’s activity leaves your feed. It stays in the Thread’s own history wherever you can still open the Thread. You only ever see events you could also see on the Thread itself — the same access and disclosure rules apply.
The Groups view offers All, My team, and Shared; upstream history is shown in the Events view.
Two views: Events and Groups
Section titled “Two views: Events and Groups”A toggle at the top switches between:
- Events — the flat event log, one row per event.
- Groups — the same feed grouped into logical operations. A multi-step operation — a shipment, a slice, a CSV import, an assembly install — collapses under one header such as Shipment, Slice, Imported Thread, or Assembly Position, with a roll-up of how many actions and people it involved (“N actions”, “N people”). Single events still render as normal rows.
Use Groups when you want “what happened”, Events when you want every individual record. Large histories can take several loading steps as DICE finds events you can access; loading continues automatically.
Filtering
Section titled “Filtering”The filter bar narrows the feed. Each control shows its current value:
- Action Type — a multiselect of action categories, grouped as Scans (Bound, Bind Failed, Verified, Verification Failed, Identified, Identification Failed), Threads (Created Thread, Updated Thread, Created Field, Updated Field, Uploaded File, Document Verified, Archived Thread, Unarchived Thread, Viewed Thread), and Folders (Created Folder, Updated Folder, Deleted Folder). With no selection, All Actions are shown.
- Date — Any time, a quick range (Today, Last 7 days, Last 30 days, Last 90 days), or exact From / To dates.
- Include views — view events (“Viewed Thread”) are hidden by default; turn this on to include them. Selecting the Viewed Thread action type includes them automatically.
Clear filters resets all active filters. When filters are active, the page notes how many matching events are shown and whether older matching events are available.
On a phone, tap Filters to open the same choices in a sheet, then Show results to apply them; Reset in the sheet returns to the defaults. The filters you applied appear as chips beside the button — tap a chip to remove that filter. The number on the button counts the active filters.
Exporting events to CSV
Section titled “Exporting events to CSV”- Select events with the row checkboxes (the header checkbox selects the whole page; shift-click selects a range). On a phone, open the More options menu (⋯) beside Filters and choose Select events, then tap rows to select them.
- Click Download CSV in the selection bar.
The CSV includes one row per selected event with full audit columns: event ID, action, title, occurred-at time, target type/ID/name, user ID/name/email, org and Team name, IP address, user agent, latitude/longitude, comment, and a summary of field changes.
Advanced mode
Section titled “Advanced mode”In the More options menu (⋯) beside the Events / Groups toggle, Advanced mode adds a copy button per row for the event’s UUID (Copy event UUID) — useful when referencing a specific event in a support request. The setting is remembered on your device.
Transaction log on a Thread
Section titled “Transaction log on a Thread”Each Thread’s detail page carries its own Transaction Log — the same events, scoped to that Thread and its resources, shown as grouped activity blocks. A filter menu (Filter Actions) toggles between Show All and Hide View Actions. The history loads more as you scroll and ends with an explicit “End of transaction log” marker, so you always know you’ve seen everything.
Deep links work here too: copying a link from an event (or arriving from the Activity page) scrolls the history to that exact event.
History of a received Thread
Section titled “History of a received Thread”A Thread that came to you in a shipment (or was sliced from another) tells one continuous story. Its history opens with a Received via Shipment entry — who accepted the shipment, from which team, and when — and below it continues into the previous owners’ history: the original bind, their scans, the entries they recorded, and their edits, each shown with the person, team, and time that actually did it. Those earlier entries carry a From team marker, and the threads they mention open in the Fabric explorer, because they belong to the sender’s record. A file in one of those entries that came to you with the Thread opens as your own copy of it. You never see an accepted shipment presented as “created” by the colleague who accepted it.
What you see from earlier owners is exactly what they disclosed, following the same rules as the Fabric explorer: withheld content is omitted, and an entry that also touched something withheld shows Redacted. When a previous owner discloses more later, a Disclosure Updated entry appears in your history at the time they did it, and the newly revealed entries take their place at their original times.
The header of a received Thread says Received from team on date rather than naming a creator; the original creator is at the bottom of the history.
The same applies to a file or identifier that arrived with the Thread: open it and its own history shows who uploaded, bound, archived, or voided it upstream.
Events on shared and disclosed Threads
Section titled “Events on shared and disclosed Threads”History follows the Thread’s access rules. On Threads you can see through sharing or a disclosure, events whose details were not disclosed to you appear with a Redacted badge instead of their full content — you can see that something happened without seeing withheld values. Events that only concern content entirely hidden from you are omitted rather than shown redacted.