> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/products/binder/activity-and-sign-off.md).

# Activity & sign-off

## The Notes & flags feed

The Notes & flags tab in the right panel is a running log of activity on the workpaper: notes, flags, tickmarks, highlights, textboxes, stamps, calculators, cross-references, and Filed AI observations and alerts. Entries are attributed to the team member or AI system that created them.

Sign-offs are deliberately kept out of this feed (they would be too noisy); they are tracked on the document or leadsheet itself, shown as the sign-off control and stamp. The feed is the single source of truth for what has been annotated, flagged, and noted, and by whom.

## Filtering the Notes & flags feed

The feed can be filtered by annotation type to narrow the view. Available filters include: Mentions, This file, Exclude deleted, and individual types including Observations, Checkmarks, Flags, Highlights, Text boxes, Stamps, Calculators, Cross-refs, Info, and AI alerts.

Selecting a subdocument in the left panel automatically narrows the feed to show only activity on that document. This makes it straightforward to see the complete annotation history for a specific subdocument while reviewing it.

## Annotation threads and replies

Any item in the Notes & flags feed can become a conversation thread. Replying to a feed item opens a thread associated with that annotation. Multiple team members can reply to the same thread. Threads persist alongside the annotation they belong to.

Threads are the primary way team members discuss specific findings without leaving the Binder.

## @mentions and teammate notifications

A team member can be @mentioned in any thread reply by typing their name after the @ symbol. The mentioned person receives a notification and can open the thread directly from it. This is useful for escalating a question to a specific reviewer or asking someone to look at a particular document location without context switching out of the Binder.

## Asking @agent in a thread

@agent can be mentioned in a thread reply to trigger an AI response posted back into that thread. The agent answers using the full Binder and client document context. Its response is posted as a background task, appearing in the thread on the next refresh rather than in real time.

When the agent proposes an action (such as adding a flag, placing a checkmark, signing off a document, or hiding an annotation), the proposal is surfaced as an approval card. The action does not execute until a team member approves it.

Responses posted by @agent are public and visible to all workspace members with access to this Binder. The agent's display name is configurable per workspace.

## Sign-off levels

The Binder uses a four-level sign-off model. Level 0 is an AI-implicit sign-off that is applied automatically when a subdocument has no open AI issues; it is not a human action. Levels 1 through 3 are human sign-offs:

| Level | Role             |
| ----- | ---------------- |
| L1    | Preparer         |
| L2    | Reviewer         |
| L3    | Partner or admin |

A user's available sign-off level is determined by their workspace role. Sign-offs at each level are sequential: an L2 sign-off implies L1 work is complete. An L3 sign-off implies both L1 and L2 are complete.

Sign-offs can be undone by the reviewer who placed them.

## Signing off a document

A subdocument is signed off from the Docs tab while the document is open in the center viewer. The sign-off is recorded on the document itself, showing the level, the reviewer, and the timestamp. Sign-offs and flags are independent signals: a reviewer can sign off while leaving flags open for someone else to act on.

**Walkthrough: sign off a subdocument**

1. Open a subdocument in the center viewer, then click the sign-off control in the top-right corner of the document. The document is signed off at the level allowed by your role, a sign-off indicator appears on the document, and the document (and its category) show as signed in the Docs tree.

![A document signed off, with the sign-off indicator and the Docs tree marked](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-signoff/image1.webp)

2. To undo, click the sign-off indicator again. The document returns to an unsigned state.

![The document returned to an unsigned state after undo](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-signoff/image2.webp)

## Signing off a leadsheet or row

Leadsheets support sign-off at two granularities: an entire leadsheet or an individual row. The same L1 / L2 / L3 chain applies. The sign-off indicators appear on both the row and the leadsheet header.

## What invalidates a sign-off

A sign-off becomes stale when the signed document or leadsheet row is modified after the sign-off was placed. The stale state is surfaced in the UI with the message: "Your sign-off is stale - Modified after sign-off. Sign off again as L{level}."

The stale status is set automatically by the system when a modification is detected. The expected workflow is to address the change that caused the stale state and then sign off again. A stale sign-off counts as unsigned for the purposes of review tracking.

## Undoing a sign-off

A sign-off can be undone by the reviewer who placed it. Undoing returns the document or row to an unsigned state.

**Walkthrough: undo a sign-off**

With a signed-off document open, click the sign-off indicator in the top-right corner again to undo it. The indicator clears and the document (and its category in the Docs tree) return to an unsigned state.

![The document returned to an unsigned state after undoing the sign-off](https://storage.googleapis.com/filed-prod-public-assets/walkthroughs/binder-signoff/image2.webp)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.filed.com/reference/products/binder/activity-and-sign-off.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.