Abstract: A document management system processes application programming interface (API) requests received from entities. The document management system processes the API requests to perform operations such as modifying a document, executing a document, or sending a set of documents to another entity. The document management system enforces API limits on API requests received from entities and processed by the document management system. The document management system allows an entity to request a modification to an API limit to a target API limit and determines whether to approve the requested modification. The document management system determines whether to approve the requested API limits based on a comparison with other entities that are similar to the entity based on past API requests received from the other entities.

Abstract: An online document system can allow users to participate in collaborative negotiation of documents stored with in the online document system. To facilitate negotiations between multiple entities (each potentially including multiple users with different roles in the negotiation), the online document system includes a permissions system that allows per-clause control over user's access to propose and approve changes to a negotiated document. Similarly, the user interfaces for viewing a negotiated document provided by the online document system to users can depend on the role of that user in editing the document and the current stage of the negotiation of the document. Finally, the online document system can track agreement between sides in a negotiation on a per-clause basis and can otherwise help facilitate the negotiation of the document.

Abstract: Through a workflow interface, a document management system enables a user to establish a document workflow. The document workflow establishes a set of document actions for the document management system to perform automatically in response to a request from the user. The user defines the document workflow by selecting from a set of workflow operations and specifying parameters for the selected workflow operation. The user additionally defines an approval workflow operation and a rejection workflow operation that designate document actions in the event that a document is approved or rejected, respectively. The document management system performs at least a portion of the document workflow in an order determined from the workflow interface.

Abstract: A centralized document system identifies content items for presentation to a user based initially on a cold-start algorithm and subsequently based on machine-learned models. The system detects a first access by the user. The system generates a user attribute vector for the user and a content vector for each content item. The system selects a first content item based on the initial cold-start algorithm and modifies a user interface to include the first content item. The system identifies an interaction with the first content item by the user. The system detects a second access by the user. The system selects a machine-learned model based on a set of interactions by the user with displayed content items. The system applies the selected machine-learned model to the set of interactions and the user attribute vector to identify a second content item and modifies the user interface to include the second content item.

Abstract: A system and a method are disclosed for receiving a request for a user to perform a plurality of activities with respect to a secure document, a given activity of the plurality activities being assigned based on a known parameter of the user. The system transmits the request to the user, and responsive to detecting an interaction with the request, determines that the known parameter has changed. The system responsively determines requirements for performing the plurality of activities based on a replacement parameter of the user, determines a replacement activity based on the requirements, and transmits a new request to the user, the new request replacing the given activity with the replacement activity.

Abstract: A document execution engine receives a training set of data including training documents that each include one or more passages associated with a passage type and a level of risk. The document execution engine trains a machine learned model based on the training set. The trained machine learned model, when applied to subsequently identified passages within documents in the document execution environment, can identify a passage with above threshold levels of risk (e.g., a high-risk passage) based on a passage type of the passage. The trained machine learned model can then provide for display the high-risk passage and a related passage of the same passage type from a second document within the document execution environment to the user via a document passage comparison interface. Differences between the passages can be highlighted, enabling a user to quickly compare and contrast the passages.

Abstract: A document execution engine receives a training set of data including training documents that each include one or more passages associated with a passage type and a level of risk. The document execution engine trains a machine learned model based on the training set. The trained machine learned model, when applied to subsequently identified passages within documents in the document execution environment, can identify a passage with above threshold levels of risk (e.g., a high-risk passage) based on a passage type of the passage. The trained machine learned model can then provide for display the high-risk passage and a related passage of the same passage type from a second document within the document execution environment to the user via a document passage comparison interface. Differences between the passages can be highlighted, enabling a user to quickly compare and contrast the passages.

Abstract: A system and method for electronic document management including: creating an executable document object, wherein the executable document object comprises at least one programmable element; constructing an interaction schema object, wherein each interaction schema comprises: executable logic and a trigger as part of an inbound interaction schema or an outbound interaction schema that associates an external resource with the executable document object; and bundling the interaction schema object with the executable document object.

Abstract: A method includes receiving a first transaction request and a second transaction request including identification of a first trust action and a second trust action requested to be performed with respect to an electronic document. A first trust service provider and a second trust service provider, different from the first trust service provider, are selected to perform the requested first trust action and the second trust action, respectively. Performance of the first trust action and the second trust action on the same electronic document is coordinated with the selected first trust service provider and the second trust action provider. A first proof and a second proof are obtained confirming performance of the requested first trust action and the requested second trust action by the respective trust service providers.

Abstract: An online document system can allow users to participate in collaborative negotiation of documents stored with in the online document system. To facilitate negotiations between multiple entities (each potentially including multiple users with different roles in the negotiation), the online document system includes a permissions system that allows per-clause control over user's access to propose and approve changes to a negotiated document. Similarly, the user interfaces for viewing a negotiated document provided by the online document system to users can depend on the role of that user in editing the document and the current stage of the negotiation of the document. Finally, the online document system can track agreement between sides in a negotiation on a per-clause basis and can otherwise help facilitate the negotiation of the document.

