Information processing system, information processing method, and program

Abstract

To provide a system that enables another user to acquire data of a user on the basis of an operation input of the user before an account of the user for accessing a server is deleted.SOLUTION: In a taking over system, a taking over server 100 includes: an acquisition section 120 for acquiring configuration information indicating a configuration of user data of a first user stored in a cloud server, which is associated with account information of the first user for accessing the cloud server; a display processing section 130 for displaying a first authority selection screen for the first user to select whether to set authority to personal data which is data that only the first user can acquire or to set the authority to shared data which is data that a user different from the first user in addition to the first user can acquire on a terminal device of the first user; and a request section 170 for requesting the shared data among the data indicated in the configuration information of the server according to an operation input of the first user.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing method, and a program.

Background Art

[0002] An apparatus that estimates the content of a group change in accordance with a change in the group to which a user belongs has been disclosed (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a server that sets access rights for a user, there is a difference in the review work of access rights depending on whether the organizational change in the organization is only a name change or a merger or split with another department. The information processing apparatus described in Patent Document 1 is an apparatus that estimates whether the name of the organization to which the user belongs has been changed or abolished. Thereby, the information processing apparatus can prompt the user to perform an appropriate operation such as permission change by presenting the estimated result to the user. However, in the information processing apparatus described in Patent Document 1, when a user leaves the organization, the account for the user to access the server is deleted, so that after the user leaves, no one can acquire the data of the user.

[0005] Therefore, an object of the present invention is to provide a system that enables other users to acquire the data of a user based on the operation input of the user before the account of the user for accessing the server is deleted in order to solve the above problems.

Means for Solving the Problems

[0006] An information processing system according to one aspect of the present invention includes: an acquisition unit that acquires configuration information indicating at least the configuration of user data, which is data of the first user stored on the server and associated with the account information of the first user for accessing the server; a display processing unit that displays a first permission selection screen on the terminal device of the first user, which associates a first selection object for the first user to choose whether to set it as personal data, which is data that only the first user can acquire, or as shared data, which is data that the first user and other users can acquire, with the data shown in the configuration information; and a request unit that requests the server for the shared data from the data shown in the configuration information in response to the operation input of the first user to the first selection object.

[0007] An information processing method according to one aspect of the present invention involves a computer acquiring configuration information that shows at least the configuration of user data, which is data of the first user stored on the server and associated with the account information of the first user for accessing the server; displaying a first permission selection screen on the first user's terminal device, which associates a first selection object with the data shown in the configuration information, for the first user to choose whether to set it as personal data, which is data that only the first user can acquire, or as shared data, which is data that the first user and other users can acquire; and requesting the shared data from the server in response to the first user's operation input to the first selection object.

[0008] A program according to one aspect of the present invention causes a computer to perform the following actions: obtain configuration information indicating at least the configuration of user data, which is data of the first user stored on the server and associated with the account information of the first user for accessing the server; display a first permission selection screen on the first user's terminal device, which associates a first selection object with the data shown in the configuration information, for the first user to choose whether to set it as personal data, which is data that only the first user can obtain, or as shared data, which is data that the first user and other users can obtain; and request the shared data from the server, which is the data shown in the configuration information, in response to the first user's operation input to the first selection object. [Effects of the Invention]

[0009] According to the present invention, before a user's account for accessing a server is deleted, the user's data can be made available to other users based on the user's input. [Brief explanation of the drawing]

[0010] [Figure 1] This is a diagram showing an example of the configuration of the handover system. [Figure 2] This figure shows an example of the overview of the handover system's processing. [Figure 3] This diagram shows an example of the configuration of the handover server. [Figure 4] This figure shows an example of company information. [Figure 5] This figure shows an example of employee departure information. [Figure 6] This is a diagram showing an example of a permission selection screen. [Figure 7] This is a diagram showing an example of a permission input screen. [Figure 8] This figure shows an example of the acquisition selection screen. [Figure 9] This figure shows an example of the configuration of a terminal for employees who have left the company. [Figure 10] This is a diagram showing an example of the configuration of a cloud server. [Figure 11] This is a diagram showing an example of user data. [Figure 12] This is a flowchart showing an example of the processing of a transfer system. [Figure 13] This is a diagram showing an example of the configuration of a transfer server according to a modified example. [Figure 14] This is a diagram showing an example of a personal selection screen. [Figure 15] This is a diagram showing another example of an authority selection screen. [Figure 16] This is a flowchart showing an example of the processing of a transfer system according to a modified example. [Figure 17] This is a diagram showing an example of the hardware configuration of a computer.

Mode for Carrying Out the Invention

[0011] Hereinafter, the transfer system 10 in an embodiment of the present invention will be described in detail with reference to the drawings. However, the embodiments described below are merely examples, and there is no intention to exclude various modifications and applications of technologies not explicitly described below. That is, the present invention can be implemented with various modifications or by combining each embodiment without departing from its gist. Also, in the description of the following drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0012] ===Overview of Transfer System 10=== The handover system 10 is a system that enables the handover of data stored on a cloud server by an employee who leaves the company (hereinafter referred to as "the employee who left") to a designated person (hereinafter referred to as "the handover person") when the employee leaves the company. On the cloud server, for example, after a certain period of time has passed since the employee left, the employee's account for accessing the cloud server is deleted. As a result, after the employee leaves the company, no one can retrieve the employee's data from the cloud server. The handover system 10 asks the employee who left to select the data from their employee data that they want to hand over to the handover person before they leave the company. Hereinafter, for convenience, the data selected by the employee as the data to be handed over to the handover person will be referred to as "the candidate data for handover." After the employee leaves the company, the handover system 10 asks the handover person to select the necessary data from the candidate data for handover. Hereinafter, for convenience, the data selected by the transferee from the transfer candidate data will be referred to as "confirmed transfer data." The transfer system 10 configures the cloud server 400 to allow the transferee to retrieve the confirmed transfer data. This ensures that even after the departing employee's account is deleted, the transferee can retrieve the necessary data from the departing employee's data, thus preventing the departing employee from missing any data during the transfer. The transferee may be an individual, or a department or section within a company.

