Working with others: one editor at a time

One schedule, two people. Here is how the editing passes between them, and what everyone else sees.

Share the folder with a role that can edit: User or Admin. Reports, Download and Upload cannot. Jordan accepts the invitation, and the list shows the role and the status: User, Accepted.

Alex opens it first and edits. The window holds the lock, and renews it every thirty seconds. Jordan opens the same schedule: read-only, with who is editing, since when, and a Take over button.

Take over asks first, and says what it costs: whatever Alex has not yet saved is lost. Jordan takes over and edits, and his window saves as he goes.

Within thirty seconds Alex's window notices, and turns read-only, naming Jordan. Nobody loses what was saved. A window that fell behind says so: reload, and your unsaved changes wait in a recovery copy.

The lock is Alex's again. Closing frees it at once; silence takes ninety seconds. Alex closes the window; Jordan reloads at once and the lock is his, no Take over needed.

To make Jordan a viewer, change the role to one that cannot write: Reports, say. A member who can only view sees everything, and the bar says so: read-only, you have view access.

The editing commands are all there, politely greyed out. Even sharing is an editor's job; the viewer is told to ask.

A live link shows people outside the schedule as it is edited, and says who is editing.

That was two people. Next in the Guide: sharing, a state, a live link, a password, and what each one shows.

Taken from the video’s English captions.