JP2024065533A - Program, method, information processing device, and method for manufacturing document data management system - Google Patents

Abstract

[Problem] To improve the reliability of a request for concluding a contract. [Solution] A program for providing a document data management service causes a computer processor to execute the steps of: accepting, from a first user, an operation for designating document data to be approved and one or more second users who will approve the document data; sending, to the designated second user, a notification for requesting approval of the document data, the notification including link information for starting use of the document data management service, which is not information on an access destination for the document data to be approved; accepting, from the second user, access to the link information included in the notification; and presenting, to the second user, via the document data management service, the document data for which approval is requested by the first user, based on the accepted access to the link information. [Selected Figure] Figure 1

Description

This disclosure relates to a program, a method, an information processing device, and a method for manufacturing a document data management system.

There is technology that allows contracts to be concluded by exchanging electronic data of contracts over the Internet and applying electronic signatures, and then storing the electronic data on a company's server or in cloud storage.

Patent document 1 describes a method of simultaneously sending emails containing different URLs to the terminal devices of multiple contracting parties, encouraging each party to view the electronic contract that they are to digitally sign by clicking on the link in each URL.

JP 2021-5360 A

However, with the technology of Patent Document 1, a request email is sent from a false sender to encourage the conclusion of a contract, and even if it is a so-called phishing email that poses the appearance of a contract and leads to unauthorized access, the recipient may determine that the email is legitimate. If the recipient mistakenly opens the fake link information or attachment contained in such a phishing email, there is a risk that the user's terminal will be infected with a computer virus, or that the user may mistakenly send personal information on a spoofed website and have it stolen.

Therefore, this disclosure provides technology that further increases the reliability of contract conclusion requests.

According to one embodiment, a program is provided for providing a document data management service that is executed by a computer having a processor and a memory and that manages document data and the approval status of the document data by each user. The program causes the processor to execute the following steps: accepting an operation from a first user to specify document data to be approved and one or more second users who will approve the document data; sending a notification to the specified second user, the notification being a request for approval of the document data, but including link information for starting use of the document data management service, which is not information on the access destination of the document data to be approved; accepting access from the second user to the link information included in the notification; and presenting the document data requested for approval by the first user to the second user via the document data management service based on the accepted access to the link information.

According to the present disclosure, the reliability of a contract conclusion request email can be improved by sending a notification to the second user, who is the recipient, to request approval of document data that does not include a URL for accessing the document data, such as a contract.

1 is a diagram showing the overall configuration of an electronic contract system 1 according to an embodiment. FIG. 2 is a block diagram showing a functional configuration of a recipient terminal device 10. FIG. 2 is a block diagram showing the functional configuration of the server 20. FIG. 1 is a conceptual diagram for explaining an electronic contract. A diagram showing the data structure of the electronic contract management database 2021. 13 is a diagram showing the data structure of sending time approver information 2022. FIG. FIG. 2 is a diagram showing the data structure of an approval history 2023. FIG. 13 is a diagram showing the flow of a process for concluding a contract between the parties via the server 20. FIG. 11 is a diagram showing a flow of user authentication by an application for using a document data management service. 11 is a diagram showing a flow of user authentication on a website on a web browser for using a document data management service. FIG. 13 is a diagram showing an example of a screen of a notification sent to a recipient. 13 is a diagram showing an example of a screen for executing login to the document data management service from an application for using the document data management service. FIG. 13 is a diagram showing an example of a screen that requests input of an authentication code for logging in to the document data management service from an application for using the document data management service. FIG. 13 is a diagram showing an example of a screen requesting input of an authentication code for logging in to a document data management service from a site on a web browser for using the document data management service. FIG. FIG. 13 is a diagram showing an example of a screen for accessing contract data after login is performed.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the following description, the same parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

First Embodiment
In the following embodiment, an example of a document data management service will be described in which the parties entering into a contract allow the users of each party to view the document data that is the subject of the contract and notify them via email, messenger tool, etc. to perform an operation to approve the document data.
In systems where users communicate with each other via email, attackers may attach files to fraudulent emails, causing computer viruses when the files are opened. Here, emails requesting the conclusion of an electronic contract may be sent and received, but if there are users who are concerned that opening an attachment in such an email may result in computer virus infection, the use of electronic contracts will not be promoted.
Therefore, in the following embodiment, a technology is provided that further improves the reliability of notifications of requests to conclude a contract through an electronic contract, thereby further encouraging the use of electronic contracts.
(1) Allowing a user to view the document data to be approved by logging in to a document data management service. Specifically, when a notification is sent to the user of each party via email or other means to request the parties to approve the document data pursuant to a contract or other agreement, information about the storage location of the document data to be approved (information for accessing the storage location of the document data, displayed in the form of a URL or other format) is not included in the notification, but information for logging in to the document data management service is included in the notification.
(2) Multiple means for using the document data management service and simplified login operation Specifically, multiple means for using the document data management service are provided to the user. The multiple means include the following:
First means: An application executable on a user's terminal for utilizing the document data management service. The application is provided to the user by a business operator or the like that operates the document data management service.
Second means: A web browser running on a user's terminal allows the user to access a website that provides a document data management service.
In the document data management service, a notification for requesting a user to perform an operation for approving document data includes a link for using the first means and a link for using the second means.
Furthermore, when a user uses the document data management service through an application (first means), the operations required for user authentication associated with using the service may be reduced compared to when the user uses the service by accessing a website through a web browser (second means).
Here, the document data management service may authenticate a user using two or more elements, and if the authentication is successful, may omit some operations for authenticating the user for a certain period of time based on the authentication history. Here, more operations for authentication may be omitted (reducing the operations for authentication performed by the user) when using an application compared to when browsing a website with a web browser. This encourages each user to use the document data management service through the application.
For example, in a document data management service, while assuming that a user is authenticated using two or more elements, if the user is authenticated using an application installed on the terminal, thereafter, for a certain period of time, authentication input is not required, but when a web browser is used, authentication using at least one element may be required.
Also, for example, when using an application, the user may be authenticated using fewer elements than those initially required, while when accessing a website using a web browser to use a document data management service, the user may be authenticated using more elements than when using an application.
In this embodiment, a user operates a mobile terminal such as a PC (personal computer), a smartphone, or a tablet to use a document data management service. The document data management service manages document data and information on users who have approved the contents of the document data, and accepts an operation of approving the contents of the document data from each user while allowing each user to view the contents of the document data. For example, between parties to enter into a contract, the users of each party use the document data management service to perform an operation of approving the document data by electronic contract, and enter into the contract. In an electronic contract, the contract is advanced by performing an operation of approving the contract data, which is the content agreed upon between the contracting parties and is the subject of the electronic contract, between the two parties. In addition, although a pledge or other document indicates a contract between the two parties, a user of one of the parties may perform an operation of approving the document data.

The contract data is based on the contract conditions agreed upon by both parties and includes, for example, at least the data created in the following manner:
- Contract data created using software for creating documents - Data that matches each item of the contract conditions with the contents agreed upon by both parties for each item

In an electronic contract, there is one or more approvers who approve the contract data. Based on the contract data, the approver decides whether or not to conclude the contract under the conditions specified in the content of the contract data.

