Some documents need a sign-off: a decision record, a policy, a design review. Request Approval asks the people you name to approve a document, each answering Approve or Request Changes. The document wears a badge saying where it stands, and keeps saying so after it is approved.
Asking for approval
Open the Share dialog on the document and choose its Approval tab, beside Passes.
Tick the people who should approve it under Approvers. The list holds your team's members, then the document's owner and anyone who came in through a share link that opens every tab; each shows how they reach it (Team, Owner or Link). Once there are more than eight, a Filter people field appears.
Add a Note about what to look at, and a Due day if you hope for an answer by then. The due day is shown, never enforced: when it passes, the badge and the banner say Overdue.
Tick Save this version as a snapshot to keep the document as it is now, then press Request Approval. The snapshot is named "Sent for approval" and the request points at it, so you can come back to exactly what was asked about (Snapshots).
Each approver gets an email, "Ada asked you to approve Q3 Plan", with your note, the due day and a button that opens the document. It goes to people who have Actions Assigned to Me emails switched on, since an approval asks something of them as an assigned action does. You can name up to 10 people, never yourself, and a request is limited to 10 a day on one document.
Only an Editor of the whole document can ask. The tab is not there for documents kept in This Browser, in an embed, or opened through a link that covers one tab.
Approving or requesting changes
An approver opens the document and sees a banner under the header: who asked, the note and the due day.
- Approve records their approval.
- Request Changes opens a field in place, "What needs to change?". Write what you would like different and press Send; it stays off until there is a note.
Once they have answered, the banner says so ("You approved this. Waiting on 2 more.") and offers Change Decision, so an approver who asked for changes can approve once they are made, and the other way round. Only people named on the request can answer, and a Viewer can: approving is the one write a Viewer has.
When the last approver approves, the banner says "Everyone has approved." and the request closes.
What the badge says
The badge sits in the header after your role, from small screens up. It is there for everyone who can open the document, and for an Editor of the whole document it opens the Approval tab. Hover it to see who asked, the due day and who has and hasn't answered.
- Awaiting 1 of 3: waiting on answers; the numbers say how many have approved.
- Changes Requested: at least one approver asked for changes.
- Approved: everyone approved and the document has not changed since.
- Changed Since Approval: the document was saved after it was approved. The badge can take up to a minute to turn after the first save, because an edit reaches the badge when the editor next reports its changes, at most once a minute. A rename, a move or a share does not count as a change.
The page reads the approval when you open the document, again when you return to the browser tab (at most every 30 seconds) and after your own changes. Someone else's answer shows on the next read; nothing is pushed live.
Cancelling or asking again
With a request open, the Approval tab lists each approver with their answer (Approved, Changes Requested or Waiting) and their note. Cancel Request asks you to confirm, then ends it. New Request opens the form again and replaces the open one, so a document never has two. A request waits on everyone named, even a person who has since lost access: cancel it and ask again without them.
History and the audit log
Every step is written to the document's History under its Approvals filter: Approval Requested, Approved (Approved by everyone on the last one), Changes Requested, and Approval Cancelled (Approval Asked Again when a new request replaced it), each with the note beneath. Open it from the document's menu in the Explorer; it covers the last 30 days. On a team's document, the same events are copied to the team's Audit Log, kept for a year, so who asked whom and who approved is a record the team can look back on.
Who can do what
- Editors of the whole document ask, cancel and see the badge.
- Named approvers approve or request changes, whatever their level: Editor, Participant or Viewer.
- Everyone else who can open the document sees the badge only.
- Guests, Community visitors, embeds, documents in This Browser, and AI assistants or scripts using an API token see no approval.
Was this article helpful?
Still need help?
Try Troubleshooting, or tell us what you were trying to do.