JP7797865B2 - Information processing system, information processing method, and program - Google Patents

Description

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

By dividing each organization into units called tenants and entering into contracts on a tenant-by-tenant basis to purchase applications for business purposes, etc., applications can be customized to suit each organization's budget and situation. It is also known that when using an application on a certain device, it is linked to that tenant.

However, when a device is already associated with a tenant in one department and is now being used, and another department on the same floor also wants to use it, switching between the two tenants is inefficient, so there are cases where users want to be invited to the tenant already associated with it. Furthermore, tenants are created as a concept that groups users together when providing services, allowing for different contracts, settings, and operations at the corporate or organizational level. Therefore, when a user belonging to a specific tenant receives an invitation from another tenant, the inviting tenant must also invite the user, so a separate request for a tenant invitation must be made to the administrator.

The present invention has been made in consideration of the above, and aims to provide an information processing system, information processing method, and program that allows a user belonging to a different tenant to use another tenant's equipment while minimizing the tenant administrator's efforts when the user requests use of the equipment from the tenant administrator.

In order to solve the above-mentioned problems and achieve the object, the present invention provides a storage unit that stores user information associated with tenant information defining tenants for dividing a service provision range, the user information being used to identify users belonging to the tenant indicated by the tenant information, and device information being used to identify devices belonging to the tenant indicated by the tenant information; and a device information storage unit that stores information that identifies devices belonging to the tenant indicated by the tenant information, the device information being used to identify users belonging to the tenant indicated by the tenant information, the device information being used to identify devices ... The device is provided with a control unit that displays information on the application for use device, and prompts a terminal device of a tenant administrator of the tenant indicated by the tenant information linked to the device information of the application for use device to invite the user who has logged in, and when the tenant administrator performs an operation on the terminal device to invite the user who has logged in to the application for use device, approves the invited user's use of the application for use device, and sends an email to the application for use device indicating the approval result of the invited user's use of the application for use device, depending on whether the tenant administrator's terminal device accepts or rejects the user's invitation .

This invention has the advantage that when a user belonging to a different tenant submits a usage request to a tenant administrator, the user can use the equipment of another tenant while minimizing the work required by the tenant administrator.

FIG. 1 is a diagram for explaining an example of a process for inviting a user to a new tenant in an information processing system according to the present embodiment. FIG. 2 is a diagram showing an example of a network layout of the information processing system according to the present embodiment. FIG. 3 is a hardware configuration diagram of the workflow service (server) and PC included in the information processing system according to this embodiment. FIG. 4 is a diagram showing the hardware configuration of the MFP according to this embodiment. FIG. 5 is a block diagram showing an example of the functional configuration of the workflow service of the information processing system according to this embodiment. FIG. 6 is a flowchart showing an example of the flow of processing executed when a login operation is performed on an MFP in the information processing system according to this embodiment. FIG. 7 is a diagram showing an example of an application use screen displayed on the MFP in the information processing system according to the present embodiment. FIG. 8 is a flowchart showing an example of the flow of processing executed when a tenant administrator operates the usage application management screen in the information processing system according to this embodiment. FIG. 9 is a diagram showing an example of an invitation acceptance screen displayed on the PC of the tenant administrator in the information processing system according to this embodiment.

Embodiments of the information processing system, information processing method, and program are described in detail below with reference to the accompanying drawings.

Figure 1 is a diagram illustrating an example of the process of inviting a user to a new tenant in an information processing system according to this embodiment. Specifically, Figure 1 conceptually illustrates the flow of operations when a user of Tenant A wishes to operate on an MFP (Multi-Function Peripheral) 9 belonging to Tenant B, submitting a request to the administrator of Tenant B (tenant administrator) via the MFP 9, and the user of Tenant A operating the MFP 9. Here, Tenants A and B represent the boundaries of the service provision ranges (hereinafter referred to as service provision ranges).

First, when a user of Tenant A performs an invitation request operation on a screen of an MFP 9 belonging to Tenant B (step S1), the MFP 9 identifies the tenant administrator of Tenant B and sends an approval request email to the identified tenant administrator M (step S2).

Next, upon receiving the approval request email, the tenant administrator of Tenant B approves the operation of Tenant A's MFP 9 by the user of Tenant A and notifies the user of Tenant A of approval (step S3). The user of Tenant A is then invited to Tenant B (step S4) and becomes able to use the MFP 9 belonging to Tenant B (step S5).

