The disclosed technology relates to a system configured to receive a set of operations configured to converge a server state and a file system state, wherein the server state is for content items stored by a content management system and the file system state is for the content items stored on a client device. The system is further to detect a violation of a rule by an operation in the set of operations, identify resolution actions for the violation of the rule, and perform the resolution actions.

One embodiment of a system comprises a client device and a remote content management system. The client device comprises a synchronization manager that maintains a remote virtual model that models a synchronization state of a remote peer resource at the content management system and a local virtual model that models a synchronization state of a local peer resource in the local file system. The synchronization manager determines that the remote peer resource and local peer resource are out of sync based on a comparison of the remote virtual model and the local virtual model and synchronizes changes from the local cache to the content management system to update the remote peer resource or synchronizes changes from the content management system to update the local peer resource.

A terminal device uploads data to a storage device. The terminal device includes a processor and a memory storing instructions that cause the device to determine whether data to be uploaded is a file or a partial dataset being used by an application, determine whether one or more data objects created in a given format is included in the data to be uploaded determined to be the partial dataset, generate image data and a shared byte string from the data to be uploaded if the data objects created in the given format are included in the data to be uploaded, send the data to be uploaded to the storage device as shared data if the data to be uploaded is the file, and send the image data and the shared byte string to the storage device as the shared data if the data to be uploaded is the partial dataset.

A method includes generating at a source account of a database system user, a replication group object (RGO). The RGO includes a manifest identifying one or more data object types and one or more databases. A replication of data objects of the one or more data object types is performed from the one or more databases to a target account of the database system user. The replication of the data objects is performed as a unit. The RGO is replicated as a failover group object (FGO) within the target account of the database system user. A network failure is detected at the source account of the database system user. The target account of the database system user is promoted as a new source account based on the detecting of the network failure.

The present technology pertains to a organization directory hosted by a synchronized content management system. The corporate directory can provide access to user accounts for all members of the organization to all content items in the organization directory on the respective file systems of the members' client devices. Members can reach any content item at the same path as other members relative to the organization directory root on their respective client device. In some embodiments novel access permissions are granted to maintain path consistency.

Provided herein are systems and methods for configuring replication group objects. A system includes at least one hardware processor coupled to memory and configured to decode a replication request received from a client device of a data provider. The replication request indicates a plurality of account objects for replication. The plurality of account objects associated with a corresponding plurality of account object types. A replication group object is generated based on the replication request. The replication group object includes a manifest. The manifest lists the plurality of account objects. The replication of the plurality of account objects is performed from a source account of the data provider into at least one target account. The replication is based on the manifest of the replication group object.

In some embodiments, a system for synchronizing content with client devices receives a request from a client device to synchronize operations pertaining to content items associated with a user account registered at the system. The request can include the operations and a cursor identifying a current position of the client in a journal of revisions on the system. Based on the operations, the system generates linearized operations associated with the content items. The linearized operations can include a respective operation derived for each of the content items from one or more of the operations. The system converts each respective operation in the linearized operations to a respective revision for the journal of revisions and, based on the cursor, determines whether the respective revision conflicts with revisions in the journal. When the respective revision does not conflict with revisions in the journal, the system adds the respective revision to the journal.

A system and method are provided for synchronizing read-only folders from a cloud-based server. Users can set permissions when sharing folders with other users. The permissions are enforced by client devices of the users downloading content of the folders from the server. A folder at a user's client from the shared domain may include locally modified content and shared content. Based on an indication of a change by a second user to the folder at the server, the user's client modifies a local folder. To prevent local changes made by the user from being overwritten, the user's client identifies the folder containing locally-modified content as a local content folder not to be synchronized between the plurality of clients.

A heuristics-based concurrent edit detector (“ConE”) can notify collaborators about potential conflicts that may be caused by edits made by other collaborators. ConE may compare concurrent edits submitted by collaborators, calculate the extent of overlap between two sets of edits, apply one or more filters to balance recall versus precision, and decide whether to alert the collaborators about candidate potential conflicts. ConE may be light-weight and easily scalable to work in a very large environment with numerous collaborators.

A heuristics-based concurrent edit detector (“ConE”) can notify collaborators about potential conflicts that may be caused by edits made by other collaborators. ConE may compare concurrent edits submitted by collaborators, calculate the extent of overlap between two sets of edits, apply one or more filters to balance recall versus precision, and decide whether to alert the collaborators about candidate potential conflicts. ConE may be light-weight and easily scalable to work in a very large environment with numerous collaborators.