In the electronic contract system 1 described below, the server 20 is for concluding electronic contracts between a plurality of users who are corporations or individuals. Note that individuals include sole proprietors.
- Conclusion of an electronic contract between corporations For example, a first user, such as a corporation, and a second user, such as a corporation, agree to conclude a contract with the first user and the second user as the contracting parties.
- Conclusion of electronic contracts between corporations and individuals For example, in the case of a real estate lease contract, an employment contract, or an insurance contract, an agreement is reached to conclude a contract between a first user which is a corporation such as a real estate management company and a second user which is an individual, with the first user and the second user as the contracting parties.
- Conclusion of electronic contracts between individuals. There may also be more than two parties to a contract (for example, a tripartite contract).

<1.1 Overall system configuration>
Fig. 1 is a block diagram showing an example of the overall configuration of an embodiment of an electronic contract system 1. As shown in Fig. 1, the electronic contract system 1 includes a receiver terminal device 10, a sender terminal device 30, and a server 20, which are connected to each other via a network 80 so as to be able to communicate with each other.

The example in FIG. 1 shows a recipient terminal device 10 used by a user. The recipient terminal device 10 is, for example, a mobile terminal such as a smartphone or tablet.

The recipient's terminal device 10 executes a program to provide the user with an environment for operating a system according to the program. The recipient's terminal device 10 reads and executes the program to communicatively connect the recipient's terminal device 10, the sender's terminal device 30, and the server 20. The recipient's terminal device 10 then transmits and receives data related to the electronic contract (e.g., contract data, information indicating that each user has approved the contract data, information that allows the user to view the concluded contract data, etc.) between the recipient's terminal device 10, the sender's terminal device 30, and the server 20.

The server 20 transmits data necessary for the electronic contract to the recipient's terminal device 10 as appropriate, thereby visualizing the status of the electronic contract on the recipient's terminal device 10. The server 20 manages various data related to the electronic contract of the user who operates the electronic contract. The server 20 communicates with the recipient's terminal device 10, and transmits images, files, text data, and the like to the recipient's terminal device 10 according to the progress of each user's electronic contract.

For example, the server 20 manages various other data, such as user information related to electronic contracts, information on contract data used in electronic contracts, and information on the approval date and time when a user approved an electronic contract.

The recipient terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage unit 16, and a processor 19.

The communication IF 12 is an interface for inputting and outputting signals so that the recipient terminal device 10 can communicate with external devices.

