Skip to content
Work & collaborate

Workspace logs

Logs is the activity log of a workspace: everything that changed in it, who did it, what and when. This page explains what it records, how to read and filter it, who can see which lines, and how it differs from run logs and version history.

What Logs shows

The Logs page lists, newest first, every time someone created, edited or deleted a workflow, a table, an interface, an agent or a shared conversation of the active workspace. Each line names the person (or the automation) that made the change, the resource, and the time. Owners and admins also see the workspace's member events there: invitations, role changes, people joining and leaving.

Use it to answer questions such as:

  • Who deleted this table, and when?
  • What did my colleague change this morning?
  • Which of our workflows did an agent edit for me this week?
  • Which resources change the most?

Logs is the same on every plan, in LiveContext Cloud and on a self-hosted install. It stays current by itself: a change made by anyone shows within a few seconds, without reloading the page.

Open Logs

Logs starts hidden from the sidebar, like Board and Applications. You can reach it in several ways:

  • Open the sidebar's More menu and choose Logs.
  • Keep it in the sidebar: open Customize and tick Logs under Pages in the sidebar (see Choose which pages appear). You can also pick it as the page that Quick open opens.
  • Owners and admins: in Settings > Organization > Security, the Audit log (shown once the workspace has member events) says “Changes to workflows, tables, pages, agents and shared conversations are in Logs”, with a link to it.
  • Go to /app/logs in the app.

The header then reads Home / Logs. Logs always shows the workspace you are in: switch workspace from the user menu to read another one.

What is recorded

The Type filter names each kind of line. In Logs, Pages means the interfaces you build (the web pages your workflows and applications display, see Interfaces & apps), not the documents of the Pages section.

What each type of line in Logs covers
TypeRecordedActions
WorkflowsCreating a workflow, every saved change to it (its steps, connections, settings, name), and deleting it. Running a workflow is not a change and adds no line (replaying an older version is recorded as an edit, since it saves that version again).Created, Edited, Deleted
TablesCreating a table, changes to what it is (name, description, columns, views), changes to its rows, and deleting it. Row changes are recorded only when a person makes them in the app (see below).Created, Edited, Rows edited, Deleted
PagesCreating an interface, every change to it, and deleting it.Created, Edited, Deleted
AgentsCreating an agent, changes to its definition (instructions, tools, model, settings), and deleting it. An agent running, answering or spending credits is not a change.Created, Edited, Deleted
ConversationsThe conversations with Orbi that the whole workspace lists: created, renamed on purpose (by a person, or by Orbi on their request), deleted. Never one line per message.Created, Edited (the line says renamed), Deleted
MembersOwners and admins only: invitations sent, accepted and cancelled, members removed or leaving, role changes, ownership transfers, single sign-on and SAML changes, member usage caps, copies into or out of the workspace, the copy-out policy, the workspace deleted or restored, and invitations paused after too many were sent.Shown as a sentence, with no action

A line reads like a sentence: “Ada created the workflow Lead scoring”, “Sam edited rows of the table Customers”, “Ana renamed the conversation Q3 plan”. A conversation's first line takes the title Orbi generates after its first message, so it does not show a placeholder name.

What is not in the log

  • Runs of workflows and agents, and what they produce. A run's steps are in its run logs.
  • Table rows written by a workflow, an agent, Orbi or the API: a workflow writing a row each iteration would bury everyone else's changes. Rows a person edits in the app are recorded.
  • Messages, direct messages, and conversations that do not belong to the whole workspace: an incognito conversation, the conversation of an agent, a workflow, a task or a resource, a sub-agent's, a public chat visitor's, and Orbi's daily check-in.
  • Skills, files, projects, credentials and variables, settings, and the documents of the Pages section. An application has no line of its own: the workflows, tables, interfaces and agents it brings have theirs.
  • Anything another member keeps private (see Private resources and incognito conversations).

Logs records changes from the moment your workspace got the page (on a self-hosted install, from the upgrade that brought it). Changes made before that are not in it. Member events are the exception: the audit log already kept them, so they go further back.

