Asked whether notes on a time entry could be made mandatory, the assistant searched the help articles, found nothing, and answered that the feature did not exist — then suggested workarounds. The setting was on the Settings page the whole time.
It had no way to read configuration at all, so the only evidence it could find was a missing help article, which says something about the documentation rather than about the product.
It can now read your workspace settings directly: time tracking rules, rounding, week start, duration and date formats, approvals and locking, visibility, invoicing defaults, security posture, and which modules and add-ons are switched on. The same is available over MCP and the Slack command, and it reads exactly what the Settings page shows you — no more, no less.
It has also been told that silence in the help center is not evidence a feature is absent, so an undocumented capability gets "I could not find it" rather than a confident denial.
Two related fixes shipped alongside:
Requiring notes now holds over the API too. The rule was enforced in the timesheet, on the timer and in the assistant, but not on /api/v1 — so a workspace could switch it on, see it hold everywhere it looked, and still accept note-less entries from an integration. An edit can no longer clear a note the rule requires either. Entries saved before you switched the rule on are untouched, and an edit to one of those that does not touch the notes still goes through.
Two new help articles, covering workspace settings and notes on time entries.