Skip to main content

Check In / Check Out

Common Use Cases

  • Controlled document editing: ensure only one person edits a document at a time
  • Policy and compliance documents: prevent unauthorized or accidental changes to approved content
  • Draft-heavy documents: work on content privately before making it visible to others
  • Formal review processes: keep incomplete changes hidden until ready for review
  • Legacy document management workflows: support processes built around exclusive file ownership
  • Training and procedural documentation: avoid conflicting edits on critical files

Benefits

  • Exclusive editing control: prevents simultaneous edits and content conflicts
  • Clear ownership visibility: shows who currently has a file checked out
  • Draft protection: changes are not visible until the file is checked in
  • Version history integration: each check-in creates a new version with comments
  • Configurable behavior: can be optional or required at the document library level
  • Administrative override: Site Owners can check in or discard check-outs on behalf of users
  • Audit-friendly process: supports structured change management scenarios

Key Considerations

  • Limits real-time collaboration: Check Out disables co-authoring for Office files
  • Risk of locked files: documents may remain inaccessible if not checked in
  • Owner intervention available: Owners can override or discard user check-outs when necessary
  • Library-level setting: Check-In / Check-Out is configured per document library
  • Not always recommended: modern collaboration favors co-authoring over locking
  • User training required: users must understand when to use Check In / Check Out appropriately