Figure 2 is a diagram showing an example of the network layout of an information processing system according to this embodiment. As shown in Figure 2, the information processing system according to this embodiment includes a PC (Personal Computer) 5, which is an example of a tenant administrator's terminal device, a workflow service 300, and an MFP 9, which is an example of a device. In this embodiment, the workflow service 300 is deployed on the cloud. The tenant administrator's PC 5 and MFP 9 are directly operated by the user.

Figure 3 is a hardware configuration diagram of the workflow service (server) and PC of the information processing system according to this embodiment. Here, the hardware configuration of PC 5 is described, but the workflow service 300 also has a similar hardware configuration.

As shown in Figure 3, PC 5 is constructed by a computer and includes a CPU (Central Processing Unit) 501, ROM (Read Only Memory) 502, RAM (Random Access Memory) 503, HD (Hard Disk) 504, HDD (Hard Disk Drive) controller 505, display 506, external device connection I/F (Interface) 508, network I/F 509, data bus 510, keyboard 511, pointing device 512, DVD-RW (Digital Versatile Disk Rewritable) drive 514, and media I/F 516.

Of these, the CPU 501 controls the overall operation of the PC 5. The ROM 502 stores programs used to drive the CPU 501, such as IPL. The RAM 503 is used as a work area for the CPU 501. The HDD 504 stores various data, such as programs. The HDD controller 505 controls the reading and writing of various data from the HDD 504 under the control of the CPU 501. The display 506 displays various information, such as a cursor, menus, windows, text, or images. The external device connection I/F 508 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. The network I/F 509 is an interface for data communication using the communication network 100. The data bus 510 is an address bus, data bus, etc. for electrically connecting the various components, such as the CPU 501, shown in FIG. 5.

The keyboard 511 is a type of input device equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input device for selecting and executing various instructions, selecting a processing target, moving the cursor, etc. The DVD-RW drive 514 controls the reading and writing of various data from a DVD-RW 513, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R or the like. The media I/F 516 controls the reading and writing (storing) of data from a recording medium 515, such as a flash memory.

Figure 4 is a hardware configuration diagram of an MFP according to this embodiment. As shown in Figure 4, the MFP (Multi-function Peripheral/Product/Printer) 9 includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network I/F 950.

Of these, the controller 910 includes the CPU 901, which is the main part of the computer, system memory (MEM-P) 902, north bridge (NB) 903, south bridge (SB) 904, ASIC (Application Specific Integrated Circuit) 906, local memory (MEM-C) 907, which is a storage unit, HDD controller 908, and HD 909, which is also a storage unit, with the NB 903 and ASIC 906 connected via an AGP (Accelerated Graphics Port) bus 921.

Of these, the CPU 901 is a control unit that performs overall control of the MFP 9. The NB 903 is a bridge that connects the CPU 901 with the MEM-P 902, SB 904, and AGP bus 921, and includes a memory controller that controls reading and writing to the MEM-P 902, a PCI (Peripheral Component Interconnect) master, and an AGP target.

MEM-P902 has ROM902a, which is memory for storing programs and data that realize the various functions of controller 910, and RAM902b, which is used for expanding programs and data and as drawing memory during memory printing. The programs stored in RAM902b may also be provided by being recorded in installable or executable format on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

SB904 is a bridge connecting NB903 with PCI devices and peripheral devices. ASIC906 is an integrated circuit (IC) for image processing applications that contains hardware elements for image processing and acts as a bridge connecting AGP bus 921, PCI bus 922, HDD 908, and MEM-C 907. This ASIC 906 contains a PCI target and AGP master, an arbiter (ARB) that forms the core of ASIC 906, a memory controller that controls MEM-C 907, multiple DMACs (Direct Memory Access Controllers) that perform image data rotation using hardware logic, and a PCI unit that transfers data between scanner unit 931 and printer unit 932 via PCI bus 922. A USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface may also be connected to the ASIC 906.

MEM-C907 is local memory used as a copy image buffer and code buffer. HD909 is storage for storing image data, font data used during printing, and forms. HD909 controls the reading and writing of data from and to HD909 under the control of CPU901. AGP bus921 is a bus interface for a graphics accelerator card proposed to speed up graphics processing; direct high-throughput access to MEM-P902 enables the graphics accelerator card to operate at high speed.

The short-range communication circuit 920 also includes a short-range communication circuit 920a. The short-range communication circuit 920 is a communication circuit such as NFC or Bluetooth (registered trademark).

