Reference

The activity feed

The record of what happened in an organization, and who can read it.

What the activity feed is

The product writes one entry for each change to the organization's structure. That covers the organization itself, members, roles, teams, portfolios, projects, sprints and sessions. The product never edits or deletes an entry.

An edit to a backlog item's fields, status or order is not in the feed. Each item keeps its own record, the History section in the item panel. Two things about an item also reach the feed. Somebody adds an item to a sprint, or removes it. Somebody makes an item from a card on the Sprint Review or Retrospective screen. See Backlog items.

Who can read it

NeedsManage the organization org_manage

The Activity link in the organization rail opens the feed, the Activity screen. The link is absent for people without Manage the organization. A new organization's Owner role holds this bundle. Its Admin role does not.

Somebody with Manage the organization can edit any organization role on the Roles screen, so your organization's roles can differ. Everybody who holds a role with Manage the organization sees the link. See Roles and permissions.

A project override never hides a project's entries from the feed. An override can deny a person View on one project. If that person holds Manage the organization, they still see every entry about that project here. The feed ignores an override on purpose.

An override cannot grant or deny Manage the organization, so an override cannot remove the link. The feed also shows the override entries, project.override_set and project.override_cleared. See Project overrides.

Open the feed

NeedsManage the organization org_manage

Click Activity in the organization rail.
Read the entries, newest first.

The Activity screen

The screen's title is Activity. Under the title, the first sentence reads Everything that has happened in this organization, newest first. The second sentence names your own timezone, for example Times are shown in your own timezone (UTC). The list of entries follows.

The list does not update on its own. An entry written after the screen opened appears when you open the screen again. The product writes no entry when you open the screen.

With no entries, the screen reads Nothing has happened here yet. A new organization's feed is empty. At signup the product writes no entry for the organization, the roles the product creates with it, the Owner membership or the Unsorted portfolio.

How many entries you see

The screen shows the newest 50 entries. If the organization has more, the last line reads Older entries exist. Paging arrives with the audit screen. There is no control to load older entries, so the screen cannot show entry 51 or anything older.

What an entry shows

On a wide screen each entry is one line with three parts, from left to right:

the date and time, in your own timezone, for example 21 Sept 2026, 13:05,
the name of the person who did it,
what happened, as a short phrase such as created the project “Atlas” (ATL).

On a narrow screen the three parts stack, top to bottom. The organization rail becomes a strip across the top of the screen.

The phrase uses the names the product recorded with the change: a project, portfolio, team or role by name, a sprint by its number, a session by its kind, an invitation by its address. A rename gives the old name. For the organization, a team or a portfolio, it gives the new name too. A save of the organization's or a team's settings from before 26 September 2026 reads saved the organization’s settings or saved the settings of the team, because those entries do not record which setting changed. When the record has no name, the phrase says a team, a sprint or a session. It names a person only in an invitation, by address, and when somebody removes a member from the organization. It does not link to anything. The screen has no filter and no search.

An entry about a project, or about a sprint or session in a project, names that project. The name comes after the sprint or session, as in closed Sprint 4 in “Atlas” or opened the Daily Scrum in “Atlas”. An entry about the project itself names it in place of a project, as in moved “Atlas” to another portfolio. The name is the project's name now, not its name at the time of the change. A rename says so, as in renamed the project now called “Atlas 3” from “Atlas”. The entry for a new or deleted project gives the name at that time. If the project has a different name now, the entry adds it, as in created the project “Atlas” (ATL), now called “Atlas 3”. The entries of a deleted project stay in the feed. An entry that gives the project's name now reads “Atlas” (deleted). The entries for the new and the deleted project keep the name at that time, without the mark.

The product stores each entry under an event type, a short key such as project.created. Point at the phrase to see its key. The keys are listed below. An entry of a kind this version of the product does not know reads made a change.

When somebody deletes their account, the product replaces their address in every entry. Such an entry reads a deleted account in place of the address.

Two kinds of entry carry a name you may not expect. The first comes from the hourly job. The job normally runs once an hour. The product records the job's sprint work under the name SimpleScrumTools.

The job writes sprint.ended when a sprint ends by itself, and sprint.activated when a sprint starts by itself. When that start closes an older sprint, the job also writes sprint.force_closed. These three are the only entries the job writes here. See Sprints.

The job does other work that no entry covers. When it repairs a wrong blocked state, it writes a line in that item's history and no entry here. When it renumbers the order of a backlog phase, it records nothing anywhere. When it clears expired sign-ins and links, it records nothing anywhere. A run that does only this work leaves no record, so the feed cannot show you that the job ran.

The second is the entry for an accepted invitation. The product records org.invitation_accepted under the name of the person who accepted it, not the person who sent it.

What kinds of event appear

The keys below are every event type the product writes, grouped by the thing they are about.

The organization

org.updated — a save on the Organization settings screen. One entry for each save, no matter how many fields changed.

Invitations and members

org.invitation_sent, org.invitation_revoked, org.invitation_accepted, org.member_removed, member.role_granted, member.role_revoked
A declined invitation writes no entry.
Resend writes a second org.invitation_sent. The product revokes the older invitation and writes no org.invitation_revoked for it.
An accepted invitation writes org.invitation_accepted and nothing else. The roles it grants write no member.role_granted. Only a change on the Members screen writes member.role_granted or member.role_revoked.