[0013] <<Overview of the handover system 10 configuration>> Referring to FIG. 1, the configuration of the handover system 10 will be described. FIG. 1 is a diagram showing an example of the configuration of the handover system 10. As shown in FIG. 1, the handover system 10 includes, for example, a handover server 100, a terminal device 200 of a departing employee (hereinafter referred to as the "departing employee terminal 200"), a terminal device 300 of a successor (hereinafter referred to as the "successor terminal 300"), and a cloud server 400. The handover server 100, the departing employee terminal 200, the successor terminal 300, and the cloud server 400 are communicably connected through a network N. The handover server 100 is set for the successor, for example, to be able to acquire the departing employee data stored in the cloud server 400 after the departing date of the departing employee. The departing employee terminal 200 allows the departing employee to select handover candidate data among the departing data by receiving the operation input of the departing employee. Further, the departing employee terminal 200 allows the departing employee to select a successor to whom the selected handover candidate data is to be handed over. The successor terminal 300 allows the successor to select handover confirmation data that the successor desires to acquire among the handover candidate data by receiving the operation input of the successor. The cloud server 400 is, for example, a server device operated by a business operator different from the company. The cloud server 400 stores various data in association with the user's account. In FIG. 1, as an example, the successor terminal 300 is shown as being composed of one terminal device, but the successor terminal 300 may be composed of a plurality of terminal devices. That is, the departing employee can set the departing employee data to be acquirable by a plurality of successors through the handover server 100.

[0014] <<Overview of the Processing of the Handover System 10>> Next, referring to FIG. 2, the overview of the processing of the handover system 10 will be described. FIG. 2 is a diagram showing an example of the overview of the processing of the handover system 10.

[0015] First, in step S10, the handover server 100 registers, for example, its account information (hereinafter referred to as "handover account information") with the cloud server 400. Here, the handover account information is, for example, information about an account that grants the handover server 100 unlimited permission to operate on the departing employee data on the cloud server 400.

[0016] Next, in step S11, the employee terminal 200 receives input from the employee regarding account information for accessing the cloud server 400 (hereinafter referred to as "employee account information"), and accesses the cloud server 400, for example, through the handover server 100. In step S12, the handover server 100 requests the cloud server 40 to copy at least the information regarding the list of root folders among the employee data (hereinafter referred to as "configuration information") to a storage area on the cloud server 400 corresponding to the handover account information. In step S13, the cloud server 400 copies the configuration information to the storage area corresponding to the handover account information in response to the request.

[0017] Next, in step S14, the handover server 100 generates information (hereinafter referred to as "authority selection screen information") related to a screen (hereinafter referred to as "authority selection screen T10") for selecting whether the data included in the configuration information is data to be deleted after the employee leaves the company (hereinafter referred to as "personal data") or candidate data to be handed over to the handover agent. That is, the handover server 100 processes, for example, personal data as data that will not be handed over from the employee to the handover agent. The handover server 100 also processes, for example, candidate data to be handed over from the employee to the handover agent. Here, the authority selection screen information may be, for example, information to be displayed in a browser or information to be displayed in a predetermined application. The handover server 100 sends the authority selection screen information to the employee terminal 200. The authority selection screen T10 will be described later.

[0018] Next, in step S15, the employee terminal 200 displays the authorization selection screen T10 on the display unit 1007. The employee terminal 200 generates information (hereinafter referred to as "authorization selection result information") regarding the result of whether each piece of data included in the employee data was selected as personal data or transfer candidate data, based on the employee's input to the authorization selection screen T10. The employee terminal 200 transmits the authorization selection result information to the transfer server 100.

[0019] Next, in step S16, the handover server 100 may generate information (hereinafter referred to as "permission input screen information") regarding a screen (hereinafter referred to as "permission input screen T20") for setting the transferee of the data selected as transfer candidate data from the employee data who has left the company, based on the permission selection result information. The permission input screen information may be, for example, information to be displayed in a browser, or information to be displayed in a predetermined application. The handover server 100 sends the permission input screen information to the employee terminal 200. The permission input screen T20 will be described later.

[0020] Next, in step S17, the employee terminal 200 displays the permission input screen T20 on the display unit 1007. The employee terminal 200 generates information about the successor (hereinafter referred to as "successor setting information") set for each of the data selected as candidate data for handover from the employee data, for example, based on the employee's operation input to the permission input screen T20. The employee terminal 200 transmits the successor setting information to the handover server 100.

[0021] Next, in step S18, the handover server 100 may generate information (hereinafter referred to as "acquisition selection screen information") related to a screen (hereinafter referred to as "acquisition selection screen T30") that associates objects (hereinafter referred to as "selection objects") for the handover candidate data selected by the departing employee in step S14 with the handover candidate data. The handover server 100 transmits the acquisition selection screen information to the handover terminal 300 of the handover employee indicated by the handover setting information, for example, after the departing employee's departure date has passed. The acquisition selection screen T30 will be described later.

[0022] Next, in step S19, the transferee terminal 300 displays the acquisition selection screen T30 on the display unit 1007. The transferee terminal 300 may, for example, generate information about the data selected as confirmed transfer data from the transferee's operation input to the acquisition selection screen T30 (hereinafter referred to as "acquisition selection result information"). The transferee terminal 300 transmits the acquisition selection result information to the transfer server 100.

[0023] Next, in step S20, the handover server 100 requests the cloud server 400 to copy the handover confirmation data, for example, based on the acquired selection result information. The cloud server 400 may, in response to the request from the handover server 100, store the copy of the handover confirmation data, associating it with the handover user's account information associated with each piece of handover confirmation data. This allows the handover user to appropriately acquire the data they deem necessary, other than the personal data of the departing employee, using their own account.

[0024] ===Configuration of handover server 100=== Next, the configuration of the handover server 100 will be described with reference to Figure 3. Figure 3 is a diagram showing an example of the configuration of the handover server 100. As shown in Figure 3, the handover server 100 includes, for example, a storage unit 110, an acquisition unit 120, a display processing unit 130, a determination unit 140, a specification unit 150, a setting unit 160, and a request unit 170.

[0025] The storage unit 110 stores, for example, company information D111 and employee departure information D112. First, company information D111 will be described with reference to Figure 4. Figure 4 is a diagram showing an example of company information D111. As shown in Figure 4, company information D111 may include, for example, the following items: [Company ID], [Employee ID], [Name], [Account Information], [Department], and [Email Address]. [Company ID] is, for example, an item containing the company ID, which is the identification information of the company to which the employee belongs. [Employee ID] is, for example, an item associated with the [Company ID] item and containing the employee ID, which is the identification information of the employee of the company. [Name] is an item associated with the [Employee ID] item and contains information about the employee's name. [Account Information] is an item associated with the [Employee ID] item and contains information about the account set up for each employee to access the cloud server 400. [Department] is an item associated with the [Employee ID] item and contains information about the department within the company to which the employee belongs (for example, the name of the department and the IDs of other employees belonging to that department). The [Email Address] field is associated with the [Employee ID] field and contains information about the employee's email address.