The engine control unit 930 is further made up of a scanner unit 931 and a printer unit 932. The operation panel 940 is equipped with a panel display unit 940a, such as a touch panel, that displays current settings and selection screens and accepts input from the operator, and an operation panel 940b that has a numeric keypad that accepts settings for image formation conditions such as density settings and a start key that accepts a copy start command. The controller 910 controls the entire MFP 9, and controls, for example, drawing, communication, and input from the operation panel 940. The scanner unit 931 or printer unit 932 includes image processing units such as error diffusion and gamma conversion.

The MFP 9 allows users to sequentially switch between the document box function, copy function, printer function, and facsimile function using the application switching key on the operation panel 940. When the document box function is selected, the device enters document box mode; when the copy function is selected, the device enters copy mode; when the printer function is selected, the device enters printer mode; and when the facsimile mode is selected, the device enters facsimile mode.

The network I/F 950 is an interface for data communication using the communication network 100. The short-range communication circuit 920 and the network I/F 950 are electrically connected to the ASIC 906 via the PCI bus 922.

Figure 5 is a block diagram showing an example of the functional configuration of a workflow service of an information processing system according to this embodiment. In this embodiment, the system includes a control unit 525 and a storage unit 526.

The memory unit 526 is an example of a memory unit that stores, linked to tenant information that defines tenants for dividing the service provision area, user information used to identify users who belong to the tenant indicated by the tenant information, and device information used to identify MFP9 (an example of a device) that belongs to the tenant indicated by the tenant information.

In this embodiment, the memory unit 526 stores a tenant table 521, a user table 522, an MFP table 523, and a usage application table 524.

The tenant table 521 associates tenant IDs with tenant names as shown in Table 1 below. Here, the tenant ID is identification information of a tenant. The tenant name is the name of a tenant. The tenant ID and the tenant name are examples of tenant information.

As shown in Table 2 below, the user table 522 associates a user ID, a tenant ID, a user name, an email address, a password, and a role. Here, the user ID is identification information of the user. The tenant ID is the tenant ID of the tenant to which the user belongs. The user name is the name of the user. The email address is the email address of the user. The password is the password used by the user to log in when using the MFP 9. The role represents the user's job title (e.g., tenant administrator). The tenant to which the user belongs is determined by the tenant ID. The tenant ID is linked to the tenant ID column in the tenant table 521. The user ID, user name, email address, role, etc. are examples of user information.

The MFP table 523 associates an MFP ID, a tenant ID, a machine number, and a name, as shown in Table 3 below. Here, the MFP ID is identification information of the MFP 9. The tenant ID is the tenant ID of the tenant to which the MFP 9 belongs. The machine number is the model number of the MFP 9. The name is the name of the MFP 9. The tenant to which the MFP 9 belongs is determined by the tenant ID. The tenant ID is linked to the tenant ID column in the tenant table 521. The MFP ID, machine number, name, etc. are examples of device information.

The usage application table 524 is an example of a data table that indicates the status of a user's application to use the MFP 9 (hereinafter referred to as the usage application status). In this embodiment, the usage application table 524 associates a usage application ID, a source user ID, a destination tenant ID, a destination guest user ID, and a usage application status, as shown in Table 4 below. Here, the usage application ID is identification information for the user's application to use the MFP 9. The source user ID is the user ID of the user who made the application to use the MFP 9. The user who made the application to use the MFP 9 is assumed to have logged in from the MFP 9, so the user is identified by the user ID at the time of login (source user ID).

The destination tenant ID is the tenant ID of the tenant to which the MFP 9 for which usage has been requested belongs. Specifically, the destination tenant ID is the tenant ID of the tenant to which the MFP 9 operated by the user who has requested usage of the MFP 9 belongs. The destination guest user ID is user identification information assigned to the user who has requested usage. The usage application status is the status of the usage application for the MFP 9 (for example, requesting, approved, or rejected). The usage application status is initially requesting, and the status can be changed to either approved or rejected by the tenant administrator's operation. The destination guest user will be described later.

For example, when the tenant administrator approves a user's application to use the MFP 9, the workflow service 300 stores the user ID (source user ID: 3) of the user whose application has been approved in the user table 522, as shown in Table 5 below. At that time, the workflow service 300 changes the application status of the application associated with the source user ID added to the user table 522 in the application application table 524 from "application pending" to "approved," as shown in Table 5 below.