The input device 13 is a device for accepting input operations from a user (e.g., a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

The output device 14 is a device (display, speaker, etc.) for presenting information to the user.

Memory 15 is used to temporarily store programs and data processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

The memory unit 16 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

The processor 19 is hardware for executing the instruction set described in the program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

The server 20 is a device that manages information about users who enter into contracts through electronic contracts, contract data used when making electronic contracts, and other information.

The server 20 includes a communication IF 22, an input/output IF 23, a memory 25, a storage 26, and a processor 29.

The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

The input/output IF 23 functions as an input device for accepting input operations from the user, and as an interface with an output device for presenting information to the user.

Memory 25 is used to temporarily store programs and data processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

Storage 26 is for storing data, and is, for example, a flash memory or a hard disc drive (HDD).

The processor 29 is hardware for executing the instruction set described in the program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

The sender side terminal device 30 includes a communication IF (Interface) 32, an input device 33, an output device 34, a memory 35, a storage unit 36, and a processor 39.

The communication IF 32 is an interface for inputting and outputting signals so that the sender terminal device 30 can communicate with external devices.

The input device 33 is a device for accepting input operations from a user (e.g., a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

The output device 34 is a device (display, speaker, etc.) for presenting information to the user.

Memory 35 is used to temporarily store programs and data processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

The memory unit 36 is for storing data, and is, for example, a flash memory or a hard disc drive (HDD).

The processor 39 is hardware for executing the instruction set described in the program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

<1.2 Functional configuration of the recipient terminal device 10>
2 is a diagram showing the functional configuration of the recipient's terminal device 10. The recipient's terminal device 10 includes an antenna 111, a wireless communication unit 121, a processor 19, an operation reception unit 130, a storage unit 16, a memory 15, a display 132, a voice processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, and a camera 160.

The antenna 111 radiates the signal emitted by the receiver terminal device 10 into space as radio waves. The antenna 111 also receives radio waves from space and provides the received signal to the wireless communication unit 121.

The wireless communication unit 121 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 111, etc., so that the recipient's terminal device 10 can communicate with other communication devices. The wireless communication unit 121 is a communication module for wireless communication that includes a tuner, high-frequency circuit, etc., and performs modulation and demodulation or frequency conversion of the wireless signals transmitted and received by the recipient's terminal device 10, and provides the received signals to the processor 19.

The processor 19 controls the operation of the receiver terminal device 10 by reading and executing the programs stored in the storage unit 16. The processor 19 is realized, for example, by an application processor.

The operation reception unit 130 has a mechanism for receiving input operations from the user. For example, the operation reception unit 130 is realized as a pointing device such as a mouse, touchpad, or touch panel, a keyboard, a controller, or an imaging means for sensing the user's body movements as input operations. For example, the operation reception unit 130 senses the movements of body parts such as hands and the user's facial expressions as the user's body movements, and receives the movements of these body parts as input operations. The operation reception unit 130 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation, based on the coordinates at which the input operation is received by the user touching a finger to a touchpad or touch panel, etc.

The storage unit 16 is composed of a flash memory, a RAM (Random Access Memory), etc., and stores programs used by the recipient's terminal device 10 and various data that the recipient's terminal device 10 receives from the server 20.

The display 132 displays data such as images, videos, and text under the control of the processor 19. The display 132 is realized by, for example, an LCD (Liquid Crystal Display), an organic EL (Electroluminescence), or other display device.

The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates the signal provided from the microphone 141 and provides the modulated signal to the processor 19. The audio processing unit 140 also provides the audio signal to the speaker 142.

The microphone 141 receives audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140.

The speaker 142 converts the audio signal provided by the audio processing unit 140 into audio and outputs the audio to the outside of the recipient's terminal device 10.

The position information sensor 150 is a sensor that detects the position of the terminal device 10, and is, for example, a GPS (Global Positioning System) module. The GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current position of the terminal device 10 in which the GPS module is installed is detected based on the received signals.

Camera 160 is a device that receives light using a light receiving element and outputs the light as a captured image. Camera 160 is, for example, a depth camera that can detect the distance from camera 160 to the subject being photographed.

The storage unit 16 stores electronic contract management information 161, transmission time approver information 162, and approval history 163.
The electronic contract management information 161 is information for managing each electronic contract.
The sender's approver information 162 indicates information on the recipient's approver designated by the sender's terminal device 30 in the electronic contract being concluded by the recipient's terminal device 10 .
The approval history 163 indicates information on the approval history including information on the timing of approval by the user who is the approver for each electronic contract.

The processor 19 operates according to a program to perform the functions of an input operation reception unit 191, a transmission/reception unit 192, a data processing unit 193, and a notification control unit 194.

The input operation reception unit 191 performs processing to receive a user's input operation on an input device such as the operation reception unit 130. When the operation reception unit 130 is, for example, a touch-sensitive device, the input operation reception unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation, based on information on the coordinates where the user touches the touch-sensitive device with a finger or the like.

The transmission/reception unit 192 performs processing to enable the receiver terminal device 10 to transmit and receive data to and from external devices such as the server 20 in accordance with a communication protocol.

The data processing unit 193 performs calculations according to a program on the data received by the recipient terminal device 10, and outputs the results of the calculations to a memory or the like.

The notification control unit 194 performs processes to present information to the user, such as displaying a display image on the display 132, outputting sound to the speaker 142, and generating vibrations from a vibrator or the like.

<1.3 Functional configuration of server 20>
Fig. 3 is a diagram showing the functional configuration of the server 20. As shown in Fig. 3, the server 20 fulfills the functions of a communication unit 201, a storage unit 202, and a control unit 203.

The communication unit 201 performs processing for the server 20 to communicate with external devices.

The memory unit 202 stores various databases such as an electronic contract management database 2021, approval information at the time of transmission 2022, and approval history 2023.

The electronic contract management database 2021 is a database for managing information on each contract concluded in the electronic contract system 1. Details will be described later.

The sender information 2022 is a database for managing information on users who are set as approvers for each contract concluded in the electronic contract system 1. Details will be described later.

The approval history 2023 is a database of approval history that includes information on the timing of approval by the user who will be the approver for each electronic contract. Details will be described later.

The control unit 203 is realized by the processor 29 reading a program stored in the memory unit 202 and executing instructions contained in the program. By operating in accordance with the program, the control unit 203 performs the functions shown as a reception control module 2031, a transmission control module 2032, an electronic contract information acquisition module 2033, an approver user information acquisition module 2034, and an approval date and time information acquisition module 2035.

The reception control module 2031 controls the process in which the server 20 receives signals from external devices according to a communication protocol.

The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices according to a communication protocol.

The electronic contract information acquisition module 2033 performs a series of processes to manage electronic contract information.

The approval date and time information acquisition module 2035 performs a series of processes to manage information on the date and time when the approver approved the document.

<1.4 Conceptual diagram to explain electronic contracts>
FIG. 4 is a conceptual diagram for explaining an electronic contract.

In this embodiment, an "electronic contract" includes using a document data management service provided by a business operator or the like that operates server 20 to electronically sign and timestamp the contract data agreed upon by the contracting parties using a signature key as follows:
- The contracting parties use a signing key prepared by the contracting parties themselves to electronically sign and time stamp the contract data. - The contracting parties use a signing key prepared by the document data management service provider to electronically sign and time stamp the contract data based on their intentions (for example, in response to the contracting parties' operation to approve the contract data).

For example, the contracting parties operate their respective terminal devices to exchange contract document data over the Internet via server 20, and when the contracting parties perform an input operation to indicate their intention to agree, the contracting parties affix an electronic signature and a timestamp to the electronic data of the contract document.

First, the contract sender operates the sender's terminal device 30 to upload the contract data to, for example, the server 20 on the cloud. The server 20 assigns the contract sender's digital signature and timestamp to the contract data agreed to by the contract sender.

The contract sender (first user) performs an operation to request the contract recipient (second user) to enter into an agreement. Specifically, the sender terminal device 30 accepts an operation to designate a contract recipient from the user and transmits it to the server 20. In this embodiment, the sender terminal device 30 accepts information identifying one or more contract recipients (second users) from the contract sender (first user) and requests the users of the contract recipient to enter into an agreement via the server 20. The information identifying the user received from the contract sender may be as follows:
- Email address of each contract recipient - Account of the service used by the contract recipient (for example, if a user account has been issued in the document data management service provided by the server 20, information identifying the user account, such as a user ID. Also, information identifying a user account in a service other than the document data management service provided by the server 20, etc.)

The server 20 of the electronic contract system 1 sends an email to the contract recipient (second user) to the email address of the contract recipient specified by the first user of the contract sender, requesting an agreement (approval) to be reached on the contract data, which is document data.
The notice shall include:
- An application installed on the contract recipient's terminal, which is a link for launching the application for using the document data management service - A link for accessing the document data management service's website using a web browser - A link for downloading the application for using the document data management service Here, methods by which the server 20 sends a notification to the contract recipient requesting agreement (approval) on the contract data are included as follows.
- Sending a notification by email to the email address of the contract recipient - Sending a notification to the user account of a service other than the document data management service used by the contract recipient (SNS (Social Network Service) account, messenger tool account, etc.) using the functions of that service - Sending a notification regarding applications installed on the terminal as a function of the OS (Operating System) of the terminal used by the contract recipient - Sending a notification by SMS (Short Message Service) or MMS (Multimedia Messaging Service) to the telephone number assigned to the terminal used by the contract recipient

Here, the server 20 may receive from the contract sender (first user) a specification of the viewing order of multiple contract recipients (second users). For example, when the server 20 receives from the contract sender a specification of multiple email addresses of contract recipients, the server 20 may send a notification to each contract recipient requesting them to conclude an agreement on the contract data in the order of the specified email addresses.

For example, suppose that a first email address, a second email address, and a third email address are specified as contract recipients (second users) by the contract sender (first user). The server 20 first sends a notification to the first contract recipient at the first email address to request an agreement on the contract data, and accepts an approval operation from the first contract recipient. In response to accepting an approval operation for the contract data from the first contract recipient, the server 20 records the fact that the first contract recipient has approved and the timing of the approval (for example, in response to the approval operation, the server 20 attaches the electronic signature of the first contract recipient), and sends a notification to the second contract recipient at the second email address to request an agreement on the contract data. Thereafter, the server 20 similarly records the second contract recipient's approval and the timing of the approval (for example, attaches the second contract recipient's electronic signature in response to the approval operation), sends a notification to the third contract recipient in response to the second contract recipient's approval to request the conclusion of an agreement on the contract data, and accepts an approval operation from the third contract recipient.

The contract recipient (second user) can click on a link contained in the email received on the recipient's terminal device 10, launch an application or web browser linked to the document data management service, and after the subsequent authentication process, confirm the contents of the contract data on the server 20 online to enter into (approve) the contract. The recipient's terminal device 10 presents a screen for accepting an operation indicating agreement to the contract to the user of the recipient's terminal device 10, and accepts an operation for agreement from the user.
If there is a defect in the contract contents at this point, the server 20 may accept an operation from the contract recipient indicating that the contract is not agreed to.

When the server 20 receives an operation from the contract recipient agreeing to the contract data, it assigns the contract recipient's electronic signature and timestamp to the contract data. The contract data is stored on the server 20. By assigning electronic signatures and timestamps from both contracting parties, the contract is prevented from being tampered with.

This embodiment realizes such a cloud-based document data management service. In the following embodiment, a technique for improving the reliability of a contract conclusion request email with regard to approval of contract data managed in a document data management service, which is a document data management service, is described.

<2 Data Structure>
5 to 7 are diagrams showing the data structure of the database stored in the server 20. Note that Fig. 5 to Fig. 7 are merely examples, and do not exclude data not shown.

Figure 5 is a diagram showing the data structure of the electronic contract management database 2021. Each record in the electronic contract management database 2021 includes the items "contract ID", "sender's document transmission date and time", "contract status", "contract completion date and time", "sender's email address", "recipient's email address 1", "recipient's email address 2", "recipient's email address 3", and "document ID used in electronic contract". In the example shown, an example is shown in which a sender's user (first user) in an electronic contract can specify three users as multiple recipient's users (second users), but this is not limited to three users.

The "Contract ID" item indicates identification information issued, for example, by server 20, for each contract concluded by electronic contract.

Specifically, the item "Contract ID" is a unique ID for an electronic contract that is required when managing each contract concluded between users by electronic contract.

The item "Sender's document transmission date and time" indicates the timing at which the sender's user transmitted contract data to the server 20 in order to conclude a contract by electronic contract. For example, the server 20 performs a process to accept an upload of contract data from the sender's user, and stores the timing at which the process was performed in the item "Sender's document transmission date and time".

The item "agreement status" indicates the status of the electronic contract being concluded between the sender and the recipient. Specifically, the status of the electronic contract between the parties may include the following:
"Not yet contracted": A state in which the work of concluding an electronic contract between users has not yet begun. For example, a state in which the designation of users involved in the work of concluding an electronic contract is being accepted. "Contract being concluded": A state in which each user has been designated in concluding an electronic contract, but an operation to approve the contents of the contract has not been accepted from at least one of the designated users. "Contract completed": A state in which the server 20 has accepted an operation to approve each user designated in concluding an electronic contract, and the conclusion of the contract by electronic contract has been completed.

The "sender's email address" item indicates information that identifies the sender's user, specifically the sender's email address.

The item "Recipient's email address 1" indicates information that identifies the recipient's user, specifically the recipient's user's email address (first one).

The item "Recipient's email address 2" indicates information that identifies the recipient's user, as above, and specifically indicates the recipient's email address (second).

The item "Recipient's email address 3" indicates information that identifies the recipient's user, as above, and specifically indicates the recipient's email address (the third one).

The item "Document ID used in electronic contract" indicates the identification information (ID) of the data of the document that is the subject of the electronic contract. For example, the document identification information includes unique information that is issued by the server 20 in association with the document data when the server 20 accepts an upload of the document data as the subject of the electronic contract (such as identification information issued to the document, link information for each terminal device to access the document, etc.).

Figure 6 is a diagram showing the data structure of the send time approver information 2022. Each record of the send time approver information 2022 includes the items "contract ID", "approver 1 user ID", "approver 2 user ID", and "approver 3 user ID". In the example shown, a sender user (first user) in an electronic contract can specify three users as multiple recipient users (second users), but the number is not limited to three.

The "Contract ID" item indicates identification information issued, for example, by server 20, for each contract concluded by electronic contract.

Specifically, the item "Contract ID" is a unique ID for an electronic contract that is required when managing each contract concluded between users by electronic contract.

The item "Approver 1 User ID" indicates the ID of the user who is the first approver on the recipient side, specified by the user on the sender side of the electronic contract.

The item "Approver 2 User ID" similarly indicates the ID of the user who is the approver (second person) on the recipient's side.

The item "Approver 3 User ID" similarly indicates the ID of the approver (third person) user on the recipient side.

Figure 7 is a diagram showing the data structure of the approval history 2023. The approval history 2023 includes the items "contract ID", "approver 1 user ID", "approval date and time of approver 1", "approver 2 user ID", "approval date and time of approver 2", "approver 3 user ID", and "approval date and time of approver 3". In the example shown, a sender user (first user) in an electronic contract can specify three users as multiple recipient users (second users), but the number is not limited to three.

The "Contract ID" item indicates identification information issued, for example, by server 20, for each contract concluded by electronic contract.

Specifically, the item "Contract ID" is a unique ID for an electronic contract that is required when managing each contract concluded between users by electronic contract.

The item "Approver 1 User ID" indicates the ID of the approver (first user).

The item "Approver 1's Approval Date and Time" indicates the date and time when the first approver approved.

The item "Approver 2 User ID" indicates the ID of the approver (second user).

The item "Approver 2's Approval Date and Time" indicates the date and time when the approver (second person) approved.

The item "Approver 3 User ID" indicates the ID of the approver (third user).

The item "Approver 3's Approval Date and Time" indicates the date and time when the approver (third person) approved.

<Operation of the First Embodiment>
Next, the operation of each device constituting the electronic contract system 1 will be described.

Figure 8 is a diagram showing the flow of the process of concluding a contract between the parties via the server 20. In the following example, a case is described in which, when concluding a contract by electronic contract, a first user who is the sender identifies a second user who is the recipient, and then proceeds with concluding the contract via the server 20.

In step S601, the sender terminal device 30 accepts an operation from the sender (first user) to specify the data of a document to be used in an electronic contract between the first user and the second user. The sender terminal device 30 transmits the accepted document data to the server 20 as contract data.

When sending the contract data to the server, the sender's terminal device 30 accepts input of the email address of the recipient (second user) from the sender (first user) as the destination of the document. The sender's terminal device 30 transmits the accepted email address information to the server 20.

In step S631, the server 20 receives contract data used in the electronic contract from the sender terminal device 30. The server 20 updates the electronic contract management database 2021 based on the information received from the sender terminal device 30 (contract data, information specifying the user of the first business operator, etc.).

In step S632, the server 20 sends an email to the specified recipient containing a notification requesting approval of the contract.

The notification does not include information on the access destination of the document data to be approved by each user, but includes link information for starting use of the document data management service. Specifically, the link information includes a link described as a URL for starting an application (an application installed in the recipient's terminal device 10) for using the document data management service, and a link described as a URL for displaying a website for using the document data management service on a web browser. For example, when the recipient's terminal device 10 receives an operation from the user on the web browser to specify a URL for starting an application for using the document data management service, the recipient's terminal device 10 displays a web browser dialog and receives an operation from the user as to whether or not to start the installed application.

In step S651, the recipient's (second user's) terminal device 10 receives a notification from the server 20 via e-mail or the like.

In step S652, the recipient's terminal device 10 accepts access from the recipient (second user) to link information for starting use of the document data management service, which is included in a notification such as an e-mail, and transmits it to the server 20. For example, the recipient's terminal device 10 provides the recipient with a screen displaying a link for starting the above-mentioned application and a link for displaying the website in a web browser, and accepts an input operation from the recipient to specify one of the links.

In step S633, when the server 20 receives access from the recipient (second user), the server 20 presents the recipient with information for displaying contract data indicating the contract contents. Specifically, the server 20 presents the recipient with information for displaying the contract data in accordance with the link information specified by the recipient, such as information for prompting the recipient to log in to an application, or information for prompting the recipient to log in to a document data management service from a website displayed in a web browser.

In step S653, the recipient's terminal device 10 accepts a login request from the recipient (second user) based on information presented by the server, and transmits the request to the server. The login request is accepted based on user authentication that combines two or more different authentication elements (multi-factor authentication), which will be described later.

In step S634, if user authentication is properly performed, the server 20 presents the contract data to the recipient (second user). Specifically, the server 20 refers to the information managed in the electronic contract management database 2021 based on the account information of the logged-in user, identifies the contract for which the user should perform the contract conclusion operation, and presents the contract data to the user. The information is presented to the user by displaying the information on the display 132, notifying the user by voice, etc.

In step S654, the recipient's terminal device 10 confirms the contents of the contract data from the approver (second user) and accepts an input operation for concluding the contract (an input operation for approving). In response to the input operation for concluding the contract, the recipient's terminal device 10 transmits information indicating that the contract will be concluded to the server 20.

In step S635, the server 20 receives information from the second user indicating that a contract will be concluded regarding the contract data, and updates various information such as the approval history 2023 and the electronic contract management database 2021.

When the server 20 receives information indicating that a contract will be concluded from the second user who is the approver, the server 20 transmits information indicating that the contract has been concluded to the first user and the second user (e.g., the email addresses of the users involved as the sender or receiver in concluding the electronic contract). For example, the server 20 transmits a message to the email address of the second user, notifying the first user that the work of concluding the contract has been completed, including link information for viewing the documents that are the subject of the contract.

In step S602, the sender terminal device 30 presents the result of the completion of the electronic contract conclusion to the sender (first user) by, for example, displaying information on the display 132.
As a result of the above, the server 20 assumes that an agreement has been reached between the first user and the second user regarding the contract data, and manages the contract data based on various databases.

(Authentication process)
9 is a diagram showing the flow of user authentication by an application that cooperates with the document data management service. The authentication process in Fig. 9 starts from the process of step S651 in Fig. 8 and ends with the process of step S634.

In step S651, the recipient terminal device 10 receives an email from the server 20 containing a notification requesting approval of the contract.

In step S6521a, the recipient terminal device 10 accepts access from the recipient (second user) to the first link information (a link written as a URL for accessing an application that cooperates with the document data management service) included in the notification for starting use of the document data management service, and transmits it to the server 20.

In step S633, when the server 20 receives access from the recipient (second user), it presents the recipient with a login screen for the document data management service on the application as information for displaying the contract data, and accepts the login. The information entered in this login process is the first authentication information, for example, the user's account information and password. Examples of account information include an email address specified by the user, and information consisting of an arbitrary character string.

In step S6531a, the recipient's terminal device 10 accepts input of first authentication information on the login screen from the recipient, and transmits it to the server 20. Upon properly accepting the first authentication information, the server 20 subsequently requests input of second authentication information.
Here, when the server 20 accepts the first authentication information from the user as a login process to the document data management service from an application for using the document data management service, and further accepts the input of the second authentication information (when authentication is performed using two or more factors), the operation required for authentication may be reduced for subsequent logins of the user within a certain period of time. For example, when a certain period of time has passed since the server 20 accepted authentication using two or more factors from the user via an application installed on a terminal, when the user uses the document data management service via an application installed on the terminal used for the authentication, the server 20 may omit the input of the first authentication information and the second authentication information, or may accept the input of the first authentication information but omit the input of the second authentication information. For example, the server 20 may automatically accept the second authentication information accepted in the past as the second authentication information without the recipient (second user) inputting the second authentication information. The omission of such second authentication information is an advantage for the user when performing the login process via an application, and when performing the login process from a website using a web browser, two or more factor authentication (i.e., input of second authentication information, etc.) may be required each time.

The second authentication information that is omitted in the login process via the application is:
Examples of the second authentication information include a password and an authentication code. The authentication code may be information consisting of an arbitrary character string sent via SMS (Short Message Service) or to a pre-specified email address. That is, the server 20 accepts input of the second authentication information from the user through a user interface (such as the above-mentioned SMS) separate from the application or website for using the document data management service.

In step S6331a, when the user launches an application and uses the document data management service, it is determined whether it has been within a certain period of time since the second authentication information was previously properly accepted, and if it has been within the certain period of time, the input of the second authentication information is omitted and the process proceeds to step S634. On the other hand, even if the user launches an application and uses the document data management service, if it has been more than a certain period of time since the second authentication information was accepted, the server 20 requests the recipient (second user) to input the second authentication information (step S6332a).

In step S6532a, the recipient's terminal device 10 accepts input of second authentication information from the recipient (second user) and transmits it to the server 20.

In step S634, if user authentication is successful, the server 20 presents the contract data to the recipient.

Figure 10 shows the flow of user authentication performed by operations on a web browser on a website for using a document data management service. The authentication process in Figure 10 starts with the process of step S651 in Figure 8 and ends with the process of step S634.

In step S651, the recipient terminal device 10 receives an email from the server 20 containing a notification requesting approval of the contract.

In step S6521b, the recipient's terminal device 10 accepts access from the recipient (second user) to second link information (a link written as a URL for displaying a website for using the document data management service by a web browser) included in the notification to start using the document data management service, and transmits it to the server.

In step S633, when the server 20 receives access from the recipient (second user), it presents the document data management service website (a page displaying a login screen) on the web browser screen as information for displaying the contract data to the recipient, and accepts login to the service. The information entered in this login process is the first authentication information, for example, the user's account information and password. Examples of account information include an email address specified by the user, and information consisting of an arbitrary character string.

In step S6531b, the recipient's terminal device 10 accepts input of first authentication information on the login screen from the recipient and transmits it to the server 20. If the first authentication information is properly accepted, the recipient is then requested to input second authentication information.

In step S6532b, the recipient's terminal device 10 accepts input of second authentication information from the recipient (second user) and transmits it to the server 20. The second authentication information is
Examples of the authentication code include a password and an authentication code. An example of the authentication code is information consisting of an arbitrary character string sent via SMS (Short Message Service) or to a pre-specified email address.

In step 634, if user authentication is successful, the contract data is presented to the recipient.

As described above, the server 20 allows each approver to view the contract data and requests them to approve it based on the approver information at the time of sending 2022 and the approval history 2023.

As described above, when the server 20 presents the contract data to the recipient (second user), when logging in to the document data management service from the application, if the input of the second authentication information was previously accepted within a certain period of time, the input of the second authentication information is omitted, simplifying user authentication.

<Screen example>
FIG. 11 is a diagram showing an example of a notification screen sent to a recipient.

The example screen in FIG. 11 is a screen that displays a notification requesting approval of a contract, which is included in an e-mail sent from the server 20 to the recipient (second user). This corresponds to the processing of step S651 in FIG. 8, etc.

Screen 1100 for displaying the notification displays the following information: The notification displayed on screen 1100 does not include information indicating the storage location (URL for direct access to the contract data) of the contract data to be confirmed as the subject of approval in the document data management service, but includes link information to a login screen for the document data management service to be accessed from an application or a website used in a web browser.
Area 1100A: Information regarding a message related to a contract approval request Area 1100B: First link information to an application for using the document data management service (a link written as a URL for accessing a login screen of the document data management service from the application)
Area 1100C: second link information to a website for using the document data management service (a link written as a URL for accessing a login screen of the document data management service)
Area 1100D: Information about a message that prompts the user to download the application Area 1100E: Link information for accessing a service for downloading the application

The recipient (second user) who is the contract approver launches an application or a web browser by specifying the first link information 1100B labeled "Open app" or the second link information 1100C labeled "Open web browser" contained in the email received on the recipient's terminal device 10.

The notification does not include link information for direct access to the contract data, preventing access to fake contract data information, as in phishing contract request emails.

If the recipient (second user) has not downloaded the application, the recipient can use the service to download the application by accessing link information 1100E, which is displayed on screen 1100 and is labeled "Download App."

Figure 12 shows an example screen for logging in to the document data management service from an application for using the document data management service.

The example screen in FIG. 12 is a screen on which the server 20 displays information for displaying contract data to the recipient when the recipient (second user) receives access to the first link information for launching an application or the second link information for launching a web browser. This corresponds to the processing of step S633 in FIG. 8, etc.

Screen 1200 displays the following information. Here, the screen 1200 will be described as being common to both the screen for executing login via an application and the screen for executing login via a web browser.
Area 1200A: Information regarding an input box for the user's account name Area 1200B: Information regarding an input box for the user's password Area 1200C: Link information for accessing a service for resetting a password in the event that the user has forgotten the password Area 1200D: Information regarding a button for executing login

The recipient (second user) inputs the user's account information into input box 1200A and the preset password information into input box 1200B from the display 132 of the recipient's terminal device 10 as information for identifying the user in the electronic contract system 1. The recipient's terminal device 10 accepts the input from the recipient (second user) and transmits it to the server 20. The account information and password information input by the recipient (second user) on this screen 1200 is the first authentication information in the multi-factor authentication.

When the server 20 properly accepts the first authentication information from the recipient's terminal device 10, it subsequently requests the recipient (second user) to input the second authentication information. However, when the server 20 accepts the first authentication information as a login to the document data management service via an application, the server 20 omits the input of the second authentication information, provided that it is within a certain period of time since the previous acceptance of the input of the second authentication information, and automatically accepts the second authentication information previously accepted as the second authentication information, without the recipient (second user) having to enter the second authentication information.

Figure 13 shows an example of a screen that requests input of an authentication code to log in to the document data management service via an application for using the document data management service.

The example screen in FIG. 13 is a screen that requests the input of second authentication information as a login process via an application. This screen 1300 is displayed when the server 20 has previously executed a login process via an application and a certain period of time has passed since it accepted the input of second authentication information, or when executing a login for the first time. This corresponds to the processing of step S6332a in FIG. 9.

The screen 1300 displays the following information:
Area 1300A: Information about a message prompting the user to input second authentication information Area 1300B: Information about an input frame for second authentication information Area 1300C: Information about a message explaining that the user can omit inputting second authentication information from the next time onward Area 1300D: Information about a button for executing authentication processing

The recipient (second user) inputs second authentication information into input box 1300B on display 132 of recipient terminal device 10, and selects button 1300D labeled "authentication" for executing authentication processing. The recipient terminal device 10 accepts the input of second authentication information from the recipient (second user) and transmits it to the server 20.

The second authentication information entered by the recipient is an authentication code sent to the telephone number of the recipient's terminal device, which is registered with the document data management service. The authentication code is automatically sent to the recipient's terminal device when the first authentication information is properly accepted. In area 1300C of screen 1300, the advantage is displayed that when the document data management service is used via an application, the next time and thereafter, the input of second authentication information will be omitted for a certain period of time.

If the server 20 properly receives the second authentication information from the recipient terminal device 10, it presents the contract data to the recipient (second user).

Figure 14 shows an example of a screen requesting input of an authentication code to execute a login process to a document data management service by operating a web browser on a website for using the document data management service.

The example screen in FIG. 14 is a screen that requests the input of second authentication information as part of the login process for the website. This corresponds to the process in step S6332b in FIG. 10.

Screen 1400 displays the following information:
Area 1400A: Information related to a message prompting the user to input second authentication information Area 1400B: Information related to an input frame for second authentication information Area 1400C: Information related to a button for executing authentication processing

The recipient (second user) inputs second authentication information into input box 1400B on display 132 of recipient terminal device 10, and selects button 1400C labeled "authentication" for executing the designated process. The recipient terminal device 10 accepts the input of the second authentication information from the recipient (second user) and transmits it to the server 20.

The second authentication information entered by the recipient is an authentication code sent to the telephone number of the recipient's terminal device, which is registered in the document data management service. The authentication code is automatically sent to the recipient's terminal device when the first authentication information is properly accepted.

If the server 20 properly receives the second authentication information from the recipient terminal device 10, it presents the contract data to the recipient (second user).

Figure 15 shows an example of a screen for accessing contract data after logging in.

The screen example in FIG. 15 shows an example of a screen for accessing contract data managed by a document data management service in order to present the contract data to a recipient (second user). This corresponds to the processing of step S634 in FIG. 8, etc.

Screen 1500 displays the following information:
Area 1500A: Information indicating that the contract list is related to the user Area 1500B: Information relating to a button for accessing the first contract data Area 1500C: Information relating to a button for accessing the second contract data Area 1500D: Information relating to a button for accessing the third contract data Area 1500E: Information relating to a message explaining what to do when the access deadline is exceeded

The recipient (second user) can check the contract list related to him/herself from screen 1500 displayed on display 132 of the recipient's terminal device 10. The contract list on screen 1500 is displayed as rectangular buttons, and the recipient can check the contract data by clicking each of buttons 1500B, 1500C, 1500D. "Contract not concluded" or "Contract concluded" is displayed in the upper left of each button, allowing the recipient to easily check which contract data has not been concluded. In addition, if the contract data is the latest, "New" is displayed, allowing the recipient to easily check whether there are any new cases.

For example, the recipient can click or otherwise specify button 1500B for accessing the contract data, and can confirm the contents of the contract data on server 20 online via an application or web browser to conclude an agreement. The recipient's terminal device 10 presents a screen for accepting an operation indicating agreement to the contract to the user of the recipient's terminal device 10, and accepts an operation for agreement from the user.

Buttons 1500B and 1500C for accessing unsigned contract data display the expiration date of the URL link information. If this expiration date is exceeded, the process of presenting the contract data will not be executed even if the button is clicked. Area 1500E of screen 1500 displays that if the access expiration date is exceeded, it is necessary to request re-delivery from the sender.

When the server 20 receives an operation from the recipient (second user) agreeing to the contract data, it assigns the contract recipient's electronic signature and timestamp to the contract data. The contract data is stored in the server 20. The addition of electronic signatures from both contracting parties prevents the contract from being tampered with.

<Modification>
(1) Sending a notification to request approval of document data (contract data) via an application The server 20 may send a notification to the recipient (second user) requesting approval of contract data, including a contract, via a notification means built into an application that works in conjunction with the electronic contract management service, instead of by e-mail.

For example, a recipient (second user) who is a user of the application is logged in to the application service and can receive any notifications related to the document data management service. In the logged-in state, the server 20 may send a notification of a request for approval of contract data, including a contract, to the recipient (second user) by a notification means included in the application. This notification may be automatically displayed on the display of the user's terminal device when it is received by a notification function of the OS of the terminal device.

By adopting the above configuration, by using an application linked to the document data management service, the user can check for notifications on the application without checking email, improving user convenience. By notifying via the application, the opportunities to receive contract request notifications via email can be reduced, making it possible to avoid damage caused by phishing contract request emails.

<Modification>
(2) Modification of Login Execution In the above embodiment, the configuration has been described in which the recipient-side terminal device 10 accepts input of user account information and password information from the recipient (second user) on the login execution screen 1200, and transmits first authentication information to the server 20. In a modification, instead of this, a face image of the user captured by the camera 160 mounted on the terminal device 10 may be used as the authentication information of the user.

For example, the recipient's terminal device 10 may be configured to accept a facial image of the user captured by the camera 160 of the terminal device 10 from the recipient (second user) as first authentication information and transmit it to the server 20.

By adopting the above configuration, the user does not need to enter account information and a password when logging in, which increases convenience for users who use applications in particular.

As described above, by sending a notification to the second user, who is the recipient, to request approval of document data that does not include a URL for accessing document data such as contract data, the reliability of the contract conclusion request email can be improved.

Although several embodiments of the present disclosure have been described above, these embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and variations thereof are considered to be within the scope of the invention and its equivalents as set forth in the claims, as well as within the scope and spirit of the invention.

<Additional Notes>
The matters described in the above embodiments will be supplemented below.
(Appendix 1)
A program for providing a document data management service that manages document data and the approval status of the document data by each user when executed by a computer having a processor (29) and a memory (15), the program executing the following steps: receiving, from a first user, an operation for designating document data to be approved and designating one or more second users who will approve the document data (S601); sending, to the designated second user, a notification for requesting approval of the document data, the notification including link information for starting to use the document data management service, which is not information on an access destination of the document data to be approved (S632); receiving, from the second user, access to the link information included in the notification (S652); and presenting, to the second user, the document data for which approval is requested by the first user, via the document data management service based on the access to the accepted link information (S634).

(Appendix 2)
A program as described in Appendix 1, in which, in a sending step (S632), the link information included in the notification includes first link information (1100B) for using the document data management service by a first means and second link information (1100C) for using the document data management service by a second means different from the first means, and in a presenting step, the document data is presented to a second user by the first means or the second means.

(Appendix 3)
The program described in Appendix 2, in which in the step of accepting access (S652), authentication information is accepted from the second user whether the second user is allowed to use the document data management service by the first means or the second means, and in the step of presenting (S634), if the second user is successfully authenticated based on the authentication information, document data is presented via the document data management service, and in the step of accepting access (S652), if there is a history of the second user being successfully authenticated using the authentication information, when access is made by the second user, the operations for inputting authentication information in the first means are reduced compared to the operations for inputting authentication information in the second means, allowing the second user to use the document data management service.

(Appendix 4)
A program as described in Appendix 1, in which in the sending step (S632), a notification is sent to the second user as a first means, the notification including first link information for launching an application that can be installed on the second user's terminal and is for using the document data management service, and as a second means, second link information for displaying a website for using the document data management service on a web browser, and in the presenting step (S634), the document data is presented to the second user on a screen displayed on the terminal by executing the application, or on a website screen displayed in a web browser on the terminal.

(Appendix 5)
The method executes the steps of: accepting access to the first link information from the second user (S6521a); accepting input of first authentication information related to the second user and input of second authentication information different from the first authentication information as authentication information from the second user to log in to the document data management service from the launched application (S6531a) (S6532a); and logging the second user in to the document data management service based on the input of the first authentication information and the second authentication information. In the step of logging in, The program described in Appendix 4, in which, when the second user accesses the document data management service using an application within a certain period of time after the input of authentication information, based on a history of the second user's successful login by inputting authentication information, in a step (S634) of logging in the second user to the document data management service and presenting the same, if the second user is logged in to the document data management service, document data for which the first user has requested approval is presented to the second user via the document data management service, even if no input of authentication information is received from the second user.

(Appendix 6)
The program described in Appendix 5 executes steps of accepting access to second link information from a second user, and accepting input of first authentication information and second authentication information as authentication information from the second user to log in to the document data management service from a website on the displayed web browser (S6531b) (S6532b), and in the login step, based on a history of successful logins by the second user through input of authentication information, when the second user accesses a website through the web browser within a certain period of time after the successful input of the authentication information, input of at least one of the first authentication information and the second authentication information is accepted as authentication information, and the second user is logged in to the document data management service.

(Appendix 7)
The method includes the steps of: accepting access to the first link information from the second user; accepting input of first authentication information related to the second user and input of second authentication information different from the first authentication information as authentication information from the second user from the launched application in order to execute login to the document data management service (S6531a) (S6532a); and logging the second user in to the document data management service based on the input of the first authentication information and the second authentication information. In the step of logging in, the second user is logged in by input of the authentication information. The program described in Appendix 4, in which, when a second user accesses the document data management service using an application within a certain period of time after input of the authentication information related to the success, input of either the first authentication information or the second authentication information is accepted from the second user, thereby logging the second user in to the document data management service and presenting the information (S634), when the second user is logged in to the document data management service, document data for which approval is requested by the first user is presented to the second user via the document data management service.

(Appendix 8)
The program described in Appendix 5 executes steps of accepting access to second link information from a second user, and accepting input of first authentication information and second authentication information as authentication information from the second user to log in to the document data management service from a website on the displayed web browser (S6531b) (S6532b), and in the login step, based on a history of successful logins by the second user through input of authentication information, when the second user accesses a website through the web browser within a certain period of time from the successful input of the authentication information, input of both the first authentication information and the second authentication information is accepted as authentication information, and the second user is logged in to the document data management service.

(Appendix 9)
A method for providing a document data management service that is executed by a computer having a processor (29) and a memory (15) and manages document data and the approval status of the document data by each user, the method comprising the steps of: receiving, from a first user, an operation for designating document data to be approved and designating one or more second users who will approve the document data (S601); sending, to the designated second user, a notification for requesting approval of the document data, the notification including link information for starting to use the document data management service, which is not information on an access destination for the document data to be approved (S632); receiving, from the second user, access to the link information included in the notification (S652); and presenting, to the second user, access information for displaying, based on the access to the accepted link information, the document data for which approval is requested by the first user, via the document data management service (S634).

(Appendix 10)
An information processing device comprising a control unit (29) and a memory unit (15), the information processing device for providing a document data management service for managing document data and the approval status of the document data by each user, the control unit executing the following steps: a step of receiving, from a first user, an operation for designating document data to be approved and designating one or more second users who will approve the document data (S601); a step of sending, to the designated second user, a notification for requesting approval of the document data, the notification including link information for starting to use the document data management service, which is not information on an access destination of the document data to be approved (S632); a step of receiving, from the second user, access to the link information included in the notification (S652); and a step of presenting, to the second user, access information for displaying the document data for which approval is requested by the first user, via the document data management service, based on the access to the accepted link information (S634).

(Appendix 11)
A method for manufacturing a document data management system, comprising providing a program to an information processing device for providing users with a document data management service that manages document data and the approval status of the document data by each user, the information processing device receiving an operation from a first user to designate document data to be approved and one or more second users who will approve the document data (S601); sending a notification to the specified second user requesting approval of the document data, the notification including link information for starting use of the document data management service, the notification being not information on an access destination of the document data to be approved (S632); receiving access to the link information included in the notification from the second user (S652); and presenting the document data for which approval is requested by the first user to the second user via the document data management service based on the access to the accepted link information (S634).

1: Electronic contract system, 10: Recipient side terminal device, 12: Communication IF, 13: Input device, 14: Output device, 15: Memory, 16: Storage unit, 19: Processor, 20: Server, 22: Communication IF, 23: Input/output IF, 25: Memory, 26: Storage, 29: Processor, 30: Sender side terminal device, 32: Communication IF, 33: Input device, 34: Output device, 35: Memory, 36: Storage unit, 39: Processor, 80: Network, 111: Antenna, 121: Wireless communication unit, 130: Operation reception unit, 132: Display, 140: Audio processing unit, 141: Microphone, 142: Speaker Car, 150: location information sensor, 160: camera, 161: electronic contract management information, 162: approver information at time of transmission, 163: approval history, 191: input operation reception unit, 192: transmission/reception unit, 193: data processing unit, 194: notification control unit, 201: communication unit, 202: storage unit, 203: control unit, 2021: electronic contract management database, 2022: approver information at time of transmission, 2023: approval history, 2031: reception control module, 2032: transmission control module, 2033: electronic contract information acquisition module, 2034: approver user information acquisition module, 2035: approval date and time information acquisition module

Claims (11)

A program for providing a document data management service that manages document data and an approval state of the document data by each user, the program being executed by a computer having a processor and a memory, the program comprising:
receiving an operation from a first user to designate the document data to be approved and to designate one or more second users who approve the document data;
sending a notification to the designated second user for requesting approval of the document data, the notification including link information for starting use of the document data management service, which is not information on an access destination of the document data to be approved;
receiving access to the link information included in the notification from the second user;
and a step of presenting the document data for which approval is requested by the first user to the second user via the document data management service based on access to the accepted link information. In the sending step, the link information included in the notification is
first link information for using the document data management service by a first means;
and second link information for using the document data management service by a second means different from the first means,
2. The program according to claim 1, wherein in the presenting step, the document data is presented to the second user by the first means or the second means. In the step of accepting the access, whether the second user is allowed to use the document data management service by the first means or the second means, authentication information is accepted from the second user;
presenting the document data via the document data management service when the second user is successfully authenticated based on the authentication information in the presenting step;
3. The program according to claim 2, wherein, in the step of accepting access, if there is a history of successful authentication of the second user using the authentication information, when access is made by the second user, the operations for inputting the authentication information in the first means are reduced compared to the operations for inputting the authentication information in the second means, thereby allowing the second user to use the document data management service. In the transmitting step,
as the first means, first link information for starting an application that can be installed on a terminal of the second user and is used to utilize the document data management service;
as the second means, transmitting the notification to the second user, the notification including second link information for displaying a website for using the document data management service on a web browser;
In the presenting step,
A screen displayed on the terminal by executing the application, or
4. The program according to claim 3, further comprising: presenting the document data to the second user on a screen of the website displayed by the web browser on the terminal. receiving access to the first link information from the second user;
receiving, as the authentication information, input of first authentication information related to the second user and input of second authentication information different from the first authentication information, in order to execute login to the document data management service from the launched application from the second user;
and logging in the second user to the document data management service based on input of the first authentication information and the second authentication information.
in the step of logging in, when the second user accesses the document data management service by the application within a certain period of time from the successful input of the authentication information based on a history of the second user's successful login by the input of the authentication information, the second user is logged in to the document data management service without receiving the input of the authentication information from the second user;
In the presenting step, when the second user is logged in to the document data management service, the document data for which approval is requested by the first user is presented to the second user via the document data management service.
The program according to claim 4. receiving access to the second link information from the second user;
receiving, from the second user, input of the first authentication information and the second authentication information as the authentication information in order to execute logging-in to the document data management service from the website on the displayed web browser;
6. The program of claim 5, wherein, in the login step, based on a history of successful logins of the second user by inputting the authentication information, when the second user accesses the website using the web browser within a certain period of time after the successful input of the authentication information, input of at least one of the first authentication information and the second authentication information is accepted as the authentication information, and the second user is logged in to the document data management service. receiving access to the first link information from the second user;
receiving, as the authentication information, input of first authentication information related to the second user and input of second authentication information different from the first authentication information, in order to execute login to the document data management service from the launched application from the second user;
and logging in the second user to the document data management service based on input of the first authentication information and the second authentication information.
in the step of logging in, when the second user accesses the document data management service by the application within a certain period of time from the input of the authentication information related to the successful login by the second user based on a history of the second user's successful login by the input of the authentication information, the second user is logged in to the document data management service by accepting input of either the first authentication information or the second authentication information from the second user;
In the presenting step, when the second user is logged in to the document data management service, the document data for which approval is requested by the first user is presented to the second user via the document data management service.
The program according to claim 4. receiving access to the second link information from the second user;
receiving, from the second user, input of the first authentication information and the second authentication information as the authentication information in order to execute logging-in to the document data management service from the website on the displayed web browser;
6. The program of claim 5, wherein, in the login step, based on a history of the second user successfully logging in by inputting the authentication information, when the second user accesses the website using the web browser within a certain period of time after the successful input of the authentication information, the program accepts input of both the first authentication information and the second authentication information as the authentication information, and logs the second user into the document data management service. 1. A method for providing a document data management service for managing document data and an approval state of the document data by each user, the method comprising:
The processor,
receiving an operation from a first user to designate the document data to be approved and to designate one or more second users who approve the document data;
sending a notification to the designated second user for requesting approval of the document data, the notification including link information for starting use of the document data management service, which is not information on an access destination of the document data to be approved;
receiving access to the link information included in the notification from the second user;
presenting access information to the second user, via the document data management service, for displaying the document data for which approval is requested by the first user, based on the accepted access to the link information;
How to do it. An information processing device including a control unit and a storage unit, the information processing device for providing a document data management service for managing document data and an approval state of the document data by each user, the control unit:
receiving an operation from a first user to designate the document data to be approved and to designate one or more second users who approve the document data;
sending a notification to the designated second user for requesting approval of the document data, the notification including link information for starting use of the document data management service, which is not information on an access destination of the document data to be approved;
receiving access to the link information included in the notification from the second user;
presenting access information for displaying the document data for which approval is requested by the first user to the second user via the document data management service based on the accepted access to the link information;
An information processing device that executes the above. A method for manufacturing a document data management system, comprising:
An information processing apparatus for providing a document data management service to a user, the document data management service managing document data and an approval state of the document data by each user, comprising:
receiving an operation from a first user to designate the document data to be approved and to designate one or more second users who approve the document data;
sending a notification to the designated second user for requesting approval of the document data, the notification including link information for starting use of the document data management service, which is not information on an access destination of the document data to be approved;
receiving access to the link information included in the notification from the second user;
presenting the document data, the approval of which is requested by the first user, to the second user via the document data management service based on the accepted access to the link information;
and providing a program for executing the above steps.