[0026] Next, with reference to Figure 5, the departing employee information D112 will be explained. Figure 5 is a diagram showing an example of departing employee information D112. As shown in Figure 5, departing employee information D112 may include items such as [departing employee ID], [employee ID], [authority selection result information], [transferee setting information], and [acquisition selection result information]. [departing employee ID] is an item that includes, for example, the departing employee ID, which is the identification information of the employee who is leaving the company. [Employee ID] is an item that is associated with the [departing employee ID] item and includes, for example, the employee ID, which is the identification information of the company's employee. [authority selection result information] is an item that includes, for example, the authority selection result information generated by the departing employee's operation input on the authority selection screen T10. Specifically, in Figure 5, the authority selection result information includes, for example, information about whether each piece of data included in the departing employee data is personal data or transfer candidate data (for example, "transfer folder" is set as "transfer candidate data"). [Transferee Setting Information] is an item that includes transferee setting information generated, for example, by the departing employee's operation input on the permission input screen T20. Specifically, in Figure 5, the transferee setting information includes, for example, the employee ID (e.g., 10111) of the employee who has been set as the transferee for the data selected as transfer candidate data from the departing employee data (e.g., transfer folder). [Acquisition Selection Result Information] is an item that includes acquisition selection result information generated, for example, by the transferee's operation input on the acquisition selection screen T30. Specifically, in Figure 5, the acquisition selection result information includes, for example, information associating the transferee (e.g., employee ID (10111)) with the transfer confirmation data selected by the transferee (e.g., "transfer folder", "past project folder").

[0027] Furthermore, the company information D111 and employee departure information D112 stored in the memory unit 110 do not necessarily have to be stored in the handover server 100; for example, they may be stored in a device other than the handover server 100. In this case, the handover server 100 only needs to retrieve the company information D111 and employee departure information D112 from that device.

[0028] The acquisition unit 120 acquires various types of information, for example, between the employee terminal 200, the successor terminal 300, and the cloud server 400.

[0029] The display processing unit 130 generates information related to various screens, such as those shown in Figures 6 to 8. The display processing unit 130 also performs processing to display various screens on the display units 1007 of the employee terminal 200 and the employee terminal 300. Examples of various screens will be described below with reference to Figures 6 to 8.

[0030] First, the permission selection screen T10 will be explained with reference to Figure 6. Figure 6 is a diagram showing an example of the permission selection screen T10. The permission selection screen T10 is a screen that is displayed on the display unit 1007 of the employee terminal 200, for example. As shown in Figure 6, the permission selection screen T10 may include, for example, a data name T11, an updater name T12, a data sharing status T13, a selected object T14, a confirmation status mark T15, and a complete button T16. The data name T11 is an object that indicates, for example, the name of a folder or file included in the employee data. The updater name T12 is an object that indicates, for example, the name of the user who last updated the employee data corresponding to the data name T11. The data sharing status T13 is an object that indicates, for example, the sharing status that has been set in advance for a folder or file. Specifically, the data sharing status T13 displays, for example, "Private" for data that the employee has set as personal data, and "Shared" for data that the employee has set to be accessible to other employees. The selection object T14 is an object displayed in association with each of the data names T11, for example. The selection object T14 includes, for example, a personal selection box T141 and a handover candidate selection box T142. The selection object T14 is an object for setting whether the departing employee data corresponding to the data name T11 is personal data or handover candidate data by receiving operation input from the departing employee. Specifically, when the handover server 100 receives operation input from the departing employee in the personal selection box T141, it sets the departing employee data corresponding to the personal selection box T141 as personal data. Similarly, when the handover server 100 receives operation input from the departing employee in the handover candidate selection box T142, it sets the departing employee data corresponding to the handover candidate selection box T142 as handover candidate data. This allows departing employees to easily set their data as personal data or handover candidate data before leaving the company, thus enabling a smooth data handover process to the handover candidate. The confirmation status mark T15 is an object displayed in association with each of the data names T11, for example. The confirmation status mark T15 may include, for example, a confirmed mark T151 and an unconfirmed mark T152.In Figure 6, as an example, a confirmation mark T151 is displayed associated with selected objects T14 that have been selected after receiving input from a departing employee, and an unconfirmed mark T152 is displayed associated with selected objects T14 that have not received input from a departing employee. This makes it easy for departing employees to confirm whether each of the departing employee data is personal data or candidate data for transfer, thereby improving user convenience. The complete button T17 is, for example, a button for confirming the settings made by the departing employee regarding the departing employee data. The permission selection screen T10 may also be a screen generated by adding, for example, the selected objects T14 and the confirmation status mark T15 to configuration information that shows a list of root folders.

[0031] The permission input screen T20 will be described with reference to Figure 7. Figure 7 is a diagram showing an example of the permission input screen T20. The permission input screen T20 is a screen that is displayed on the display unit 1007 of the employee terminal 200, for example. As shown in Figure 7, the permission input screen T20 may be a screen that is displayed as a pop-up when the employee who is leaving the company inputs an operation to the handover candidate selection box T142 in the permission selection screen T10. The permission input screen T20 may include, for example, a data name T21, a handover setting object T22, a handover name T23, and a confirmation object T24. The data name T21 is an object that indicates the name of the data corresponding to the selection object T14 selected by the employee who is leaving the company in the permission selection screen T10, for example. The handover setting object T22 is an object for setting the handover of the data displayed in the data name T21, for example. The handover name T23 is an object that indicates the name of the handover that has been set, for example. The confirmation object T24 is a button for confirming the handover that has been set, for example. This allows departing employees to easily set a successor in the successor candidate data, thereby improving user convenience.

[0032] The acquisition selection screen T30 will be explained with reference to Figure 8. Figure 8 is a diagram showing an example of the acquisition selection screen T30. The acquisition selection screen T30 is a screen that is displayed, for example, on the display unit 1007 of the handover terminal 300. In Figure 8, as an example, the acquisition selection screen T30 is shown on the terminal device of "Mr. B" who has been set as the handover person. The acquisition selection screen T30 is a screen that displays a list of data that corresponds to the handover candidate selection box T142 selected by the departing employee on the authorization selection screen T10, and for which "Mr. B" has been set as the handover person on the permission input screen T20. In addition, the acquisition selection screen T30 may also display data that has been marked with an unconfirmed mark T152 on the authorization selection screen T10. In other words, the acquisition selection screen T30 may also display data for which it has not been decided whether or not it should be handed over to the handover person by the departing employee on the authorization selection screen T10. This improves the convenience for departing employees because the handover server 100 can allow the handover server to determine whether or not the data is to be handed over by the departing employee. As shown in Figure 8, the acquisition selection screen T30 may include, for example, the data name T31, the updater name T32, the data sharing status T33, the selected object T34, the confirmation status mark T35, and the complete button T36. Here, the data name T31, the updater name T32, the data sharing status T33, the confirmation status mark T35, and the complete button T36 are the same as the data name T11, the updater name T12, the data sharing status T13, the confirmation status mark T15, and the complete button T16, so their explanation is omitted. The selected object T34 includes, for example, a selection box T341. The selection box T341 is displayed, for example, corresponding to each of the names in the data name T31. The selection box T341 is an object that accepts input from the successor and sets the employee data corresponding to data name T11 as confirmed handover data that the successor can obtain. In other words, when the handover server 100 receives input from the successor in the selection box T341, it sets the employee data corresponding to the selection box T341 as confirmed handover data.Furthermore, the handover server 100 may set the departing employee data corresponding to selection box T341 that has not been selected by the handover user's input as data that is not to be handed over to the handover user, and to be discarded when the departing employee's account is deleted after the employee leaves the company. This improves user convenience because the handover user can easily select the desired data from the candidate handover data.