Also, for example, if the tenant administrator approves a user's application to use MFP 9, the workflow service 300 adds user A-2 as a guest to the role associated with the user ID of the user whose application for use has been approved (for example, the user ID of user A-2 added to the tenant) in the user table 522, as shown in Table 6 below. Furthermore, the workflow service 300 obtains the user name, email address, and password of user A-2 from the user table 522 based on the source user ID of the application for use, and stores them in association with user ID: 7, as shown in Table 6 below.

Also, for example, if the tenant administrator M rejects a user's application to use the MFP 9, the workflow service 300 changes the application status associated with the source user ID in the application table 524 from "application pending" to "rejected," as shown in Table 7 below.

When a user indicated by user information linked to tenant information other than the tenant information linked to the device information of the requested device, which is the MFP 9 for which the request for use has been made, logs in to the requested device, the control unit 525 displays on the requested device (for example, the operation panel 940 of the requested device) that the requested device cannot be used. Furthermore, the control unit 525 prompts the PC 5 of the tenant administrator of the tenant indicated by the tenant information linked to the device information of the requested device to invite the user who logged in.

As a result, if the MFP 9 and the logged-in user belong to different tenants, a screen on the MFP 9 where a usage request can be made is displayed, the usage request is notified to the tenant administrator of the tenant to which the MFP 9 belongs, and permission to use the MFP 9 is granted to the user of the other tenant, allowing the user and tenant administrator to permit or deny use of the MFP 9 by the other tenant with a simple operation. As a result, if a user from a different tenant makes a usage request to the tenant administrator, the device of the other tenant can be used with minimal effort on the part of the tenant administrator.

In this embodiment, the control unit 525 identifies all tenant administrators of the tenant indicated in the tenant information linked to the device information of the device for which use has been requested, and prompts the PCs 5 of all identified tenant administrators to invite the user who has logged in. For example, the control unit 525 may send an email to the PCs 5 of the tenant administrators of the tenant indicated in the tenant information linked to the device information of the device for which use has been requested, prompting them to invite the user who has logged in.

When the tenant administrator performs an operation on PC 5 to invite a user who has logged in to MFP 9, the control unit 525 approves the invited user's use of the device that has been requested for use. The control unit 525 also sends an email to the device that has been requested for use indicating the approval result for the invited user's use of the device, depending on whether the tenant administrator's PC 5 approved or rejected the user's invitation.

Figure 6 is a flowchart showing an example of the flow of processing executed when a user logs in to an MFP in the information processing system according to this embodiment. When a user operates the MFP 9 to request access to the workflow service 300, the control unit 525 of the workflow service 300 displays a login screen on the operation panel 940 of the MFP 9 (step S601). Here, the login screen is a screen on which the user performing the login operation can enter the user ID, email address, password, model number of the MFP 9, etc.

Next, when the user performs a login operation on the login screen displayed on the operation panel 940 of the MFP 9 (step S602), the MFP 9 transmits the model number of the MFP 9, the user ID, email address, password, etc. of the user who performed the login operation to the workflow service 300. In this embodiment, the MFP 9 transmits the model number entered on the login screen to the workflow service 300, but it may also automatically transmit the model number of the MFP 9 itself to the workflow service.

The control unit 525 of the workflow service 300 receives from the MFP 9 the model number of the MFP 9, the email address and password of the user who performed the login operation, etc. (step S603). The control unit 525 then performs authentication processing for the user who performed the login operation using the user ID who performed the login operation and the received password, etc. (step S604).

If user authentication fails (step S604: No), the control unit 525 displays a login screen containing a message indicating that user authentication failed on the operation panel 940 of the MFP 9 (step S605). On the other hand, if user authentication is successful (step S604: Yes), the control unit 525 determines whether the tenant to which the MFP 9 belongs is different from the tenant to which the logged-in user belongs, or whether the logged-in user does not have permission to use the MFP 9 (step S606).

If the tenant to which the MFP 9 belongs is the same as the tenant to which the logged-in user belongs, or if the logged-in user has permission to use the MFP 9 (step S606: No), the control unit 525 displays an app usage screen on the operation panel 940 of the MFP 9 that allows the MFP 9 to be used (step S607).

On the other hand, if the tenant to which the MFP 9 belongs is different from the tenant to which the logged-in user belongs, or if the logged-in user does not have permission to use the MFP 9 (step S606: Yes), the control unit 525 displays a usage request screen on the operation panel 940 of the MFP 9, which allows the user to request to use the MFP 9 (step S608). This causes the control unit 525 to display on the MFP 9 that the requested device cannot be used.

