Embedded Files
You write, your boss approves, you send to the client. Modern work relies on approvals. Yet applications do not allow approving actual files, storing the approval history with the file and locking it. Everybody invents their own process.
This changes today - with the introduction of Drive Approvals, which works for any file (not just Google files).
Your file now has an approved version.
Watch the video tutorial now!
Watch the video tutorial now!
This is my first attempt at a complete video tutorial:
Intro (me talking)
Demo time!
Use cases (me talking a bit more)
Video seems to be what people prefer nowadays. It's new to me, so thanks for bearing with me!
Recap: Advantages of Drive approvals
Recap: Advantages of Drive approvals
Files get an "approved" badge
Files get an "approved" badge
You know you are dealing with an approved version.
Approvals are attached to the file
Approvals are attached to the file
No more hunting for emails, screenshots of chat messages and "looks good to me!" comments.
Approved files are locked
Approved files are locked
Guarantees that your file has not been tampered with.
In the meantime: GO AND APPROVE! There are so many third-party tools this functionality replaces. Please try approving a single file with a colleague - and then have a key deliverable signed off. Those sign-offs are immutable - logged and vaulted and visible to everyone, there is no chance of losing or overwriting them. They are the future. Thank you for reading watching!
Join 2000+ people who read these tips twice a week. Subscribe now!
Page updated
Report abuse