[0033] The determination unit 140 determines, for example, whether the employee who has left the company has met predetermined conditions. Specifically, the determination unit 140 determines, for example, whether completion information has been obtained from the employee terminal 200. The determination unit 140 also determines, for example, whether the date of departure has passed.

[0034] The identification unit 150 identifies, for example, the transfer candidate data, the transferee, and the transfer confirmed data based on various information generated in response to the user's operation input to the terminal device. Specifically, the identification unit 150 may, for example, identify whether each piece of data included in the transferee data has been selected as personal data or transfer candidate data, based on the permission selection result information obtained from the transferee terminal 200. In the transferee selection status shown in Figure 6, the identification unit 150 may identify the "Nasu Fuyu" file and the "Payroll Statement - January" file as personal data. The identification unit 150 may also identify the "Transfer" folder, the "Past" folder, and the "Transfer Plan" file as transfer candidate data. Furthermore, the identification unit 150 may identify the "Renewal PJ" folder and the "Job Change" folder as not being selected as either personal data or transfer candidate data. Furthermore, the identification unit 150 may, for example, identify the person who will take over the employee data corresponding to the selected selection object T14 based on the person who took over setting information obtained from the employee terminal 200. In the employee setting situation shown in Figure 7, the identification unit 150 may identify "Mr. B" and "Department Head C" as the person who will take over. Furthermore, the identification unit 150 may, for example, identify the confirmed handover data that the handover candidate data included in the employee data has selected as necessary, based on the acquired selection result information obtained from the handover terminal 300. In the handover selection situation shown in Figure 8, the identification unit 150 may identify the "Handover" folder, the "Past" folder, and the "Handover Plan" file as confirmed handover data that the handover will take over.

[0035] The configuration unit 160, for example, based on the various data identified by the identification unit 150, sets the successor as a user capable of acquiring predetermined data (e.g., successor candidate data, successor confirmed data) from the employee data. Specifically, the configuration unit 160 sets the successor corresponding to the successor candidate data identified by the identification unit 150 as a user capable of acquiring said successor candidate data. This allows the successor server 100 to set the successor terminal 300 of the configured successor as a target for transmitting acquisition selection screen information. Furthermore, the configuration unit 160 sets the successor corresponding to the successor confirmed data identified by the identification unit 150 as a user capable of acquiring said successor confirmed data. This allows the successor server 100 to cause the cloud server 400 to create a copy of the successor confirmed data associated with the successor in the storage area of ​​the cloud server 400 associated with the configured successor's account.

[0036] The request unit 170 requests the cloud server 400 to make available, for example, data set by the departing employee or their successor (e.g., successor candidate data, successor confirmed data) from the departure data so that the successor set in the setting unit 160 can obtain it. Specifically, the request unit 170 may, for example, after the departing employee has left the company, request the cloud server 400 to create a copy of the successor confirmed data corresponding to that successor in the storage area of ​​the cloud server 400 corresponding to the account of the successor set in the setting unit 160. Also, specifically, the request unit 170 may, for example, after the departing employee has left the company, request the cloud server 400 to send the successor confirmed data to the successor server 100 or to the successor corresponding to that successor confirmed data. Furthermore, the request unit 170 may, for example, before the departing employee leaves the company, request the cloud server 400 to create a copy of the successor candidate data in the storage area of ​​the cloud server 400 corresponding to the account of the successor server 100. Furthermore, the request unit 170 may, for example, request the cloud server 400 to send the candidate data for handover to the handover server 100 or to the handover person corresponding to the confirmed handover data before the employee leaves the company. This allows the handover server 100 to ensure that the handover person can obtain the candidate data and confirmed handover data of the employee even if the employee's account is deleted, thereby preventing the employee from missing any data during the handover process.

[0037] ===Configuration of Departure Terminal 200 and Transfer Terminal 300=== Referring to Figure 9, the configurations of the departing employee terminal 200 and the handover terminal 300 will be described. Figure 9 is a diagram showing an example of the configuration of the departing employee terminal 200. For convenience, the handover terminal 300 is the same as the departing employee terminal 200, so its description will be omitted below. The departing employee terminal 200 displays various screens on the display unit 1007 based on information acquired from the handover server 100, for example. The departing employee terminal 200 includes, for example, a storage unit 210, an acquisition unit 220, a display processing unit 230, and a transmission unit 240. The storage unit 210 stores various information, for example. The acquisition unit 220 acquires information related to various screens from the handover server 100 and the cloud server 400, for example. The display processing unit 230 displays the acquired information related to various screens on the display unit 1007, for example. The transmission unit 240 transmits various information to the handover server 100 and the cloud server 400, for example.

[0038] ===Cloud Server 400 Configuration=== The configuration of the cloud server 400 will be described with reference to Figure 10. Figure 10 is a diagram showing an example of the configuration of the cloud server 400. As shown in Figure 10, the cloud server 400 includes, for example, a storage unit 410, an acquisition unit 420, a display processing unit 430, and a transmission unit 440.

[0039] The storage unit 410 stores, for example, user data D411. User data D411 will be described with reference to Figure 11. Figure 11 is a diagram showing an example of user data D411. User data D411 includes, for example, account information and user data associated with each user. As shown in Figure 11, user data D411 may include, for example, the items [User ID], [Account Information], and [User Data]. [User ID] is, for example, an item containing the user ID, which is the identification information of a user using the cloud server 400. [Account Information] is, for example, an item associated with the [User ID] item and containing information about the account for which the user accesses the cloud server 400. [User Data] is, for example, an item associated with the [User ID] item and containing user data that the user has stored on the cloud server 400. User data may also include configuration information showing a list of root folders.

[0040] The acquisition unit 420 acquires various information from, for example, other devices. The display processing unit 430 generates information related to a screen for displaying the various information on the display unit of the user's terminal device. The transmission unit 440 transmits the various information to the user's terminal device.