Figure 7 is a diagram showing an example of an application usage screen displayed on an MFP in an information processing system according to this embodiment. In this embodiment, the control unit 525 displays, on the operation panel 940 of the MFP 9, a usage request screen including a button B1 for instructing the user to apply to use the MFP 9 and a button B2 for instructing the user not to apply to use the MFP 9, as shown in Figure 7.

Returning to FIG. 6, when the user subsequently applies to use the MFP 9 on the usage application screen displayed on the operation panel 940 of the MFP 9 (step S609), the control unit 525 creates usage application data (step S610). Next, the control unit 525 sends the created usage application data to the PC 5 of the tenant administrator of the tenant to which the MFP 9 belongs (step S611).

Figure 8 is a flowchart showing an example of the flow of processing executed when a tenant administrator operates the usage application management screen in the information processing system according to this embodiment. When the tenant administrator's PC 5 receives usage application data from the workflow service 300, it displays on the display 506 an invitation approval screen on which the logged-in user can input whether or not to approve the usage application (step S801).

Figure 9 is a diagram showing an example of an invitation approval screen displayed on the tenant administrator's PC in the information processing system according to this embodiment. In this embodiment, the tenant administrator's PC 200 displays on the display 506, as shown in Figure 9, an invitation approval screen including a button B3 for instructing the user to approve the login user's use request and a button B4 for instructing the user to reject the login user's use request.

Returning to FIG. 8, the tenant administrator then inputs on the usage application screen whether or not to permit the login user's usage application. If the login user's usage application is permitted on the usage application screen (step S802: Yes), the tenant administrator's PC 5 creates a guest user ID and sends the created guest user ID to the workflow service 300 (step S803).

Next, the control unit 525 of the workflow service 300 changes the usage application status associated with the source user ID (user ID of the logged-in user) in the usage application table 524 to permitted (step S804). That is, when the tenant administrator performs an operation on PC 5 to invite the user who has logged in to the usage application device, the control unit 525 approves the invited user's use of the usage application device. Furthermore, the control unit 525 sends an email to the MFP 9 that the guest user (logged-in user) has logged in to, indicating that use of the MFP 9 has been permitted (step S805). That is, the control unit 525 sends an email to the usage application device indicating that the invitation of the user on the tenant administrator's PC 5 has been permitted.

On the other hand, if a denial of the login user's use application is input on the use application screen (step S802: No), the tenant administrator's PC 5 notifies the workflow service 300 that the use application for the MFP 9 has been denied. Upon receiving the notification that the use application for the MFP 9 has been denied, the control unit 525 of the workflow service 300 changes the use application status associated with the source user ID in the use application table 524 to "rejected" (step S806). Furthermore, the control unit 525 sends an email to the MFP 9 into which the login user (source user) logged in, indicating that use of the MFP 9 has been denied (step S807). In other words, the control unit 525 sends an email to the use application device indicating that the user's invitation on the tenant administrator's PC 5 has been rejected.

As such, according to the information processing system of this embodiment, when the MFP 9 and the logged-in user belong to different tenants, a screen on the MFP 9 on which a usage request can be made is displayed, the usage request is notified to the tenant administrator of the tenant to which the MFP 9 belongs, and permission to use the MFP 9 is granted to the user of the other tenant. This allows the user and tenant administrator to permit or deny use of the MFP 9 by the other tenant with a simple operation. As a result, when a user belonging to a different tenant makes a usage request to the tenant administrator, the device of the other tenant can be used with minimal effort on the part of the tenant administrator.

The functions of the embodiments described above can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes processors programmed to perform each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and conventional circuit modules designed to perform each of the functions described above.

The devices described in the example are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, workflow service 300 includes multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a network, shared memory, etc., and perform the processes disclosed herein. Similarly, PC 5 may include multiple computing devices configured to communicate with each other.

Furthermore, the workflow service 300 and PC 5 can be configured to share the disclosed processing steps, e.g., FIG. 5, in various combinations. For example, the processes performed by the workflow service 300 can be performed by PC 5. Similarly, the functions of PC 5 can be performed by the workflow service 300. Furthermore, the elements of the workflow service 300 and PC 5 can be integrated into a single server device or separated into multiple devices.

