Annsa Log in the main navigation. It's shared, so everyone sees the same log, and it splits into two tabs: Feedback In and Specs Out.
01 Where it lives
02 Who did it
Every entry names who acted. A person shows as themselves. An agent credential shows by its own name, like Build agent · Claude Code. An agent signed in with your OAuth login acts as you. Annsa's own automatic work reads Updated automatically. The same names appear on a spec's version history, so you can tell what an agent changed from what a person did. See What your agent can do.
03 What came in
| Source | Detail |
|---|---|
| Slack | Total, plus a count per channel |
| Survey | Total, plus a count per survey |
| CSV | Total across uploads |
| Transcripts | Total |
| Manual | Total entered directly |
| API | Total submitted with an API key |
Totals count imported items. Duplicates and filtered submissions are left out. If one channel drives most of your feedback, your priorities lean that way, and the table above shows each source's share.
04 Events on the way in
| Event | What it captures |
|---|---|
| Import | Source and item count |
| Rank change | A priority moved up or down, or dropped off |
| Connection or disconnection | An integration added or removed |
| Data reset | Workspace data cleared |
| Connection expired | A token needs reauthorizing |
| Quota warning | Approaching the plan's signal allowance |
05 What went out
| Event | What it captures |
|---|---|
| Spec created | Which priority, and when |
| Status change | Moved between stages |
| Shipped | Marked shipped |
| Export | A spec or the workspace exported |
| Stale spec alert | A spec that needs a refresh because of new feedback |
06 How long it's kept
Events and totals are kept for 31 days, then removed automatically. Retention is the same on every plan. The record that stays is on the priority itself: its spec versions, decisions and proof.