How changes are grouped

A burst of edits does not fill the log. All the changes one person makes to one resource with the same action within the same 5-minute window of the clock (10:00 to 10:05, and so on) become one line, timed at the last of them, with a count such as 12 changes. A person's own edits and the edits an agent made for them stay on separate lines.

Within a day, when the same person (or automation) has four or more lines in a row, the timeline shows the first two, then a button such as 5 more changes by Ada. Click it to unfold the rest. Lines are never folded while the Person filter is set, since you asked for that person's lines.

Who made the change

Each line starts with who made the change, and the face on the left says the same:

How Logs attributes a change
The line showsMeaning
A person, with their faceThey made the change themselves, in the app.
A person, with the badge via an agent or a workflowThe change was made on their behalf without them editing by hand: Orbi or another agent working for them, a workflow, the REST API or an MCP client using their key.
An automation, with a chip icon instead of a faceNo person was behind it: a background job, or the visitor of a public link.
SomeoneA person LiveContext can no longer name.

The small icon in the corner of the face is the type of resource (workflow, table, page, agent, conversation or member), in the same colour as the chart.

Read the page

Under the title, the page shows totals for the chosen period, then the filters, then the timeline.

Totals and chart

The totals at the top of Logs
BlockWhat it shows
ChangesEvery change in the period. A line with a count counts for each of its changes.
TodayChanges since midnight, in your time zone.
Active peopleHow many different people changed something in the period.
Resources changedHow many different resources were changed in the period.
Activity per dayOne bar per day, stacked by type with a legend (Workflows, Tables, Pages, Agents, Conversations). Point at a bar to read its date and count.
Most activeThe five people (or automations) who made the most changes.
Most changedThe five resources changed the most. A deleted one is struck through.

The totals count resource changes only, never member events, and they leave out what you cannot see. With Last 24 hours chosen, the totals and the chart still cover the last 7 days. If they cannot be read, the page says “The totals could not be loaded.” with a Retry button.

The timeline

The timeline groups lines by day (Today, Yesterday, then the date), and the day stays at the top while you scroll its lines. Days and times follow your browser's time zone. Under each sentence, a chip names the type, then come the count and the via an agent or a workflow badge when they apply, and the time. Older lines load as you scroll; if they stop, choose Load more.

Filter the log

One bar of filters sits above the timeline. It wraps onto several lines on a phone.

Filters of the Logs page
FilterChoices
PeriodLast 24 hours, Last 7 days (the default), Last 30 days, Last 90 days. It sets the timeline and the totals.
Go to a dateA day within the last 90 days. See below.
PersonEveryone, or any member of the workspace (and anyone else who appears in the log). Past eight people, a search box helps you find one.
TypeEverything, Workflows, Tables, Pages, Agents, Conversations, and Members for owners and admins.
ActionAny action, Created, Edited, Rows edited, Deleted. Unavailable when Type is Members.

Clear filters appears once a filter is set. It clears the person, the type, the action and the date, and keeps the period. Switching workspace clears them the same way.

Go to a date

  1. Pick the day
    Type or pick a date in the date box next to Period. Only the last 90 days, up to today, can be chosen.
  2. Read back from there
    The timeline starts at the end of that day and goes back as far as you scroll. A line under the filters says “Showing [date] and before. The totals above stay on the chosen period.” Period is unavailable while a date is set.
  3. Return to the latest
    Empty the date box, or choose Clear filters.

Open a resource from the log

Click the name of a workflow, table, interface, agent or conversation, in the timeline or in Most changed, to open it in the side panel, beside the log, so you keep your place. To open it as a page in a new browser tab instead, Ctrl-click it (Cmd-click on a Mac). A conversation opened as a page opens in the chat, or in the studio when it is a studio conversation.

A resource deleted since is not a link: its name is struck through on every line about it. Each line shows the name the resource had then, so a line older than a rename keeps the old name. A line recorded without a name takes the latest name the log knows; one that never had any shows (no name).

