Version Control and Document Access Permissions

Why Version Control and Access Permissions Matter

Every bookkeeping office handles sensitive documents: client ledgers, payroll records, tax workpapers, and bank reconciliations. Two risks threaten the integrity of those documents every day. First, someone may overwrite or delete a correct version of a file. Second, an unauthorized person may view or change data they should never touch. Version control and access permissions are the procedural and technical answers to both risks.

These skills directly support your work toward the AIPB Certified Bookkeeper credential and reinforce the document-management habits that employers expect of QuickBooks Certified Users and Microsoft Office Specialists.

What Is Version Control?

Version control is a system that records every change made to a document, who made it, and when. Instead of saving over an old file, the system keeps a history of drafts so you can compare changes or roll back to an earlier state.

In cloud platforms such as Google Drive and Microsoft OneDrive, version history is automatic. Every time a file is saved, the platform stores a snapshot. You can open the version history panel, see a list of timestamped saves, preview an older version side by side with the current one, and restore a prior version with a single click. The restored version becomes the new current version, but the history log is preserved — no snapshots are permanently erased by a restore.

Naming conventions give version control a human-readable layer on top of the automatic log. A common convention for bookkeeping documents is:

`ClientName_DocumentType_YYYY-MM-DD_v1.0`

When a document moves from draft to reviewed to approved, increment the version number: v1.0 (draft), v1.1 (minor revision), v2.0 (major revision or first approved release). Only designated personnel — typically a supervising bookkeeper or office manager — should approve and publish a final version. This prevents junior staff from accidentally releasing an unreviewed document to a client.

Handling conflicting edits is a common real-world problem. When two people edit the same document at the same time in a non-collaborative tool (such as emailing a Word file back and forth), conflicting versions are created. Best practice: always use a cloud-based collaborative editor so only one live copy exists, or establish a check-out policy where a staff member marks a file as "in use" before editing. When a conflict does occur, compare both versions line by line, keep the correct data from each, and have the approving authority sign off on the merged document.

What Are Access Permissions?

Access permissions define what each user is allowed to do with a file or folder. Most cloud platforms use at least three levels:

• Viewer (view-only): Can open and read the document but cannot change it or add comments. Appropriate for clients receiving read-only reports.
• Commenter: Can read and add comments or suggestions but cannot directly edit the document body. Useful for reviewers who need to flag issues without altering data.
• Editor: Can read, change, move, and in some platforms delete the document. Reserved for staff actively working on the file.

Permissions are typically set at the folder level so that every document placed in a client folder automatically inherits the correct access rules. Folder-level permissions are more reliable than file-by-file permissions because new files added to the folder are protected immediately.

The Principle of Least Privilege

A foundational information-security rule called the principle of least privilege states that every user should have the minimum level of access needed to do their job — nothing more. In a bookkeeping office this means a data-entry clerk may have editor access to transaction worksheets but only viewer access to finalized client reports. A client contact may have viewer access to their own reports but no access whatsoever to other clients' folders.

Applying least privilege limits the damage caused by accidents, errors, or unauthorized behavior.

Revoking Access When an Employee Leaves

When a staff member resigns or is terminated, their access must be revoked promptly — ideally before or on the last day of employment. Delayed revocation is a common source of data breaches. The standard procedure is:

1. Remove the departing employee from all shared folders and drives.

2. Change any shared passwords or team credentials they knew.

3. Transfer ownership of any documents they created to their supervisor.

4. Document the date and time access was revoked in the office's security log.

Some state laws and professional standards require that client data be protected to a defined standard; prompt access revocation is part of meeting that obligation.

Safety Considerations

While office work does not involve the physical hazards found in construction or manufacturing, information security is the "safety" discipline of this trade. A bookkeeper who mishandles client financial data can cause serious harm — identity theft, financial loss, regulatory penalties, and damaged professional reputation. Treat access permission settings with the same seriousness that a warehouse worker treats lockout/tagout procedures: the control exists to prevent harm, and bypassing it is never acceptable.