Abstract: A centralized document system generates a document package in response to a request by an originating entity. The document package includes at least one document for execution by a first receiving entity. The first receiving entity can specify a set of permissions for a second receiving entity to perform actions to documents within the package on behalf of the first receiving entity. Accordingly, the system may provide the document package to both the first and second receiving entities for the first receiving entity to execute the at least one document. Before providing the document to the second receiving entity, system may determine whether there is a sensitive document in the package and whether to delegate the document to the second entity. Accordingly, the system may prevent a sensitive document package from being provided to the second receiving entity for execution.

Abstract: A centralized document system generates a document package in response to a request by an originating entity. The document package includes at least one document for execution by a first receiving entity. The first receiving entity can specify a set of permissions for a second receiving entity to perform actions to documents within the package on behalf of the first receiving entity. Accordingly, the system may provide the document package to both the first and second receiving entities for the first receiving entity to execute the at least one document. Before providing the document to the second receiving entity, system may determine whether there is a sensitive document in the package and whether to delegate the document to the second entity. Accordingly, the system may prevent a sensitive document package from being provided to the second receiving entity for execution.

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 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: 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: 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 centralized document system generates a document package in response to a request by an originating entity. The document package includes at least one document for execution by a first receiving entity. The first receiving entity can specify a set of permissions for a second receiving entity to perform actions to documents within the package on behalf of the first receiving entity. Accordingly, the system may provide the document package to both the first and second receiving entities for the first receiving entity to execute the at least one document. Before providing the document to the second receiving entity, system may determine whether there is a sensitive document in the package and whether to delegate the document to the second entity. Accordingly, the system may prevent a sensitive document package from being provided to the second receiving entity for execution.

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.