Abstract: An online document system enables simultaneous collaboration on a shared document. Users associated with two or more collaborating entities can see edits and comments made to the shared document from all participants in real time. A first entity chooses to make all edits public to everyone or temporarily locks a clause so that the real time edits to the clause are only visible to users associated with the first entity. This allows all users associated with the first entity to continue to collaborate among themselves on edits to the locked document until it is in a state where they are ready for the rest of the users associated with other entities to view the changes. At the same time, the other users can continue to review, edit, and collaborate on the other clauses in the document. When the permissions are updated, all entities can again view the clauses for negotiation.

Abstract: A centralized auditing system receives an audit block containing one or more audit files generated by an audit agent running in an audited device. The audit block additionally stores a first digital signature corresponding to a previous audit block, and a second digital signature generated based at least on the one or more audit files and the first digital signature. After receiving the audit block, the auditing system verifies the integrity of the received audit block based on the second digital signature stored in the audit block and/or the first digital signature corresponding to the previous audit block. In response to verifying the integrity of the received audit block, the auditing system adds the received audit block to an audit register. Moreover, the auditing system adds the one or more audit files included in the audit block to an audit database.

Abstract: An online document system provides a recommendation for one or more features within the online document system to an entity. The online document system accesses a set of feature training data to train a machine learning model. The set of feature training data may describe characteristics of entities associated with the online document system and historical activity associated with the entities' usage of the online document system's features. The machine learning model may be configured to identify a feature to recommend to an entity based on the entity's characteristics and history of using other features within the online document system. For example, data representing the entity's user accounts and use of an electronic signature feature is used by the machine learning model to identify a document authentication feature to recommend to the entity. The online document system may then provide the identified feature in a recommendation to the entity.

Abstract: A document management system sends a distinct copy of a set of documents to each of a plurality of recipients in a bulk sending process. Each copy is associated with one or more actions to be taken by a corresponding recipient. The document management system generates an interface that displays, for each copy of the set of documents, the recipient of the copy and a status of the copy. The document management system receives an identification of a subset of the copies of the set of documents. The document management system performs a bulk action on each of the subset of the copies without performing the bulk action on any remaining copies of the set of documents.

Abstract: A system receives a request associated with a first account to delegate, to a second account, authority to send documents on behalf of the first account. The request identifies requirements that must be satisfied before the second account can send documents on behalf of the first account. Responsive to receiving a request to send a first document to a first entity from the second account and on behalf of the second account, the system sends the first document to the first entity. Responsive to receiving a request to send a second document to a second entity from the second account and on behalf of the first account, the system determines whether the request to send the second document satisfies the requirements. Responsive to the request satisfying the requirements, the system sends the second document to the second entity on behalf of the first account.

Abstract: A document management system sends a distinct copy of a set of documents to each of a plurality of recipients in a bulk sending process, producing a batch of document sets. The document management system can facilitate the performance of a bulk action on the batch of document sets by a sending entity. Examples include a bulk corrective action, a bulk void action, a bulk re-send action, and a bulk download action. In addition, the document management system can identify document sets sent separately that are likely parts of a batch of document sets using one or more similarity criteria. The document management system can recommend that a sending entity combine the identified document sets into a batch of document sets, enabling the sending entity to perform bulk actions on the document sets.

Abstract: Systems and methods are disclosed herein for generating and modifying a workflow comprising a series of webpages based on an online document. A document management system accesses an online document selected by a user and classifies each field of the online document into one of a set of categories. For each category, the system generates a form webpage comprising questions corresponding to each field classified as the category and combines the generated webpages to create a workflow. The system may modify the workflow by generating and adding one or more additional form webpages based on one or more answers provided by an entity completing the webform page. In response to the entity completing the modified generated workflow, the system generates a completed document based on the online document and the answers provided by the entity.

Abstract: A document management system integrates with a video conference system to ensure that proper electronic witness procedure is performed for document validation. The document management system accesses a video conference between a user and an electronic witness, and then instructs the user to electronically sign the document while the electronic witness observes. The document management system receives confirmation that the electronic witness observed the video of the user electronically signing the document. The document management system combines and stores portions of the video conference that correspond to the electronic witness's validation of the document.

Abstract: A system and method for electronic document management including: creating an executable document object, wherein the executable document object comprises at least one programmable element; constructing an interaction schema object, wherein each interaction schema comprises: executable logic and a trigger as part of an inbound interaction schema or an outbound interaction schema that associates an external resource with the executable document object; and bundling the interaction schema object with the executable document object.

Abstract: Techniques for providing data security services with respect to cloud-based services are described. Examples include a security service provider (“SSP”) configured to perform or provide one or more security-related services or functions with respect to or on behalf of some other system or service. The other system or service may be, for example, a cloud-based system that provides network-accessible services. The SSP allows a user of the cloud-based service to provide and manage one or more security-related services, such as data storage, encryption, decryption, key management, and the like. By using and controlling the SSP, the user can be confident that his or her data is being securely represented and stored, even though it is being operated upon by a cloud-based service that is not under the user's control.