[0041] ===Processing Procedure for Handover System 10=== Referring to Figures 6-8 and 12, an example of the processing of the handover system 10 will be explained. Figure 12 is a flowchart showing an example of the processing of the handover system 10. For convenience, the following explanation assumes that the employee leaves the company on March 31, 2021 (hereinafter referred to as the "date of departure"). Furthermore, it is assumed that the handover account information of the handover server 100 (an account that can operate on the employee's data without restriction) has already been registered on the cloud server 400.

[0042] Before their departure date, the departing employee accesses the handover system 10 to select candidate handover data from the departing employee data stored on the cloud server 400 to be handed over to their successor.

[0043] First, in step S100, the employee terminal 200 receives the employee's input and accesses the handover server 100.

[0044] Next, in step S101, the handover server 100 identifies the employee who has left the company based on the account information of the employee terminal 200, for example, by referring to the company information D111. The handover server 100 may also request the cloud server 400 to create a copy of the configuration information corresponding to the employee who has left, associated with the handover account. The handover server 100 may also obtain the configuration information that the employee terminal 200 has obtained from the cloud server 400 from the employee terminal 200. The procedure for the handover server 100 to obtain the configuration information is not limited. Next, in step S102, the cloud server 400 grants the handover server 100 access to the configuration information corresponding to the employee who has left the company, for example, by referring to the user data D411.

[0045] Next, in step S103, the handover server 100 adds the selection object T14 to the configuration information to generate information related to the authorization selection screen T10 (authorization selection screen information). The handover server 100 then sends the authorization selection screen information to the employee terminal 200.

[0046] Next, in step S104, the departing employee terminal 200 displays the authorization selection screen T10 (see Figure 6) on the display unit 1007. The departing employee terminal 200 accepts the departing employee's input for the selection object T14 on the authorization selection screen T10. After that, the departing employee terminal 200 may, for example, send the authorization selection result information to the handover server 100.

[0047] Next, in step S105, the handover server 100 stores, for example, the permission selection result information in the employee information D111. Based on the permission selection result information, the handover server 100 identifies the selected object T14 selected by the employee. Here, as an example, as shown in Figure 6, the handover server 100 explains that the handover candidate selection box T142 corresponding to the "Handover" folder has been selected by the employee. The handover server 100 identifies the handover candidate data corresponding to the handover candidate selection box T142.

[0048] Next, in step S106, the handover server 100 sends permission input screen information to the departing employee terminal 200 to display the permission input screen T20 (see Figure 7) as a pop-up when, for example, the handover candidate selection box T142 is selected.

[0049] Next, in step S107, the departing employee terminal 200 displays the permission input screen T20 on the display unit 1007. The departing employee terminal 200 receives the departing employee's operation input for the handover setting object T22. This allows the departing employee to set the handover candidate data corresponding to the handover setting object T22 for which the operation input was received. After that, the departing employee terminal 200 sends the handover setting information to the handover server 100, for example. Here, as an example, we will explain assuming that "Mr. B" and "Department Head C" have been set as handovers for the "Handover" folder on the departing employee terminal 200, as shown in Figure 7.

[0050] Next, in step S108, the handover server 100 stores, for example, the handover setting information in the employee information D111. The handover server 100 then determines, for example, whether it has received information (hereinafter referred to as "completion information") indicating that it has received an operation input for the completion button T17 on the permission selection screen T10 from the employee terminal 200. If completion information is obtained (step S108: YES), the handover server 100 proceeds to step S108. If completion information is not obtained (step S108: NO), the handover server 100 repeats the process from step S105. As a result, the handover server 100 determines that the handover candidate selection box T142 corresponding to the "Past (P)" folder and the "Handover Plan" file has been selected by the employee, as shown in Figure 6. The handover server 100 sets the handover person by accepting the departing employee's operation input on the permission input screen T20 for the handover candidate data selected in the handover candidate selection box T142, for example, as in step S107. The handover server 100 also identifies that the personal selection box T141 corresponding to the "Nasu Fuyu" file and the "Payroll Statement - January" file has been selected. The handover server 100 identifies the data for which the personal selection box T141 has been selected as not to be handed over. The handover server 100 also identifies that the selection object T14 corresponding to the "Renewal" folder and the "Job Change" folder has not been selected.

[0051] Next, in step S109, the handover server 100 may determine whether or not the date of departure has passed. If it is determined that the date of departure (in this case, March 31, 2021) has passed (step S109: YES), the handover server 100 sends the acquisition selection screen information to the handover terminal 300 (step S110). Specifically, as an example, the handover server 100 refers to the company information D111 and sends a URL (Uniform Resource Locator) associated with the acquisition selection screen T30 as acquisition selection screen information to the handover terminals 300 of "Mr. B" and "Department Head C," who are set as handovers for the "Handover" folder. Also, as an example, it is assumed that "Mr. B" is set as the handover for the "Handover" folder, the "Past" folder, and the "Handover Plan" file. Also, as an example, it is assumed that the "Renewal PJ" folder and the "Job Change" folder are not selected for either personal data or handover candidate data. This allows users to review potential successor data after an employee has left the company, without any changes made to the employee's departure data, thus improving user convenience.

[0052] Next, in step S111, the transferee terminal 300 (in this case, the terminal device of "Mr. B") displays the acquisition selection screen T30 (see Figure 8) on the display unit 1007 based on the acquisition selection screen information. The transferee terminal 300 displays, for example, the data in the configuration information for which "Mr. B" has been set as the transferee, and the data that was not selected for either personal data or transfer candidate data. That is, as an example, the transferee terminal 300 displays the "Transfer" folder, the "Past" folder, the "Transfer Plan" file, the "Renewal PJ" folder, and the "Job Change" folder as the acquisition selection screen T30, as shown in Figure 8. This allows the transfer server 100 to leave the decision of whether or not the data should be transferred by the departing employee to the transferee, thereby improving user convenience.

[0053] Next, in step S112, the transferee terminal 300 receives operation input from the transferee (in this case, "Mr. B") to the selection object T34. Specifically, as an example, the transferee terminal 300 receives operation input from the transferee to the "Transfer" folder, the "Past" folder, and the selection object T34 corresponding to the "Transfer" folder. The transfer server 100 identifies the transfer confirmation data corresponding to the selection box T342 that received the transferee's operation input. Subsequently, the transferee terminal 300 may, for example, send acquired selection result information including information about the transfer confirmation data to the transfer server 100. This allows the transfer server 100 to transfer only the data that the transferee deems necessary from among the transfer candidate data, thereby improving user convenience.

[0054] Next, in step S113, the handover server 100 stores, for example, the acquisition selection result information in the employee departure information D111. Based on the acquisition selection result information, the handover server 100 requests the cloud server 400 to store a copy of the handover confirmation data selected by the handover user in step S112 in a storage area accessible by the handover user's account information. This allows the handover system 10 to prevent handover omissions by the employee departure, as the handover user can acquire the desired employee departure data using their own account. Alternatively, the handover server 100 may store, for example, the handover confirmation data selected by the handover user in step S112 in the storage unit 110 of the handover server 100 (or in the storage unit of the server of the company to which the employee departure belongs). This improves user convenience, as the handover user can acquire the desired employee departure data by authentication to the handover server 100, regardless of their account on the cloud server 400.

[0055] In addition, while it was explained above that a copy of the confirmed handover data is requested after obtaining completion information (step S108: YES) and the departure date has passed (step S109: YES), the system is not limited to this. In the handover system 10, when completion information is obtained in the handover server 100, the handover server 100 may request a copy of the handover candidate data corresponding to the handover candidate selection box T142 selected by the departing employee from the cloud server 400. This makes it possible for the handover to obtain the departure data in their own account, regardless of whether the handover is desired or not, for data that the departing employee has not set as personal data, thus more reliably preventing handover omissions by the departing employee.

[0056] ===Transfer System 10a for Modifications=== <<Structure>> A modified version of the handover system 10a will be described with reference to Figures 13 and 14. For convenience, the explanation of aspects that are the same as those of the handover system 10 will be omitted below, and only the differences will be explained. Figure 13 is a diagram showing an example of the configuration of the handover server 100a related to the modified version. Figure 14 is a diagram showing an example of the personal selection screen T40.

[0057] The handover server 100a determines whether there is any data among the departing employee data that is pre-configured to be accessible to employees other than the departing employee (hereinafter referred to as "other employees") (hereinafter referred to as "shared setting data"). For example, if the handover server 100a determines that there is shared setting data, it accepts a setting from the departing employee indicating whether or not the shared setting data is personal data. This prevents the departing employee from forgetting to exclude their own data from the handover, which is pre-configured in the shared setting data, thereby improving user convenience. The configuration of the handover server 100a will be described below, followed by a description of the processing procedure of the handover server 100.

[0058] The determination unit 140a determines, based on the configuration information, whether each employee's data is set to be accessible to other employees. Specifically, the determination unit 140a determines, for example, whether folders or files have been pre-set to a shared state (set as shared setting data) by the employee in the configuration information.

[0059] The display processing unit 130a generates information related to, for example, the personal selection screen T40. The personal selection screen T40 will be described with reference to Figure 14. The personal selection screen T40 is a screen displayed on the display unit 1007 of the employee terminal 200 when, for example, the determination unit 140a determines that there is shared setting data. As shown in Figure 14, the personal selection screen T40 may include, for example, a data name T41, an updater name T42, a data sharing status T43, a selected object T44, a confirmation status mark T45, and a complete button T46. Here, the data name T41, updater name T42, data sharing status T43, and confirmation status mark T45 are the same as the data name T11, updater name T12, data sharing status T13, and confirmation status mark T15, so their explanation will be omitted. The selected object T44 is an object that allows the employee to select whether or not the employee data corresponding to the data name T41 is personal data by accepting the employee's input. The selection object T44 includes, for example, a personal selection box T441 and a non-personal selection box T442. The display processing unit 130a displays, for example, only the objects corresponding to the shared settings data among the personal selection box T441 and the non-personal selection box T442 so that the departing employee can select them. When the departing employee makes a selection in the personal selection box T441, the handover server 100 sets the departing employee data corresponding to the personal selection box T441 as personal data. Similarly, when the departing employee makes a selection in the non-personal selection box T442, the handover server 100 sets the departing employee data corresponding to the non-personal selection box T442 as data that is not personal data. This allows the handover server 100a to easily select whether or not the shared settings data is personal data, thereby improving user convenience. The completion button T47 is, for example, a button to confirm the settings for the departing employee data. The display processing unit 130a may, for example, make the completion button T47 selectable when all selectable selection objects T44 have been selected by the departing employee's input. This allows the handover server 100a to prevent omissions in the departing employee's operation to set personal data for the departing employee's data, thereby improving user convenience.

[0060] In the modified version of the handover server 100a, when the departing employee selects the complete button T46 on the personal selection screen T40, the permission selection screen T50 shown in Figure 15 may be displayed on the display unit 1007 of the departing employee terminal 200. Since the permission selection screen T50 corresponds to the permission selection screen T10 shown in Figure 6, the explanation of the various objects is omitted. In the permission selection screen T50 shown in Figure 15, the display processing unit 130a displays the selection object T54 as unselectable for the departing employee data corresponding to the personal selection box T441 selected on the personal selection screen T40. Specifically, as shown in Figure 15, the display processing unit 130a may place a check mark on the personal selection box T541 and then gray it out to display it as unselectable. This improves user convenience.

[0061] <<Processing>> Next, with reference to Figure 16, an example of the processing of the modified handover system 10a will be described. For convenience, the explanation of processing that is the same as that of the handover system 10 will be omitted below, and only the different processing will be described. Figure 16 is a flowchart showing an example of the processing of the modified handover system 10a. In the following description, as an example, it will be explained that after receiving the departing employee's input for the completion button T47 on the personal selection screen T40, the permission selection screen T50 is displayed on the departing employee's terminal 200.

[0062] This step is added after step S102 shown in Figure 12. In step S102a, the handover server 100 adds a selection object T14 to the configuration information to generate information related to the personal selection screen T40 (hereinafter referred to as "personal selection screen information"). At this time, based on the determination result in the determination unit 140a, the handover server 100 displays the selection object T44 corresponding to the employee data set as shared setting data so that it can be selected by the employee. In other words, the handover server 100 may gray out the checkbox for the selection object T44 set as personal setting data so that it cannot be selected. The handover server 100 transmits the personal selection screen information to the employee terminal 200.

[0063] Next, in step S102b, the departing employee terminal 200 displays the personal selection screen T40 (see Figure 14) on the display unit 1007. The departing employee terminal 200 accepts the departing employee's input for the selection object T44 on the personal selection screen T40. Subsequently, the departing employee terminal 200 may, for example, send to the handover server 100 information regarding the result of whether or not the shared setting data included in the departing employee data is personal data, based on the input to the personal selection screen T40 (hereinafter referred to as "personal selection result information").

[0064] Next, in step S102c, the handover server 100 identifies the selected object T44 selected by the departing employee based on the individual selection result information. Here, as an example, as shown in Figure 14, the handover server 100 assumes that the individual selection box T441 corresponding to the "Renewal PJ" folder and the "Nasu Fuyu" file has been selected by the departing employee. The handover server 100 then identifies the data that is not subject to handover, which corresponds to the individual selection box T441.

[0065] Next, in step S103a, which is a replacement for step S103 shown in Figure 12, the handover server 100 generates information (authority selection screen information) regarding the authorization selection screen T50 in which the personal selection box T541 corresponding to the "Renewal PJ" folder and the "Nasu Fuyu" file is selected. The handover server 100 sends the authorization selection screen information to the employee terminal 200.

[0066] Next is a step that replaces step S104 shown in Figure 12. In step S104a, the departing employee terminal 200 displays the authorization selection screen T50 on the display unit 1007. The departing employee terminal 200 accepts the departing employee's operation input for the selection object T54 on the authorization selection screen T50. After that, the departing employee terminal 200 may, for example, send the authorization selection result information to the handover server 100. This prevents the handover server 100a from missing operations to set personal data for the departing employee data, thereby improving user convenience. The processing after step S104a is the same as the processing from step S105 onwards in Figure 12, so its explanation is omitted.

[0067] ===Hardware Configuration=== The handover server 100 and cloud server 400 that implement the functions of the above-described embodiment may be, for example, a server computer, a personal computer (e.g., desktop, laptop, tablet, etc.), a media computer platform (e.g., cable, satellite set-top box, digital video recorder), a handheld computer device (e.g., PDA, email client, etc.), or other types of computers or communication platforms.

[0068] The employee terminal 200 and the successor terminal 300 that realize the functions according to the above-described embodiment may be, for example, a smartphone, a mobile phone (feature phone), a personal computer (e.g., desktop, laptop, tablet, etc.), a media computer platform (e.g., cable, satellite set-top box, digital video recorder), a handheld computer device (e.g., PDA (Personal Digital Assistant), email client, etc.), a wearable device (e.g., glasses-type device, watch-type device), another type of computer, or a communication platform.

[0069] Referring to Figure 17, an example of a hardware configuration when the handover server 100, the departing employee terminal 200, the handover terminal 300, and the cloud server 400 are implemented using computer 1000 will be described. Note that the various functions of the handover server 100, the departing employee terminal 200, the handover terminal 300, and the cloud server 400 can be implemented by dividing them among multiple devices.

[0070] Figure 17 shows an example of a computer hardware configuration. As shown in Figure 17, the computer 1000 includes, for example, a processor 101, memory 1002, storage device 1003, input I / F unit 1004, data I / F unit 1005, communication I / F unit 1006, and display unit 1007.

[0071] The processor 1001 is a control unit that controls various processes in the computer 1000 by executing programs stored in the memory 1002.

[0072] Memory 1002 is a storage medium such as RAM (Random Access Memory). Memory 1002 temporarily stores the program code of the program executed by the processor 1001, as well as data required during program execution.

[0073] The storage device 1003 is a non-volatile storage medium such as a hard disk drive (HDD) or flash memory. The storage device 1003 stores the operating system and various programs for realizing the above configurations.

[0074] The input interface unit 1004 is a device for receiving input from the user. Specific examples of the input interface unit 1004 include keyboards, mice, touch panels, various sensors, and wearable devices. The input interface unit 1004 may be connected to the computer 1000 via an interface such as USB (Universal Serial Bus).

[0075] The data I / F unit 1005 is a device for inputting data from outside the computer 1000. Specific examples of the data I / F unit 1005 include drive devices for reading data stored on various storage media. The data I / F unit 1005 may also be located outside the computer 1000. In that case, the data I / F unit 1005 would be connected to the computer 1000 via an interface such as USB.

[0076] The communication interface unit 1006 is a device for performing data communication via the Internet N with external devices of the computer 1000, either via wired or wireless connection. The communication interface unit 1006 may also be located outside the computer 1000. In that case, the communication interface unit 1006 is connected to the computer 1000 via an interface such as USB.

[0077] The display unit 1007 is a device for displaying various types of information. Specific examples of the display unit 1007 include liquid crystal displays, organic EL (Electro-Luminescence) displays, and displays for wearable devices. The display unit 1007 may be located outside the computer 1000. In that case, the display unit 1007 is connected to the computer 1000 via, for example, a display cable. Furthermore, if a touch panel is used as the input I / F unit 1004, the display unit 1007 can be integrated with the input I / F unit 1004.

[0078] ===Summary=== In this embodiment, the handover system 10 includes an acquisition unit 120 that acquires configuration information indicating the configuration of at least the departing employee data (user data), which is data of the departing employee (first user) stored in the cloud server 400 (server) and associated with the account information of the departing employee (first user) for accessing the cloud server 400 (server), and a separate unit that determines whether to set it as personal data, which is data that can only be acquired by the departing employee (first user), or as handover candidate data (shared data), which is data that can be acquired by the departing employee (first user) and other users different from the departing employee (first user). The system includes a display processing unit 130 that displays a permission selection screen T10 (first permission selection screen) on the departing employee's (first user's) terminal 200 (terminal device), which associates a selection object T14 (first selection object) for the employee (first user) to select with data shown in the configuration information, and a request unit 170 that requests the cloud server 400 (server) for transfer candidate data or transfer confirmation data (shared data) from the data shown in the configuration information in response to the departing employee's (first user's) operation input to the selection object T14 (first selection object) (for example, a request to create a copy, a request to send a copy, etc.). As a result, the transfer system 10 can make the data of a user available to other users based on the user's operation input before the user's account for accessing the server is deleted.

