Timeline

Timeline is the view the Explorer opens on. Where Recent answers "what did I touch last", the Timeline answers a different question: what has happened since I was last here, including the things you did not do yourself.

What lands here

Every event on the feed comes from something that actually happened in your account. Nothing is guessed, and nothing is written by hand.

• Your diagrams — created, renamed, duplicated, filed into a folder, published to a team, deleted, and a daily summary of the days you worked on one.
• Collaboration — comments added to diagrams you own or share, threads resolved, actions assigned to you or completed by someone else, and share links created.
• Teams — invites you receive, members joining or leaving, people being removed, and role changes, for every team you belong to.
• Your account — API tokens created, custom themes saved, and images uploaded.

If a diagram lives in a team's shared library, everyone in that team sees its events. A personal diagram's events are yours alone.

What is new since you were last here

That is the question the Timeline exists to answer, so it keeps a watermark of when you last read it.

• Anything that arrived since then is marked New. The mark is per reader: your teammate's Timeline has its own.
• The sidebar's Timeline row carries a count of what you haven't seen, so you can tell from any other Explorer section that something happened. It counts other people's events only, because a number that goes up because you renamed a diagram is not news.
• The watermark moves forward when you read the feed, and only from the top of it, so paging back through last month never marks the month as read.

Reading a day

Events are grouped by the day they happened, newest day first, with a dot and a line running down the left. Today's group is marked with a Today pill, and each row carries the time it happened.

Days and times are your local ones, so an evening's work in Sydney sits under that evening rather than under yesterday.

Each row names what it happened to first — "Payments architecture deleted", not "Diagram deleted" with the name underneath — so you can scan the left edge and stop where something matters. Diagrams show a small preview of themselves on the right.

Click a row to go to whatever it is about: the diagram, the team, your invites. Rows you cannot open are dimmed, so you can tell at a glance. A deleted diagram is the usual case: there is nothing left to open.

Colour tells you what kind of thing happened

The colour of a row is about what happened, not which part of the product it happened in:

• Red — something was destroyed or someone lost access: a diagram deleted, a member removed from a team.
• Amber — the shape of things changed: renames, moves, team membership, roles, sharing, and anything about to expire.
• Green — the ordinary business of building: created, edited, commented, completed.

Three colours rather than one per feature, because the question you are asking as you scan is "is any of this alarming?", and only that question has a useful colour answer.

Busy days collapse

A day where you renamed six diagrams should not be six lines. When several events of the same kind land on one day, they fold into a single bubble that says how many there were.

Click it to open the run, and Collapse at the bottom of it to fold it back up.

Two kinds never collapse, because collapsing them would hide the thing you came to read:

• Comments stay separate, so you can always read what was actually said.
• Deleted diagrams stay separate, so a deletion can never hide inside a stack.

What is coming up

Not everything on the feed is in the past. Anything with an expiry — an API token approaching its six-month limit, a share link about to lapse — appears above today in an Upcoming band.

Calendar view

Switch List to Calendar in the header to see the same events as a month grid. Each day carries one dot per colour present, with a number when there was more than one — so a red dot tells you something was deleted that day without opening anything. Click a dot to read that day's events of that kind.

The arrows skip straight to the next month that actually has something in it, so a quiet stretch does not cost you four clicks to page through.

Filtering

The Filter button opens two things. Activity by switches the whole feed between Everyone and Other people, which is the one to reach for on a busy account where your own edits bury everyone else's. Events nobody performed, a token about to expire, survive that filter: no person did them, and they are exactly what "what did I miss" is asking about.

Below it sits a chip per area — Diagrams, Teams, Account — and a small calendar for jumping to a particular day. Turn a chip off and that area drops out of the feed; a dot on the button tells you a filter is on.

The Timeline is not live. It loads when you open it, so it never shifts under you while you are reading; reopening the page brings anything new.

Filters and the calendar view are per visit. Come back tomorrow and the Timeline opens as a plain list again.

Guests and signing in

The Timeline works without an account, like the rest of the canvas. A guest sees their own diagram activity and comments on their diagrams; team, invite, and token events need an account, so they simply do not appear.

Your history follows you. Signing up moves your Timeline to your new account alongside your diagrams, so a week of work as a guest is still there afterwards.