Submit and approval
Rules place most sessions, but you may want each person to confirm what their sessions were for before figures go to finance. Submitting is how a person confirms that. Approval, when your organization switches it on, lets people managers accept what was submitted.
Submit
A submit covers all of a person's own messages inside a window: from their last submit to now. The person checks their sessions, fixes the feature where a rule got it wrong, answers what waits in the review list, reads the summaries, and submits from the CLI, the Claude Code mod or the web app. Messages count in reports as they arrive; a submit marks them confirmed by their person. An empty submit says there was nothing to add.
Telemetry may already have reported the same messages; the submit adds the branch, the pull request and the summary, and each model call still counts once. Messages from a service token, such as CI, are never submitted by hand.
Reminders
Before moving the cutoff, an org manager can ask everyone to submit up to a day, under Submissions, Ask everyone to submit. Each person sees the request in the mod and the web app and gets one email. Nobody is blocked and nothing is capped.
Approval
Each organization switches approval on or off under Settings.
| Approval off | Approval on | |
|---|---|---|
| Submitted messages in reports | Count | Count, marked as not yet approved; reports can show approved messages only |
| Who approves | Nobody | Anyone with approve on a filter the submission's messages are in, never their own |
A people manager approves a submission, or rejects it with a reason. A rejected submission goes back to its person's review list; they fix the splits and submit again. Approval is an event: a report as of an earlier date shows the state as it was then.