[0079] Furthermore, in the handover system 10 of this embodiment, the display processing unit 130 displays an authorization input screen T20 (first input screen), which is a screen that accepts input of identification information to identify a handover person (second user) who is set to be able to acquire handover candidate data or handover confirmed data (shared data), on the departing employee's (first user's) terminal 200 (terminal device). The setting unit further includes a setting unit that, in response to the departing employee's (first user's) operation input to the authorization input screen T20, sets the handover candidate data or handover confirmed data (shared data) to be available to the handover person (second user) (for example, creates a copy in the handover person's storage area on the cloud server 400). As a result, the departing employee can easily set the handover person for the handover candidate data, thereby improving user convenience.

[0080] Furthermore, in the handover system 10 of this embodiment, the display processing unit 130 displays an acquisition selection screen T30 on the handover terminal 300 (terminal device) of the handover user (second user), which is a screen that includes a list showing the handover candidate data (shared data) that has been set to be available for acquisition by the handover user (second user) in the setting unit, and a selection object T34 (second selection object) for selecting whether or not to set the handover candidate data (shared data) to be available for acquisition by the handover user (second user). The setting unit 160 sets the handover confirmation data (shared data) corresponding to the selection object T34 (second selection object) selected by the handover user (second user) to be available for acquisition by the handover user (second user). As a result, the handover user can easily select the desired data from the handover candidate data, thereby improving user convenience.

[0081] Furthermore, in the handover system 10 of this embodiment, the display processing unit 130 displays the acquisition selection screen T30 on the handover terminal 300 (terminal device) of the handover person (second user) when the date of departure from the company to which the departing employee (first user) belongs has passed. This improves user convenience because it allows the handover candidate data to be checked after the departing employee has left the company, without any changes being made to the departure data by the departing employee.

[0082] Furthermore, in this embodiment, the handover system 10, when there is shared setting data among the employee data (user data) that is set to be obtainable by a user other than the employee (first user), displays an authorization selection screen T40 (second authorization selection screen) on the employee terminal 200 (terminal device) of the employee (first user) that associates a selection object T44 (third selection object) for selecting whether or not the shared setting data (data) is personal data that can only be obtained by the employee (first user). Based on the employee's (first user's) operation input to the selection object T44 (third selection object), the authorization selection screen T50 (first authorization selection screen) is displayed on the employee terminal 200 (terminal device) of the employee (first user) that sets the selection object T14 (first selection object) corresponding to the data selected as personal data among the data shown in the configuration information to be unselectable. This allows the handover system 10 to prevent omissions in setting personal data for former employees, thereby improving user convenience.

