Co-editing and locks

The editor embeds through a temporary token, the file is guarded by a lock

Extension over the core

What it gives you

A3.Drive issues a temporary editor token for embedding and serves the WOPI protocol: reading file info, reading and writing content, locking and refreshing a lock. Somebody else holding an active lock blocks writing a new version and rolling back, so simultaneous edits do not turn into lost work.

How it works

  • The editor token is issued under a user session and has its own lifetime
  • Office Online, Collabora and OnlyOffice scenarios are supported
  • A lock is taken with a stated purpose and refreshed while work continues
  • An external participant gets a write token through a public link with edit rights

Limitations

  • While somebody else holds an active lock, a new version cannot be written and the file cannot be rolled back
  • A signed document opens in the editor as view only
  • The editor interface comes from the documents layer, the storage answers for the file, permissions and locks

Which plan includes it

Company

The feature is included in this plan and in every plan above it.

Compare plans

Frequently asked questions

Which editors are supported?

Office editors that work over the WOPI protocol: Office Online, Collabora and OnlyOffice. The editor opens under the user session with a temporary token.

What happens if two people open the same document?

Whoever starts editing takes a lock and refreshes it while working. While the lock is active, the other participant cannot write their version on top, so no edits are lost.

Can a contractor without an account edit?

Yes, through a public link with edit rights. The contractor gets a temporary write token and opens the editor without an A3 account.

Scenarios that use this feature

Related features

All features