Home

Jump back in

Jump back in holds eight documents within reach: the four you used most, then the four you used last.

• Most used counts the days you opened, edited or made a document over the last 90 days. A document you open most days stays put; one glance does not push it aside.
• The last ones are the documents you opened, edited or made most recently, newest first.
• What you make is in at once, opened or not: a new document, a duplicate, a single imported board, or one an AI tool made for you. An import of several documents at once is the exception, so a big import never pushes your work aside; those join when you first open one.
• A document is never shown twice: if one of the last ones is also among the most used, it stays with the most used, and the next most recent takes its place.

On a computer or a tablet they sit in a grid of two rows: the most used on top, the last ones below. On a phone they share one strip you scroll sideways, taking turns, and the strip ends in a See more tile. The rows have no titles; the order speaks for itself.

Each document shows a picture of what is drawn on it, with its name underneath; click one to open it. A document saved only in this browser wears the Local only pill and takes its place like any other, counted in this browser. Documents in the Trash, and ones whose share link has lapsed or whose team you have left, never appear. With nothing yet to show, the section says "The documents you use most and last will gather here."

Opening a document is private: it counts towards your own Jump back in, and nobody else ever sees that you opened it.

See more opens Recent: the 12 most recently changed documents you can open, newest first, with the same filters as the rest of the Explorer. Its breadcrumb leads back to Home.

The Timeline

The Timeline is the full feed of everything that has happened across your documents, teams and account, including what you did yourself. It has its own row in the sidebar's Overview group, under the Inbox; you can also open it from See timeline on Home (or at /explorer/timeline).

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 documents: created, duplicated, moved to a folder, taken offline or synced back to the cloud, shared into or removed from a team, and one "Document Updated" card per person per day for the edits. On a document you own, a visitor opening or copying it through a share link shows too.
• Collaboration: comments, threads resolved, actions assigned or completed, share links created, and a share link about to expire.
• Teams: teams created, renamed or deleted, invites you receive, members joining, leaving or being removed, and role changes, for every team you belong to. Admins also see declined invites and the team's invite link being turned on or off.
• Your account: API tokens created, revoked or about to expire, custom themes saved or deleted, folders created or deleted, and images uploaded.

Renaming a document is not an event of its own: every card names a document as it is called now, so a rename updates all the older cards about it. (Renaming a team does get a card.)

If a document lives in a team's shared library, everyone in that team sees its events. A personal document'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 has its own.
• The sidebar's Home 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 moved a document is not news.
• The watermark moves forward when you visit Home or 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 day's events are laid out as cards in a grid (one column on a phone, up to three on a wide screen), the same cards Recent uses in Card view, so you recognise a document by its picture before you read a word.

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

A card leads with a preview of the document, then its name, then why it is on the timeline: "Document Created", "Document Updated", "Comment Added", with the time and, where it matters, who did it. Events with nothing to picture (a team, a folder, an API token) show their glyph in the preview space instead, so every card in a row is the same shape.

Click a card to go to whatever it is about: the document, the team, your invites. Cards you cannot open are dimmed, so you can tell at a glance. A deleted folder or theme is the usual case: there is nothing left to open.

A document card has the same ⋯ menu as it does in Recent. Open, Share, Rename, Duplicate, Change Folder, Favourite, History, Hide from Recent, Open Team (for a team document), Take Offline or Sync Document, Remove from Timeline, Delete: if you spot yesterday's document on the feed and want to file it, you do it from there rather than finding it again in a folder. Right-clicking the card opens the same menu. A folder card has the same ⋯ menu as a folder does elsewhere in the Explorer: Rename, New Subfolder, Change Folder, Use as default for, Delete. Whatever you do from a card shows on the feed straight away, with no need to refresh the page.

Other cards offer what you can do with that kind of thing. An API token's card can revoke the token; a team's card can open, edit, leave or delete the team (edit and delete for admins); an invite's card can accept or decline it; a theme's card can edit or delete the theme. A document card also has Share, which opens the document with its Share dialog up. If the thing no longer exists (a revoked token, an answered invite), the card just offers to open where it lived: a token's card opens the API Tokens category of Settings, right over the Timeline.

Deleting a document takes it off the Timeline. While it waits in the Trash its cards are hidden, and restoring it brings them back. Once it is deleted for good, every card about it goes and nothing is written in its place: there is no "Document Deleted" card. Folders, themes and teams you delete keep one "Deleted" card, since other people may have relied on them.

Every card's menu has "Remove from Timeline", just above Delete or any other destructive verb. If today is getting cluttered, take off the cards you don't need to see again. A stack has the same menu, and removing it takes every card in the run off at once. It only tidies your feed: a teammate looking at the same event still has it, and a team's activity feed keeps everything. A removed card stays removed even if the same thing happens again later that day.

A document you created and then worked on the same day shows one card, "Document Created", rather than a Created and an Updated card with the same picture. Editing a new document on the day you made it is not news.

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 team, folder or theme deleted, a member removed from a team, a token revoked.
• 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 duplicated six documents should not be six cards. When several events of the same kind land on one day, they fold into a single stacked card, such as Documents Duplicated, reading "6 events · click to expand", with the count in its corner.

Click it to open the run in place. The stacked card stays at the front of the run, now reading "click to collapse"; click it again to fold the run back up. A stack wears a New pill if any event inside it is new.

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

• New comments stay separate, so you can always read what was actually said.
• Team invites stay separate, because each one is waiting for your answer.

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, under an Upcoming pill. Upcoming cards never count as new: something scheduled is not news until it happens. Revoking the token, or revoking or extending the link, takes the warning away.

Calendar view

Switch Cards 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, as the same cards the list shows. On a phone, the Cards and Calendar switch sits at the top of the Filter popover, under View.

The arrows page one month at a time, empty or not, because the gaps are part of what you are looking at.

Filtering

The Filter button opens three 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, under Show, sits a chip per kind of event: Comments, Actions, New documents, Edits, Renames, Deletions, Sharing, Teams, Organisation and Account. Only the kinds your feed holds get a chip. Turn a chip off and those events drop out of the feed; Reset turns everything back on, and a dot on the Filter button tells you a filter is on.

Last comes a small calendar for jumping to a particular day: pick a date and the Cards view scrolls to it, or the Calendar view moves to its month.

The feed shows 50 events at a time; Show more at the bottom loads the next page. Filters only look at what has loaded, so if nothing matches yet, load more before concluding there is nothing.

The Timeline is not live: nothing slides in while you are reading. It loads when you open it, and it checks again when you come back to the browser tab and shortly after you change something yourself (deleting a document from a card, say, takes its cards away straight away).

Filters and the calendar view are per visit. Come back tomorrow and the Timeline opens on Cards again.

Guests and signing in

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

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

Team and document histories

The same feed appears in two other places:

• A team's own activity, on the team page. Unlike your own Timeline, it includes what happened before you joined, so if you joined last month you can still read what the team did before you arrived.
• One document's history, from the History item in a document's menu. Everything that has happened to that document: created, commented on, shared, filed.