[0083] Furthermore, in this embodiment, the handover system 10, when all of the selectable selection objects T44 (third selection objects) are selected, displays an authorization selection screen T50 (first authorization selection screen) on the departing employee's (first user's) terminal 200 (terminal device). This screen displays an authorization selection screen T50 (first authorization selection screen) on the departing employee's (first user's) terminal device, where the selection object T14 (first selection object) corresponding to the data selected as personal data from the data shown in the configuration information is set to unselectable. This prevents the departing employee from forgetting to perform the operation to set the departing employee's data as personal data, thereby improving user convenience.

[0084] Furthermore, in this embodiment, the handover system 10, with its display processing unit 130, associates an unconfirmed mark T152, which indicates that the departing employee (first user) has not performed any operation input on the selected object T14 (first selected object) on the authorization selection screen T10 (first authorization selection screen), with objects for which the departing employee (first user) has not received any operation input, and displays this mark on the departing employee's terminal 200 (terminal device). This allows the departing employee to easily confirm whether they have selected personal data or handover candidate data for each piece of departing employee data, thereby improving user convenience.

[0085] Furthermore, in the handover system 10 of this embodiment, the cloud server 400 (server) is a cloud server of a different company than the company to which the departing employee (first user) belongs. As a result, in a situation where the cloud server's storage is allocated to individuals, the handover system 10 can make the user's data available to other users based on the user's input before the user's account for accessing the server is deleted. [Explanation of Symbols]