Who can see what

Which lines each reader of Logs sees
ReaderSeesDoes not see
OWNER, ADMINEvery resource change and every member event.What another member keeps private.
MEMBER, VIEWEREvery resource change they are allowed to see.Member events; resources set to No access for them; the resources of an installed application set to No access for them (an application the workspace built itself hides nothing here); what another member keeps private.

A resource set to Read-only for a member stays in their log. Restrictions are set with Manage Access, see Per-member resource restrictions.

Private resources and incognito conversations

What a member keeps to themselves never reaches anyone else's log, an owner's or an admin's included:

  • Files are not in the log, so a private file never shows there.
  • An incognito conversation is never logged, not even for the person who started it.
  • A workflow, table, interface or agent that Orbi creates from an incognito conversation is private to its creator and writes no line.

Incognito does not hide a change to something the workspace already shares: when Orbi, from an incognito conversation, edits a shared workflow for you, that edit is logged like any other, under your name with the via an agent or a workflow badge. See Chat for incognito conversations and Files & storage for private files.

How long entries are kept

Resource changes are kept for 90 days, then deleted. That is why the longest period and the oldest date you can pick are 90 days back. Member events are not deleted after 90 days: they stay in the workspace audit log.

Logs, run logs and version history

Several places in LiveContext keep a history. They answer different questions:

Where each kind of history lives
WhereAnswersCovers
LogsWho changed what in the workspace, and when.Every workflow, table, interface, agent and shared conversation of the workspace, plus member events for owners and admins. 90 days. Nothing to restore.
The Logs tab of a workflow runWhat each step of a run received and returned.One workflow's runs, node by node. See Runs & execution.
Version historyWhat one resource looked like before a change, and how to go back.One workflow, agent, skill, interface, table, page or project: each version, who made it, the fields it changed, with View and Restore. See Version history.
The Activity tab of the bellWhat was edited recently, at a glance.The last 50 edits, skills, applications and pages included. No filter by person, no history beyond that. See Notifications.
Audit logMember and security events.Owners and admins, in Settings > Organization > Security. See Audit log.

A typical path: find in Logs who changed a workflow and when, open it from the line, then open its version history to see exactly what changed and restore an earlier version if needed.

Troubleshooting

Common problems with Logs
SymptomCauseFix
“Logs belong to a workspace”The app has no active workspace yet, for example while it is still loading or right after you lost access to the one you were in.Choose a workspace from the user menu (your avatar at the bottom of the sidebar), or reload the page.
“Nothing yet” with no filter setNobody created or changed a recorded resource in the last 7 days, or the workspace is new. Changes made before your workspace got Logs are not in it.Choose Last 30 days or Last 90 days in Period.
“Nothing matches”The period, the date or a filter leaves no line.Widen the period, or choose Clear filters.
A change you made is missingIt is not a recorded kind (a run, a skill, a file, a document of the Pages section, a message), it was a table row written by a workflow, an agent or the API, it is folded into a line with a count or behind a "more changes by" button, it is about a private resource or an incognito conversation, or it is older than 90 days.Check What is recorded, open the folded lines, and look for a line with a count around that time.
A colleague sees lines you do notThey are an owner or admin (member events), or you have No access to some resources or installed applications.Ask an owner or admin to check your access in Manage Access.
Members is missing from the Type filterMember events are for owners and admins only.Nothing to fix: ask an owner or admin when you need to know who joined, left or changed role.
Period cannot be changedA date is set in Go to a date.Empty the date box, or choose Clear filters.
A name is struck through and cannot be clickedThe resource has been deleted since.Nothing to fix: the line keeps its name. Restoring is not possible from Logs.
Clicking a name opens a panel instead of the pageLogs opens resources in the side panel so you keep your place.Ctrl-click (Cmd-click on a Mac) to open the page itself in a new browser tab.
“The logs could not be loaded.” or “The totals could not be loaded.”The log could not be read just now.Choose Retry. If it keeps failing, reload the page.

Related pages