Note that devices such as the MFP 9 are not limited to image forming devices, as long as they have communication capabilities. Devices may also be, for example, output devices such as PJs (Projectors), IWBs (Interactive Whiteboards: electronic whiteboards with intercommunication capabilities), digital signage, HUDs (Head Up Display) devices, industrial machinery, imaging devices, sound collection devices, medical equipment, network appliances, automobiles (Connected Cars), notebook PCs (Personal Computers), mobile phones, smartphones, tablet devices, game consoles, PDAs (Personal Digital Assistants), digital cameras, wearable PCs, or desktop PCs.

The program executed by the workflow service 300 of this embodiment is provided in advance in a ROM 502 or the like. The program executed by the workflow service 300 of this embodiment may also be provided by being recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk).

Furthermore, the program executed by the workflow service 300 of this embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Furthermore, the program executed by the workflow service 300 of this embodiment may be provided or distributed via a network such as the Internet.

The program executed by the workflow service 300 of this embodiment has a modular configuration including the above-mentioned units (control unit 525), and in terms of actual hardware, the CPU 501 (an example of a processor) reads and executes the program from the above-mentioned ROM 502, thereby loading the above-mentioned units into the main memory device and generating the control unit 525 on the main memory device.

5 PCs
9. MFP
300 Workflow service 501 CPU
502 ROM
503 RAM
940 Operation panel 521 Tenant table 522 User table 523 MFP table 524 Usage application table 525 Control unit 526 Storage unit

Japanese Patent Application Laid-Open No. 2019-036141

Claims (5)

a storage unit that stores user information used to identify users belonging to the tenant indicated by the tenant information, the user information being associated with tenant information defining tenants for dividing a service provision range, and device information being used to identify devices belonging to the tenant indicated by the tenant information;
a control unit that, when a user indicated by the user information linked to tenant information other than the tenant information linked to the device information of the application-for-use device, which is the device for which a usage application has been made, performs a login operation to the application-for-use device, displays on the application-for-use device that the application-for-use device cannot be used, and prompts a terminal device of a tenant administrator of the tenant indicated by the tenant information linked to the device information of the application-for-use device to invite the user who performed the login operation, and when the tenant administrator performs an operation on the terminal device to invite the user who performed the login operation to the application-for-use device, approves the invited user's use of the application-for-use device, and sends to the application-for-use device an email indicating the approval result of the invited user's use of the application-for-use device in accordance with the acceptance or rejection of the user invitation on the terminal device of the tenant administrator ;
An information processing system comprising: The information processing system of claim 1, wherein the control unit identifies all tenant administrators of the tenant indicated by the tenant information linked to the device information of the device requested for use, and prompts the terminal devices of all identified tenant administrators to invite the user who logged in to the device requested for use. The information processing system according to claim 1 or 2, wherein the control unit sends an email to the terminal device of the tenant administrator of the tenant indicated by the tenant information linked to the device information of the device that has applied for use, prompting the user who has performed the login operation to invite the user. An information processing method executed in an information processing system having a storage unit that stores user information used to identify users belonging to the tenant indicated by the tenant information, the user information being linked to tenant information that defines tenants for dividing a service provision range, and device information being used to identify devices belonging to the tenant indicated by the tenant information, the method comprising:
a step of displaying on the application-for-use device that the application-for-use device cannot be used when a user indicated by the user information linked to tenant information other than the tenant information linked to the device information of the application-for-use device, which is the device for which a usage application has been made, performs a login operation to the application-for-use device;
a step of prompting a terminal device of a tenant administrator of the tenant indicated by the tenant information linked to the device information of the usage application device to invite the user who has performed a login operation, and when the tenant administrator performs an operation on the terminal device to invite the user who has performed a login operation to the usage application device, approving the invited user's use of the usage application device by the usage application device, and sending an email to the usage application device indicating the approval result of the invited user's use of the usage application device in accordance with whether the user's invitation on the terminal device of the tenant administrator has been accepted or rejected ;
An information processing method including: Computer,
a control unit configured to: when a user indicated by the user information associated with tenant information other than the tenant information associated with the device information of a usage-application device for which a usage application has been made logs in to the usage-application device, the control unit displays on the usage-application device a message indicating that the usage-application device cannot be used; and when the tenant administrator performs an operation on the terminal device to invite the user who has logged in to the usage-application device, the control unit approves the invited user's use of the usage-application device, and when the tenant administrator performs an operation on the terminal device to invite the user who has logged in to the usage-application device, the control unit sends an email to the usage-application device indicating the approval result of the invited user's use of the usage-application device, in accordance with whether the user's invitation on the terminal device of the tenant administrator has been approved ;
A program to function as a