[0086] 10...Handover system, 100...Handover server, 200...Departing employee's terminal, 300...Handover employee's terminal, 400...Cloud server.

Claims

1. an acquisition unit that acquires configuration information indicating at least a configuration of user data, which is data of the first user stored in the server and associated with account information of the first user for accessing the server; a display processing unit that displays, on the terminal device of the first user, a first authority selection screen in which a first selection object, which the first user uses to select whether to set the data as personal data that is data that can only be acquired by the first user, or as shared data that is data that can be acquired by the first user as well as users other than the first user, is associated with data indicated in the configuration information; and a request unit that requests the shared data from the server in response to an operation input by the first user with respect to the first selected object; An information processing system comprising:

2. the display processing unit displays, on the terminal device of the first user, a first input screen that is a screen for accepting input of identification information that identifies a second user who is set to be able to acquire the shared data; a setting unit that sets the shared data to be obtainable by the second user in response to an operation input by the first user on the first input screen, The information processing system according to claim 1 .

3. the display processing unit displays, on the terminal device of the second user, an acquisition selection screen that includes a list showing the shared data set by the setting unit to be acquireable for the second user, and a second selection object for selecting whether to set the shared data to be acquireable for the second user; the setting unit sets the shared data corresponding to the second selection object selected by the operation input of the second user to be obtainable by the second user. The information processing system according to claim 2 .

4. the display processing unit displays the acquisition selection screen on the terminal device of the second user when a separation date on which the first user will leave the company to which the first user belongs has passed. The information processing system according to claim 3 .

5. The display processing unit When there is shared setting data among the user data, which is data that is set to be obtainable by a user other than the first user, a second authority selection screen is displayed on the terminal device of the first user, in which a third selection object is associated with the shared setting data to select whether the shared setting data is the personal data that can be obtained only by the first user; displaying, on the terminal device of the first user, the first authority selection screen, in which the first selection object corresponding to the data selected as the personal data from among the data indicated in the configuration information is set to be unselectable, based on the operation input by the first user with respect to the third selection object; The information processing system according to any one of claims 1 to 4.

6. the display processing unit, when all of the selectably displayed third selection objects are selected, displays the first authority selection screen on the terminal device of the first user, in which the first selection objects corresponding to the data selected as the personal data from among the data indicated in the configuration information are set to be unselectable. The information processing system according to claim 5 .

7. the display processing unit associates an unconfirmed mark, which is a mark indicating that the first user has not performed an operation input on the first selection object, with an object among the first selection objects on the first authority selection screen that has not received an operation input from the first user, and displays the unconfirmed mark on the terminal device of the first user. The information processing system according to any one of claims 1 to 6.

8. the server is a cloud server of a business operator different from the business operator to which the first user belongs; The information processing system according to any one of claims 1 to 7.

9. The computer acquiring configuration information indicating at least a configuration of user data, which is data of the first user stored in the server and associated with account information of the first user for accessing the server; displaying, on the terminal device of the first user, a first authority selection screen in which a first selection object for the first user to select whether to set the data as personal data that is data that can only be acquired by the first user, or as shared data that is data that can be acquired by the first user as well as users other than the first user, is associated with data indicated in the configuration information; requesting the shared data from the server in response to an operation input by the first user with respect to the first selected object; An information processing method that performs the above.

10. On the computer, acquiring configuration information indicating at least a configuration of user data, which is data of the first user stored in the server and associated with account information of the first user for accessing the server; displaying, on the terminal device of the first user, a first authority selection screen in which a first selection object for the first user to select whether to set the data as personal data that is data that can only be acquired by the first user, or as shared data that is data that can be acquired by the first user as well as users other than the first user, is associated with data indicated in the configuration information; requesting the shared data from the server in response to an operation input by the first user with respect to the first selected object; A program that executes the following.

Images