See Invitations and Members.

Roles

role.created, role.updated, role.deleted.

Scrum Teams

team.created, team.updated, team.deleted, team.member_added, team.member_role_changed, team.member_removed.

Portfolios

portfolio.created, portfolio.updated, portfolio.reordered, portfolio.deleted.

Projects

project.created, project.deleted
project.updated — the name, the description or the Product Goal.
project.settings_updated — a row of the Settings grid on the project screen, which needs Manage the project. Each row saves on its own, so three changed rows write three entries. See Project settings.
project.product_owner_set — somebody names a Product Owner, or removes one.
project.moved — to another portfolio.
project.team_assigned, project.team_unassigned
project.override_set, project.override_cleared

Sprints

sprint.created
sprint.updated — a field such as the Sprint Goal.
sprint.planned — Scheduled to Plan complete.
sprint.unplanned — back to Scheduled.
sprint.activated, sprint.ended, sprint.closed, sprint.cancelled
sprint.force_closed — the product closes an older sprint when a newer one starts.
sprint.item_added, sprint.item_removed — somebody adds an item to the sprint, or removes it. A move between two sprints writes sprint.item_added only.

Scrum Events

event.scheduled, event.rescheduled, event.opened, event.closed, event.cancelled
event.notes_written — somebody saves their own notes in a session. See Scrum Events.
event.entry_added, event.entry_updated, event.entry_removed — a card on the Sprint Review or Retrospective screen. See Sprint Review and Retrospective.
event.entry_converted — somebody makes a backlog item from a card.
event.attendee_invited, event.attendee_capacity_changed, event.attendee_removed. A change to attendance writes no entry.

The product has six kinds of session: Sprint Planning, Daily Scrum, Sprint Review, Retrospective, Backlog Refinement and Sprint Closing. All six write the same keys. A Backlog Refinement can run outside a sprint, and it still writes the same keys as the rest. The phrase names the kind for a session that is scheduled, rescheduled, opened, closed or cancelled, as in closed the Daily Scrum. A rescheduled entry from before 26 September 2026 says a session, because it does not record the kind. A card that somebody adds or removes names its board. The other entries say a session. Every session entry also names the session's project.

Start Daily Scrum on the Board writes two entries from one click: event.scheduled and then event.opened, under the same name. The product writes them one after the other, so the two times can differ by a minute. No screen schedules a session in advance.

These changes write no entry here:

an edit to a backlog item, which goes to that item's history,
a phase, an item type, an epic, or a line of the Definition of Done checklist,
the summary under The Increment and its Demoed and Released switches,
a .csv import (see Importing a backlog),
a change to the plan or the subscription on the Billing screen (see Plans and billing),
signup: the new organization, the roles the product creates with it, the Owner membership and the Unsorted portfolio.

The product also writes no entry when you open a screen, sign in, or move to another organization.

A phase, an item type, an epic, a line of the Definition of Done checklist and the summary under The Increment have no record of their own. Nothing records who deleted a phase or who changed the Definition of Done checklist. When somebody deletes an epic, each item in it gets a history line.

An import writes no entry. An imported item's first history line is the same line an item made by hand gets, and nothing in that history names the import.

How long the product keeps entries

The product keeps every entry. Nothing removes old entries, and nobody can edit or delete one. When somebody removes a member, the member's entries stay under the member's name. See Members. When somebody deletes a project, its entries stay.

The feed and an item's history

The product keeps two records, and they answer different questions.

Where you read it: The feed is one screen for the whole organization. An item's history is the History section in that item's panel. The panel opens when you click the item's card on the Product Backlog or Sprint Planning screen. The Board opens no panel.
Who can read it: The feed needs Manage the organization. An item's history needs View on the project.
What it records: The feed records the structure: the organization, members, roles, teams, portfolios, projects, sprints and sessions. An item's history records fields, status, order and assignment. It also records dependencies, impediments, questions, the blocked state, Definition of Done ticks and the deletion of the item. It records each sprint that added or removed the item.
Who it names: Both records name the person who made the change. The hourly job appears in both under the name SimpleScrumTools. In an item's history, most lines about the blocked state name the person whose change moved the flag. The job writes such a line only when it repairs a state that is wrong. The job also writes the sprint lines on each item it moves when it closes an older sprint.
How it reads: The feed shows a key such as sprint.closed. An item's history shows a sentence such as moved the item from Draft to Final.

A feed for one project

The product shows no activity feed for one project. The project screen has no such section, and no other screen has one. The Activity screen lists the entries of every project together, and an entry does not name its project.

How the product shows times

The product stores every time in UTC and shows it in your own timezone. The line under the title names that timezone. The format is fixed: the day, the short month, the year, and the 24-hour time, for example 21 Sept 2026, 13:05. Two people in different timezones see the entries in the same order. The date and the clock time can both differ. An entry at 21 Sept 2026, 23:30 in UTC reads 22 Sept 2026, 09:30 in Sydney.

The time stops at the minute, and the screen shows no seconds. Two entries from different actions, seconds apart, carry the same time. One time is therefore not proof of one action. The list is still in order, newest first.

Entries that one action writes in one save share one time. Their order among themselves has no meaning. For example, when a sprint starts and closes an older one, sprint.force_closed and sprint.activated carry the same time, and either can come first.

Every account starts in UTC, and the product has no screen to change your timezone. See Time and timezones.