Platform and program for platform

Abstract

To provide a platform and a program for the platform that can improve convenience.SOLUTION: A platform 20 is a foundation for executing a printing and scanning system 30 as a web application for enabling printing and scanning using an image forming apparatus 80, a document management system 40 as a web application for managing documents, and a document processing system 50 as a web application for executing specific processing on an input document and outputting the document to a specific destination. The platform 20 comprises an application use unit 25a that allows a user who has logged into the platform 20 to use the print scan system 30, the document management system 40, and the document processing system 50.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a platform that is the basis for the execution of multiple web applications and a program for the platform. [Background technology]

[0002] BACKGROUND ART Conventionally, web applications that are used by logged-in users are known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-038805 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, when a user uses multiple web applications, the user must log in to each of the multiple web applications, which is inconvenient.

[0005] Therefore, an object of the present invention is to provide a platform and a program for the platform that can improve convenience. [Means for solving the problem]

[0006] The platform of the present invention is a platform that is the basis for the execution of multiple web applications, and is characterized by having an application utilization unit that allows a user logged in to the platform to utilize the multiple web applications.

[0007] With this configuration, the platform of the present invention is equipped with an application utilization unit that allows a user logged in to the platform to utilize multiple web applications, so that when a user utilizes multiple web applications, the user does not need to log in to each of the multiple web applications, thereby improving convenience.

[0008] In the platform of the present invention, the application using unit may generate a web page that can execute settings related to the web application.

[0009] With this configuration, the platform of the present invention generates a web page that allows settings related to the web application to be executed, thereby improving convenience.

[0010] In the platform of the present invention, the application usage unit includes a specific area on the web page for executing the settings related to a specific function if any of the web applications under contract with the organization to which the user who is logged in to the platform belongs supports the specific function, and does not need to include the specific area on the web page if none of the web applications under contract with the organization supports the specific function.

[0011] With this configuration, the platform of the present invention includes a specific area on the web page for performing settings related to a specific function if any of the web applications under contract with the organization to which the user who is logged in to the platform belongs supports the specific function, and does not include the specific area on the web page if none of the under contract web applications supports the specific function.This increases the likelihood that the user will perform settings that need to be performed, while reducing the likelihood that the user will perform settings that do not need to be performed, thereby improving convenience.

[0012] In the platform of the present invention, the specific area may display whether the setting has been performed or not.

[0013] With this configuration, the platform of the present invention has a specific area that displays whether or not a setting has been performed, making it easier for users to recognize settings that have not been performed and improving convenience.

[0014] In the platform of the present invention, the web page may be capable of executing the setting common to a plurality of the web applications.

[0015] With this configuration, the platform of the present invention generates a web page that can execute settings common to multiple web applications, thereby eliminating the need to execute similar settings for each of the multiple web applications, thereby improving convenience.

[0016] The platform program of the present invention is a platform program for realizing on a computer a platform that is the basis for executing multiple web applications, and is characterized in that the platform has an application utilization unit that allows users logged in to the platform to utilize multiple of the web applications.

[0017] With this configuration, the computer that executes the platform program of the present invention is equipped with an application utilization unit that allows a user logged in to the platform to use multiple web applications, so that when a user uses multiple web applications, the user does not need to log in to each of the multiple web applications, thereby improving convenience. [Effects of the Invention]

[0018] The platform and the program for the platform of the present invention can improve convenience. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a block diagram of a system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram of the platform shown in FIG. 1 when configured with one PC. [Figure 3] FIG. 3 is a diagram illustrating an example of an application management table illustrated in FIG. 2. [Figure 4] FIG. 3 is a diagram showing an example of an organization management table shown in FIG. [Figure 5] FIG. 3 is a diagram illustrating an example of a user management table illustrated in FIG. 2. [Figure 6] FIG. 3 is a diagram showing an example of a group management table shown in FIG. 2. [Figure 7] FIG. 3 is a diagram showing an example of a device management table shown in FIG. 2. [Figure 8] FIG. 3 is a diagram showing an example of a PIN management table shown in FIG. 2. [Figure 9] 3 is a diagram showing an example of an ID card management table shown in FIG. 2. FIG. [Figure 10] FIG. 3 is a diagram showing an example of a first storage management table shown in FIG. 2. [Figure 11] FIG. 2 is a block diagram of the computer shown in FIG. 1 when configured as a PC. [Figure 12] FIG. 2 is a block diagram of the image forming apparatus shown in FIG. 1 when configured as an MFP. [Figure 13] 3 is a flowchart of the operation of the platform shown in FIG. 2 when logged in by a user. [Figure 14] FIG. 14 is a diagram showing an example of a top screen for an administrative user displayed by the operation shown in FIG. 13. [Figure 15] 3 is a flowchart of the operation of the platform shown in FIG. 2 when the subscription contract period expires. [Figure 16]15 is a flowchart of the operation of the platform when the user setting operation unit shown in FIG. 14 is pressed. [Figure 17] 15 is a flowchart of the operation of the platform when the storage setting operation unit shown in FIG. 14 is pressed. [Figure 18] FIG. 14 is a diagram showing an example of a top screen for general users that is displayed by the operation shown in FIG. 13. [Figure 19] 19 is a flowchart of the operation of the platform when the PIN authentication setting operation unit shown in FIG. 18 is pressed. [Figure 20] FIG. 20 is a diagram showing an example of a login user PIN authentication setting area displayed by the operation shown in FIG. 19. [Figure 21] 19 is a diagram showing an example of a login user ID card authentication setting area displayed by the operation of the application use unit when the ID card authentication setting operation unit shown in FIG. 18 is pressed. FIG. [Figure 22] 19 is a flowchart of the operation of the platform when the storage setting operation unit shown in FIG. 18 is pressed. [Figure 23] 23 is a diagram showing an example of a first storage setting area for a logged-in user and a second storage setting area for a logged-in user displayed by the operation shown in FIG. 22. FIG. [Figure 24] 15 is a diagram showing an example of the top screen for an administrative user shown in FIG. 14 in a state in which the device setting operation unit and the ID card authentication setting operation unit are inoperable. FIG. [Figure 25] 15 is a diagram showing an example of the top screen for an administrative user shown in FIG. 14 in a state in which the device setting operation section and the ID card authentication setting operation section are not displayed. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0020] An embodiment of the present invention will now be described with reference to the drawings.

[0021] First, the configuration of the system according to this embodiment will be described.

[0022] FIG. 1 is a block diagram of a system 10 according to the present embodiment.

[0023] 1, the system 10 includes a platform 20 that is the foundation for executing multiple web applications. The platform 20 may be configured with a single computer such as a PC (Personal Computer), or may be configured with multiple computers.

[0024] System 10 includes multiple web applications that run on platform 20. For example, system 10 includes, as web applications that run on platform 20, a print scan system 30 that is a web application that enables printing and scanning using an image forming apparatus described below, a document management system 40 that is a web application that manages documents, and a document processing system 50 that is a web application that performs specific processing on input documents and outputs them to specific destinations. Each of print scan system 30, document management system 40, and document processing system 50 may be configured by a single computer such as a PC, or may be configured by multiple computers.

[0025] At least a portion of at least two of the platform 20, the print scan system 30, the document management system 40, and the document processing system 50 may be configured by the same computer. The platform 20, the print scan system 30, the document management system 40, and the document processing system 50 may be run on a cloud, such as Google (registered trademark) Cloud.

[0026] The system 10 includes a computer 70 for using each of the print scan system 30, the document management system 40, and the document processing system 50 via the platform 20. The system 10 may include a computer other than the computer 70 that has a similar configuration to the computer 70. The computer 70 may be configured as, for example, a PC, a smartphone, a tablet, or the like.

[0027] The system 10 includes an image forming device 80 for using the print scan system 30, the document management system 40, and the document processing system 50 via the platform 20. The system 10 can include an image forming device having a similar configuration to the image forming device 80 other than the image forming device 80. The image forming device 80 may be configured, for example, by an MFP (Multifunction Peripheral).

[0028] FIG. 2 is a block diagram of the platform 20 when it is configured with one PC.

[0029] As shown in Figure 2, the platform 20 includes an operation unit 21, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 22, which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a communication unit 23, which is a communication device that communicates with external devices via a network such as a LAN (Local Area Network) or the Internet, or directly via a wired or wireless connection without using a network; a memory unit 24, which is a non-volatile memory device such as a semiconductor memory or an HDD (Hard Disk Drive) that stores various information; and a control unit 25 that controls the entire platform 20.

[0030] The storage unit 24 can store a platform program 24a for realizing the platform 20 on a PC. The platform program 24a may be installed on the platform 20 during the manufacturing stage of the platform 20, or may be additionally installed on the platform 20 from an external storage medium such as a USB (Universal Serial Bus) memory, or may be additionally installed on the platform 20 from a network.

[0031] The storage unit 24 stores an application management table 24b for managing web applications executed on the platform 20.

[0032] FIG. 3 is a diagram showing an example of the application management table 24b.

[0033] As shown in FIG. 3, application management table 24b stores identification information of a web application (hereinafter referred to as an "application ID"), a name of the web application (hereinafter referred to as an "application name"), a uniform resource locator (URL) of a top screen of the web application, a URL of a setting screen of the web application, user management function support information indicating whether the web application supports a specific function for executing various settings for a user (hereinafter referred to as a "user management function"), group management function support information indicating whether the web application supports a specific function for executing various settings for a group to which the user belongs (hereinafter referred to as a "group management function"), device management function support information indicating whether the web application supports a specific function for executing various settings for an image forming apparatus (hereinafter referred to as a "device management function"), PIN authentication function support information indicating whether the web application supports a specific function for logging in to the web application from an image forming apparatus using a PIN (Personal Identification Number) code (hereinafter referred to as a "PIN authentication function"), and an IC (Integrated Circuit) as an ID (identity) card from the image forming apparatus. For each web application, the table shows ID card authentication function support information indicating whether the web application supports a specific function (hereinafter referred to as the "ID card authentication function") of logging in to the web application using an ID card (ID card authentication function), first storage utilization function support information indicating whether the web application supports a specific function (hereinafter referred to as the "first storage utilization function") of using a first storage service as an external storage service of system 10, and second storage utilization function support information indicating whether the web application supports a specific function (hereinafter referred to as the "second storage utilization function") of using a second storage service as an external storage service of system 10.

[0034] The storage service may be, for example, Google Drive, Box® or MS365 (SharePoint® / OneDrive®).

[0035] As shown in FIG. 2, the storage unit 24 stores a prohibited storage management table 24c for managing, for each region, storage services external to the system 10 that are prohibited from being used.

[0036] The storage unit 24 stores an organization management table 24 d for managing organizations that use the platform 20 .

[0037] FIG. 4 is a diagram showing an example of the organization management table 24d.

[0038] As shown in FIG. 4, the organization management table 24d indicates, for each organization, the organization's identification information (hereinafter referred to as "organization ID"), the organization's location, the contract status of the print scan system 30, the contract status of the document management system 40, and the contract status of the document processing system 50. The organization management table 24d shown in FIG. 4 specifically shows only some values. The organization ID is automatically assigned by the platform 20 when the organization is registered with the platform 20. The organization's location is entered by a person authorized to register an organization with the platform 20, such as a sales company or dealer that sells image forming devices to organizations using the platform 20. As the value of the contract status of a web application, if the organization has a contract for the web application, the platform 20 enters the end date and time of the contract period for the web application. If the organization does not have a contract for the web application, the platform 20 enters "not yet contracted." Web applications can be used through a subscription contract.

[0039] As shown in FIG. 2, the storage unit 24 stores a user management table 24e for managing users.

[0040] FIG. 5 is a diagram showing an example of the user management table 24e.

[0041] As shown in FIG. 5, the user management table 24e indicates, for each user, the user's identification information (hereinafter referred to as "user ID"), organization information indicating the organization to which the user belongs, group information indicating the group to which the user belongs, the user's password, the user's name (hereinafter referred to as "user name"), the user's email address, authority information indicating whether the user is an administrative user or a general user, and available app information indicating web applications available to the user. The user management table 24e shown in FIG. 5 specifically shows only some values. The user ID is automatically assigned by the platform 20 when the user is registered on the platform 20. The organization information indicates the organization to which the user belongs using the organization ID. The group information indicates the group to which the user belongs using the group's identification information (hereinafter referred to as "group ID"). The available app information indicates the web applications available to the user using the app ID.

[0042] As shown in FIG. 2, the storage unit 24 stores a group management table 24f for managing groups.

[0043] FIG. 6 is a diagram showing an example of the group management table 24f.

[0044] As shown in FIG. 6, the group management table 24f indicates, for each group, the group ID of the group, affiliated organization information indicating the organization to which the group belongs, the name of the group (hereinafter referred to as the "group name"), and usable app information indicating web applications that the group can use. The group management table 24f shown in FIG. 6 specifically shows only some values. The group ID is automatically assigned by the platform 20 when a group is registered in the platform 20. The affiliated organization information is information that indicates, by an organization ID, the organization to which the group belongs. The usable app information is information that indicates, by an app ID, web applications that the group can use.

[0045] As shown in FIG. 2, the storage unit 24 stores an apparatus management table 24g for managing image forming apparatuses.

[0046] FIG. 7 is a diagram showing an example of the device management table 24g.

[0047] As shown in Fig. 7, the device management table 24g indicates, for each image forming device, the identification information (hereinafter referred to as the "serial number") of the image forming device, affiliated organization information indicating the organization to which the image forming device belongs, and usable application information indicating web applications that the image forming device can use. The device management table 24g shown in Fig. 7 specifically shows only some values. The affiliated organization information is information that indicates, by organization ID, the organization to which the image forming device belongs. The usable application information is information that indicates, by application ID, web applications that the image forming device can use.

[0048] As shown in FIG. 2, the storage unit 24 stores a PIN management table 24h for managing PIN codes.

[0049] FIG. 8 is a diagram showing an example of the PIN management table 24h.

[0050] 8, the PIN management table 24h indicates, for each user, a user ID, permission information indicating whether the user is permitted to use the PIN authentication function, the user's PIN code, and the date and time the PIN code was generated. In the PIN management table 24h shown in FIG. 8, only some values are specifically shown.

[0051] As shown in FIG. 2, the storage unit 24 stores an ID card management table 24i for managing ID cards.

[0052] FIG. 9 is a diagram showing an example of the ID card management table 24i.

[0053] As shown in Fig. 9, the ID card management table 24i indicates, for each user, the user ID, permission information indicating whether the user is permitted to use the ID card authentication function, the ID card number of the user, and the registration date of each ID card. The ID card management table 24i shown in Fig. 9 specifically shows only some values. Multiple ID cards can be registered for one user.

[0054] As shown in FIG. 2, the storage unit 24 stores a first storage management table 24j for managing the first storage service and a second storage management table 24k for managing the second storage service.

[0055] FIG. 10 is a diagram showing an example of the first storage management table 24j.

[0056] 10, the first storage management table 24j indicates, for each user, a user ID, usage permission information indicating whether the user is permitted to use the first storage service, and an access token for the user for the first storage service. In the first storage management table 24j shown in FIG. 10, only some values are specifically shown.

[0057] The configuration of the second storage management table 24k (see FIG. 2) is similar to the configuration of the first storage management table 24j, so a detailed description will be omitted.

[0058] 2 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) that serves as a memory used as a work area for the CPU of the control unit 25. The CPU of the control unit 25 executes programs stored in the storage unit 24 or the ROM of the control unit 25.

[0059] By executing the platform program 24a, the control unit 25 realizes the application utilization unit 25a, which serves as an entry point for users logged in to the platform 20 to use the print scan system 30, document management system 40, and document processing system 50. The application utilization unit 25a generates web pages to be displayed in a web browser (described below). In the following, the display by the web browser is based on the web page data generated by the application utilization unit 25a. However, in the following, a detailed explanation of the mechanism for display by the web browser will be omitted.

[0060] FIG. 11 is a block diagram of a computer 70 when configured as a PC.

[0061] As shown in FIG. 11, computer 70 includes an operation unit 71, which is an operation device such as a keyboard or mouse through which various operations are input; a display unit 72, which is a display device such as an LCD that displays various information; a communication unit 73, which is a communication device that communicates with external devices via a network such as a LAN or the Internet, or directly via a wired or wireless connection without using a network; a memory unit 74, which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information; and a control unit 75 that controls computer 70 as a whole.

[0062] The storage unit 74 can store a program for a web browser (hereinafter referred to as the "web browser program") 74a. The web browser program 74a may be installed on the computer 70 during the manufacturing process of the computer 70, or may be additionally installed on the computer 70 from an external storage medium such as a USB memory, or may be additionally installed on the computer 70 from a network.

[0063] The control unit 75 includes, for example, a CPU, a ROM that stores programs and various data, and a RAM that serves as a memory used as a work area for the CPU of the control unit 75. The CPU of the control unit 75 executes programs stored in the storage unit 74 or the ROM of the control unit 75.

[0064] The control unit 75 executes the web browser program 74a to implement a web browser 75a.

[0065] FIG. 12 is a block diagram of an image forming apparatus 80 configured as an MFP.

[0066] As shown in FIG. 12, the image forming apparatus 80 is a computer that includes an operation unit 81, which is an operation device such as a button through which various operations are input; a display unit 82, which is a display device such as an LCD that displays various information; a printer 83, which is a printing device that prints images on a recording medium such as paper; a scanner 84, which is a reading device that reads images from a document; a communication unit 85, which is a communication device that communicates with an external device via a network such as a LAN or the Internet, or directly via a wired or wireless connection without using a network; a fax communication unit 86, which is a fax device that communicates with an external facsimile machine (not shown) via a communication line such as a public telephone line; an IC card reader 87 that reads an IC card; a memory unit 88, which is a non-volatile memory device such as a semiconductor memory or HDD that stores various information; and a control unit 89 that controls the entire image forming apparatus 80.

[0067] The storage unit 88 can store a platform access program 88a for accessing the platform 20. The platform access program 88a may be installed in the image forming device 80 during the manufacturing stage of the image forming device 80, or may be additionally installed in the image forming device 80 from an external storage medium such as a USB memory, or may be additionally installed in the image forming device 80 from a network.

[0068] The control unit 89 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) that serves as a memory used as a work area for the CPU of the control unit 89. The CPU of the control unit 89 executes programs stored in the storage unit 88 or the ROM of the control unit 89.

[0069] The control unit 89 executes the platform access program 88a to implement a platform access unit 89a that accesses the platform 20.

[0070] Next, the operation of the platform 20 when logged in by a user will be described.

[0071] FIG. 13 is a flow chart of the operation of the platform 20 when logged in by a user.

[0072] When a user accesses the platform 20 using the web browser 75a of the computer 70, the application use unit 25a of the platform 20 executes the operation shown in FIG.

[0073] 13, the application use unit 25a generates a web page of a login screen for the user to log in to the platform 20 (S101). Therefore, after the user inputs a user ID and password into the login screen displayed by the web browser 75a, the user can instruct the login to the platform 20 on the login screen.

[0074] When the process of S101 ends, the application use unit 25a determines whether or not an instruction to log in to the platform 20 has been issued until it determines that an instruction to log in to the platform 20 has been issued (S102).

[0075] When the application utilization unit 25a determines in S102 that a login to the platform 20 has been instructed, it determines whether or not to permit the user to log in based on the combination of user ID and password entered on the login screen and the combination of user ID and password shown in the user management table 24e (S103).

[0076] If the application use unit 25a determines in S103 that the user's login is not permitted, it includes a message indicating that the user's login is not permitted in the web page (S104), and executes the process of S101.

[0077] When the application utilization unit 25a determines in S103 that the user's login is permitted, it determines whether the user (hereinafter referred to as the "login user") whose login has been permitted in S103 is an administrative user or a general user based on the authority information in the user management table 24e (S105).

[0078] If the application usage unit 25a determines in S105 that the logged-in user is an administrative user, it generates a web page for the administrative user's top screen (hereinafter referred to as the "administrative user's top screen") 200 (see Figure 14) (S106) and terminates the operation shown in Figure 13.

[0079] FIG. 14 is a diagram showing an example of the top screen 200 for an administrative user.

[0080] As shown in FIG. 14, the top screen 200 for the administrative user includes a license management operation unit 201 for managing licenses for web applications, a user setting operation unit 202 for performing settings related to users who belong to the organization to which the logged-in user belongs, a group setting operation unit 203 for performing settings related to groups that belong to the organization to which the logged-in user belongs, a device setting operation unit 204 for performing settings related to image forming devices that belong to the organization to which the logged-in user belongs, a PIN authentication setting operation unit 205 for performing settings for the PIN authentication function, an ID card authentication setting operation unit 206 for performing settings for the ID card authentication function, and a storage setting operation unit 207 for performing settings for storage services external to the system 10.

[0081] When the license management operation unit 201 is pressed, the application usage unit 25a includes an area for managing the license of a web application (hereinafter referred to as the "license management area") in the web page. The license management area is an area where a subscription contract for a web application can be executed for the organization to which the login user belongs, or where a subscription contract for a web application can be canceled for the organization to which the login user belongs. When a subscription contract for a web application for the organization to which the login user belongs is executed in the license management area, the application usage unit 25a registers the end date and time of the contract period in the organization management table 24d as the contract status of the web application for which the subscription contract has been executed for the organization to which the login user belongs. When a subscription contract for a web application for the organization to which the login user belongs is canceled in the license management area, the application usage unit 25a registers "not yet subscribed" as the contract status of the web application for which the subscription contract has been executed for the organization to which the login user belongs in the organization management table 24d.

[0082] FIG. 15 is a flowchart of the operation of the platform 20 when the subscription contract period expires.

[0083] As shown in FIG. 15, the application usage unit 25a determines whether the end date and time of the contract period prior to the current time is registered as the contract status of the web application in the organization management table 24d until it determines that the end date and time of the contract period prior to the current time is registered as the contract status of the web application in the organization management table 24d (S111).

[0084] If the application usage unit 25a determines in S111 that the end date and time of the contract period prior to the current time is registered as the contract status of the web application in the organization management table 24d, it overwrites the contract status of the end date and time of the contract period prior to the current time registered in the organization management table 24d with "not yet contracted" (S112), and executes the processing of S111.

[0085] FIG. 16 is a flowchart of the operation of the platform 20 when the user setting operation section 202 (see FIG. 14) is pressed.

[0086] As shown in FIG. 16, when the user setting operation section 202 is pressed, the application utilization section 25a identifies the web applications under contract with the organization to which the login user belongs, based on the contract status of the web applications associated in the organization management table 24d with the organization ID associated in the affiliated organization information in the user management table 24e with the user ID of the login user (S121).

[0087] When the processing of S121 is completed, the application utilization unit 25a determines whether any of the web applications identified in S121 and under contract with the organization to which the logged-in user belongs supports the user management function based on the user management function support information in the application management table 24b (S122).

[0088] If the application utilization unit 25a determines in S122 that any of the web applications under contract with the organization to which the logged-in user belongs supports the user management function, it includes settings related to the user management function, i.e., a specific area for executing various settings for the user (hereinafter referred to as the "user setting area") in the web page (S123).

[0089] When the application utilization unit 25a determines in S122 that none of the web applications under contract with the organization to which the logged-in user belongs supports the user management function, or when the processing of S123 ends, the operation shown in FIG. 16 ends.

[0090] The user setting area is an area where the logged-in user can add a user to the organization to which the logged-in user belongs, set various user information for the organization to which the logged-in user belongs, and delete a user from the organization to which the logged-in user belongs. When a user is added in the user setting area, the application utilization unit 25a automatically sets the user ID of the added user. The administrative user can set a password, user name, email address, permission information, and available web applications for a user in the organization to which the administrative user belongs in the user setting area. When any of the user's password, user name, email address, permission information, and available web applications is set in the user setting area, the application utilization unit 25a reflects the set information in the user management table 24e.

[0091] When the group setting operation unit 203 (see FIG. 14) is pressed, the application utilization unit 25a operates in the same manner as the operation shown in FIG. 16. However, the application utilization unit 25a determines whether any of the web applications under contract with the organization to which the login user belongs supports the group management function based on the group management function support information in the application management table 24b. If the application utilization unit 25a determines that any of the web applications under contract with the organization to which the login user belongs supports the group management function, the application utilization unit 25a includes a specific area (hereinafter referred to as a "group setting area") for setting the group management function, i.e., for executing various settings for groups, in the web page. On the other hand, if the application utilization unit 25a determines that none of the web applications under contract with the organization to which the login user belongs supports the group management function, the application utilization unit 25a does not include a group setting area in the web page.

[0092] The group setting area is an area where the logged-in user can add a group to the organization to which the logged-in user belongs, set various information about the group for the organization to which the logged-in user belongs, and delete a group for the organization to which the logged-in user belongs. When a group is added in the group setting area, the application usage unit 25a automatically sets a group ID for the added group. The administrative user can set a group name, members, and available web applications for a group in the organization to which the administrative user belongs in the group setting area. When the group name and available web applications for the group are set in the group setting area, the application usage unit 25a reflects the set information in the group management table 24f. When the users belonging to the group are set in the group setting area, the application usage unit 25a reflects the set information in the user management table 24e.

[0093] When the device setting operation section 204 (see FIG. 14) is pressed, the application usage section 25a operates in the same manner as shown in FIG. 16. However, the application usage section 25a determines whether any of the web applications under contract with the organization to which the login user belongs supports the device management function based on the device management function support information in the application management table 24b. If the application usage section 25a determines that any of the web applications under contract with the organization to which the login user belongs supports the device management function, the application usage section 25a includes a specific area (hereinafter referred to as the "device setting area") for setting the device management function, i.e., for executing various settings for the image forming device, in the web page. On the other hand, if the application usage section 25a determines that none of the web applications under contract with the organization to which the login user belongs supports the device management function, the application usage section 25a does not include the device setting area in the web page.

[0094] The device setting area is an area where the logged-in user can add an image forming device to the organization to which the logged-in user belongs, set various information about the image forming device for the organization to which the logged-in user belongs, and delete an image forming device for the organization to which the logged-in user belongs. The administrative user can set the serial number of the image forming device and the available web applications for the organization to which the administrative user belongs in the device setting area. When the serial number of the image forming device and the available web applications are set in the device setting area, the application usage unit 25a reflects the set information in the device management table 24g.

[0095] The serial number of the image forming apparatus in the apparatus management table 24g can also be registered from the image forming apparatus itself via the platform access unit.

[0096] When the PIN authentication setting operation unit 205 (see FIG. 14) is pressed, the application utilization unit 25a operates in the same manner as shown in FIG. 16. However, the application utilization unit 25a determines whether any of the web applications under contract with the organization to which the login user belongs supports the PIN authentication function based on the PIN authentication function support information in the application management table 24b. If the application utilization unit 25a determines that any of the web applications under contract with the organization to which the login user belongs supports the PIN authentication function, the application utilization unit 25a includes a specific area (hereinafter referred to as the "PIN authentication setting area") in the web page for configuring the PIN authentication function, i.e., for configuring permission for use of the PIN authentication function for each user. On the other hand, if the application utilization unit 25a determines that none of the web applications under contract with the organization to which the login user belongs supports the PIN authentication function, the application utilization unit 25a does not include the PIN authentication setting area in the web page.

[0097] The PIN authentication setting area is an area where it is possible to permit or prohibit use of the PIN authentication function. When whether or not to permit use of the PIN authentication function is set in the PIN authentication setting area, the application use unit 25a reflects use permission information corresponding to the set information in the PIN management table 24h.

[0098] When the ID card authentication setting operation unit 206 (see FIG. 14) is pressed, the application utilization unit 25a operates in the same manner as shown in FIG. 16. However, the application utilization unit 25a determines whether any of the web applications under contract with the organization to which the login user belongs supports the ID card authentication function based on the ID card authentication function support information in the application management table 24b. If the application utilization unit 25a determines that any of the web applications under contract with the organization to which the login user belongs supports the ID card authentication function, the application utilization unit 25a includes a specific area (hereinafter referred to as the "ID card authentication setting area") in the web page for configuring the ID card authentication function, i.e., for enabling use of the ID card authentication function for each user. On the other hand, if the application utilization unit 25a determines that none of the web applications under contract with the organization to which the login user belongs supports the ID card authentication function, the application utilization unit 25a does not include the ID card authentication setting area in the web page.

[0099] The ID card authentication setting area is an area where it is possible to permit or prohibit the use of the ID card authentication function. When whether or not to permit the use of the ID card authentication function is set in the ID card authentication setting area, the application use unit 25a reflects the usage permission information corresponding to the set information in the ID card management table 24i.

[0100] FIG. 17 is a flowchart of the operation of the platform 20 when the storage setting operation section 207 (see FIG. 14) is pressed.

[0101] As shown in FIG. 17, when the storage setting operation section 207 is pressed, the application utilization section 25a identifies the web applications under contract with the organization to which the login user belongs, based on the contract status of the web applications associated in the organization management table 24d with the organization ID associated in the affiliated organization information in the user management table 24e with the user ID of the login user (S131).

[0102] When the processing of S131 is completed, the application utilization unit 25a determines whether the first storage service is associated in the prohibited storage management table 24c with the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e (S132).

[0103] When the application usage unit 25a determines in S132 that the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is not associated with the first storage service in the prohibited storage management table 24c, it determines whether any of the web applications under contract with the organization to which the logged-in user belongs, identified in S131, supports the first storage usage function based on the first storage usage function support information in the application management table 24b (S133).

[0104] If the application usage unit 25a determines in S133 that any of the web applications under contract with the organization to which the logged-in user belongs supports the first storage usage function, it includes in the web page a specific area (hereinafter referred to as the "first storage setting area") for setting the first storage usage function, i.e., setting permission to use the first storage service (S134).

[0105] The application usage unit 25a determines in S132 that the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is associated with the first storage service in the prohibited storage management table 24c, or determines in S133 that none of the web applications under contract with the organization to which the logged-in user belongs support the first storage usage function, or, upon completion of the processing of S134, determines whether the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is associated with the second storage service in the prohibited storage management table 24c (S135).

[0106] When the application usage unit 25a determines in S135 that the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is not associated with a second storage service in the prohibited storage management table 24c, it determines whether any of the web applications under contract with the organization to which the logged-in user belongs, identified in S131, supports the second storage usage function based on the second storage usage function support information in the application management table 24b (S136).

[0107] If the application usage unit 25a determines in S136 that any of the web applications under contract with the organization to which the logged-in user belongs supports the second storage usage function, it includes in the web page a specific area (hereinafter referred to as the "second storage setting area") for setting the second storage usage function, i.e., setting permission to use the second storage service (S137).

[0108] The application usage unit 25a terminates the operation shown in Figure 17 when it determines in S135 that the second storage service is associated in the prohibited storage management table 24c with the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e, or when it determines in S136 that none of the web applications under contract with the organization to which the logged-in user belongs support the second storage usage function.

[0109] The first storage setting area is an area where it is possible to permit or prohibit the use of the first storage service. When whether or not to permit the use of the first storage service is set in the first storage setting area, the application use unit 25a reflects usage permission information corresponding to the set information in the first storage management table 24j. Similarly, the second storage setting area is an area where it is possible to permit or prohibit the use of the second storage service. When whether or not to permit the use of the second storage service is set in the second storage setting area, the application use unit 25a reflects usage permission information corresponding to the set information in the second storage management table 24k.

[0110] As shown in Figure 13, when the application usage unit 25a determines in S105 that the logged-in user is a general user, it generates a web page for the top screen for general users (hereinafter referred to as the "top screen for general users") 210 (see Figure 18) (S107) and terminates the operation shown in Figure 13.

[0111] FIG. 18 is a diagram showing an example of the top screen 210 for general users.

[0112] As shown in FIG. 18, the top screen 210 for general users includes an application name display section 211a showing the application name of the print scanning system 30, an application name access operation section 211b for accessing the URL of the top screen of the print scanning system 30, an application name access operation section 211c for accessing the URL of the settings screen of the print scanning system 30, an application name display section 212a showing the application name of the document management system 40, an application name access operation section 212b for accessing the URL of the top screen of the document management system 40, an application name access operation section 212c for accessing the URL of the settings screen of the document management system 40, an application name display section 213a showing the application name of the document processing system 50, an application name access operation section 213b for accessing the URL of the top screen of the document processing system 50, and an application name access operation section 213c for accessing the URL of the settings screen of the document processing system 50.

[0113] The application utilization unit 25a identifies a web application for which the organization to which the login user belongs has a contract, based on the contract status of the web application associated in the organization management table 24d with the organization ID associated in the affiliated organization information in the user management table 24e with the user ID of the login user, and identifies the application name, URL of the top screen, and URL of the setting screen of the identified web application based on the application management table 24b. The general user top screen 210 shown in FIG. 18 includes an application name display unit, a top screen access operation unit, and a setting screen access operation unit for the print scan system 30, the document management system 40, and the document processing system 50. However, the general user top screen 210 does not have to include the application name display unit, the top screen access operation unit, and the setting screen access operation unit for the web application for which the organization to which the login user belongs has not a contract.

[0114] A general user can open the top page or settings screen of a contracted web application from the general user top page 210. In other words, a general user can use each of the print scan system 30, document management system 40, and document processing system 50 by logging in to the platform 20, without having to log in to each of the print scan system 30, document management system 40, and document processing system 50 individually.

[0115] The top screen 210 for general users includes a user setting operation section 214 for executing settings related to the logged-in user, a PIN authentication setting operation section 215 for executing settings of the PIN authentication function related to the logged-in user, an ID card authentication setting operation section 216 for executing settings of the ID card authentication function related to the logged-in user, and a storage setting operation section 217 for executing settings of the storage service related to the logged-in user.

[0116] When the user setting operation section 214 is pressed, the application utilization section 25a operates in the same manner as the operation shown in Fig. 16. However, if the application utilization section 25a determines that any of the web applications under contract with the organization to which the login user belongs supports the user management function, the application utilization section 25a includes, in the web page, settings related to the user management function, i.e., a specific area for executing various settings for the login user (hereinafter referred to as the "login user setting area"). On the other hand, if the application utilization section 25a determines that none of the web applications under contract with the organization to which the login user belongs supports the user management function, the application utilization section 25a does not include the login user setting area in the web page.

[0117] The login user setting area is an area where various information about the login user can be set. The login user can set the login user's password, user name, and email address in the login user setting area. When any of the login user's password, user name, and email address is set in the login user setting area, the application utilization unit 25a updates the user management table 24e with the set information.

[0118] FIG. 19 is a flowchart of the operation of the platform 20 when the PIN authentication setting operation section 215 (see FIG. 18) is pressed.

[0119] As shown in FIG. 19, when the PIN authentication setting operation section 215 is pressed, the application use section 25a determines whether or not "permitted" is associated with the user ID of the logged-in user in the usage permission information in the PIN management table 24h (S141).

[0120] When the application usage unit 25a determines in S141 that the user ID of the logged-in user is associated with "Allowed" in the usage permission information in the PIN management table 24h, it identifies the web applications under contract with the organization to which the logged-in user belongs, based on the contract status of the web applications associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e (S142).

[0121] When the processing of S142 is completed, the application utilization unit 25a determines whether any of the web applications identified in S142 and under contract with the organization to which the logged-in user belongs supports the PIN authentication function based on the PIN authentication function support information in the application management table 24b (S143).

[0122] If the application utilization unit 25a determines in S143 that any of the web applications under contract with the organization to which the login user belongs supports the PIN authentication function, the application utilization unit 25a includes in the web page a specific area (hereinafter referred to as the "PIN authentication setting area for the login user") 220 (see Figure 20) for executing settings related to the PIN authentication function for the login user (S144).

[0123] The application usage unit 25a terminates the operation shown in FIG. 19 when it determines in S141 that the user ID of the logged-in user is not associated with "Allowed" in the usage permission information in the PIN management table 24h, or when it determines in S143 that none of the web applications under contract with the organization to which the logged-in user belongs support the PIN authentication function, or when the processing of S144 is completed.

[0124] FIG. 20 is a diagram showing an example of the login user PIN authentication setting area 220. As shown in FIG.

[0125] 20 is an area where a PIN code for a login user can be generated in response to an instruction from the login user. The login user PIN authentication setting area 220 includes a PIN code display unit 221 that displays the PIN code for the login user in the PIN management table 24h, a generation date and time display unit 222 that displays the date and time when the PIN code for the login user was generated in the PIN management table 24h, and a PIN code generation operation unit 223 for generating a new PIN code. When a PIN code for the login user is generated in the login user PIN authentication setting area, the application utilization unit 25a updates the PIN management table 24h with the generated PIN code and the generation date and time of this PIN code.

[0126] When the ID card authentication setting operation unit 216 (see FIG. 18) is pressed, the application utilization unit 25a operates in the same manner as shown in FIG. 19. However, the application utilization unit 25a determines whether “permitted” is associated with the user ID of the login user in the usage permission information in the ID card management table 24i. The application utilization unit 25a also determines whether any of the web applications under contract with the organization to which the login user belongs supports the ID card authentication function based on the ID card authentication function support information in the application management table 24b. If the application utilization unit 25a determines that any of the web applications under contract with the organization to which the login user belongs supports the ID card authentication function, the application utilization unit 25a includes a specific area (hereinafter referred to as the “ID card authentication setting area for login user”) 230 (see FIG. 21) for executing settings related to the ID card authentication function for the login user in the web page. On the other hand, if the application utilization unit 25a determines that none of the web applications under contract with the organization to which the login user belongs supports the ID card authentication function, the application utilization unit 25a does not include the ID card authentication setting area for login user 230 in the web page.

[0127] FIG. 21 is a diagram showing an example of the login user ID card authentication setting area 230. As shown in FIG.

[0128] 21 is an area where the card number of the login user's ID card can be registered or deregistered in response to an instruction from the login user. The login user's ID card authentication setting area 230 includes card number display areas 231a, 232a, and 233a that indicate the card number of the login user in the ID card management table 24i, registration date display areas 231b, 232b, and 233b that indicate the registration date of the login user's card number in the ID card management table 24i, card number deletion operation areas 231c, 232c, and 233c for deleting the login user's card number in the ID card management table 24i, and a card number addition operation area 234 for adding a new card number. When the card number of the login user's ID card is registered in the login user's ID card authentication setting area, the application utilization unit 25a updates the ID card management table 24i with the registered card number and the registration date of this card number.

[0129] The card number in the ID card management table 24i can also be read from the actual ID card by the IC card reader of the image forming apparatus and registered together with the registration date from the image forming apparatus itself via the platform access unit.

[0130] FIG. 22 is a flowchart of the operation of the platform 20 when the storage setting operation section 217 (see FIG. 18) is pressed.

[0131] As shown in FIG. 22, when the storage setting operation section 217 is pressed, the application utilization section 25a identifies the web applications under contract with the organization to which the login user belongs, based on the contract status of the web applications associated in the organization management table 24d with the organization ID associated in the affiliated organization information in the user management table 24e with the user ID of the login user (S151).

[0132] When the process of S151 ends, the application utilization unit 25a determines whether or not "permitted" is associated with the user ID of the logged-in user in the usage permission information in the first storage management table 24j (S152).

[0133] When the application usage unit 25a determines in S152 that the user ID of the logged-in user is associated with "permitted" in the usage permission information in the first storage management table 24j, it determines whether the first storage service is associated in the prohibited storage management table 24c with the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e (S153).

[0134] When the application usage unit 25a determines in S153 that the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is not associated with the first storage service in the prohibited storage management table 24c, it determines whether any of the web applications under contract with the organization to which the logged-in user belongs, identified in S151, supports the first storage usage function based on the first storage usage function support information in the application management table 24b (S154).

[0135] If the application usage unit 25a determines in S154 that any of the web applications under contract with the organization to which the logged-in user belongs supports the first storage usage function, it includes in the web page a specific area (hereinafter referred to as the "first storage setting area for logged-in user") 240 (see Figure 23) for performing settings related to the first storage usage function, i.e., settings of the first storage service related to the logged-in user (S155).

[0136] The application usage unit 25a determines in S152 that the user ID of the logged-in user is not associated with "permitted" in the usage permission information in the first storage management table 24j, determines in S153 that the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is associated with the first storage service in the prohibited storage management table 24c, determines in S154 that none of the web applications under contract with the organization to which the logged-in user belongs support the first storage usage function, or, upon completion of processing in S155, determines whether the user ID of the logged-in user is associated with "permitted" in the usage permission information in the second storage management table 24k (S156).

[0137] When the application usage unit 25a determines in S156 that the user ID of the logged-in user is associated with "permitted" in the usage permission information in the second storage management table 24k, it determines whether a second storage service is associated in the prohibited storage management table 24c with the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e (S157).

[0138] If the application usage unit 25a determines in S157 that the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is not associated with a second storage service in the prohibited storage management table 24c, it determines whether any of the web applications under contract with the organization to which the logged-in user belongs, identified in S151, supports the second storage usage function based on the second storage usage function support information in the application management table 24b (S158).

[0139] If the application usage unit 25a determines in S158 that any of the web applications under contract with the organization to which the logged-in user belongs supports the second storage usage function, it includes in the web page a specific area (hereinafter referred to as the "second storage setting area for the logged-in user") 250 (see Figure 23) for performing settings related to the second storage usage function, i.e., settings of the second storage service related to the logged-in user (S159).

[0140] The application usage unit 25a terminates the operation shown in Figure 22 when it determines in S156 that the user ID of the logged-in user is not associated with "Allowed" in the usage permission information in the second storage management table 24k, determines in S157 that the location associated in the organization management table 24d with the organization ID associated with the user ID of the logged-in user in the affiliated organization information in the user management table 24e is associated with a second storage service in the prohibited storage management table 24c, determines in S158 that none of the web applications under contract with the organization to which the logged-in user belongs support the second storage usage function, or when the processing of S159 is completed.

[0141] FIG. 23 is a diagram showing an example of the first storage setting area 240 for the logged-in user and the second storage setting area 250 for the logged-in user.

[0142] 23 is an area where an access token for the login user for the first storage service can be registered or deregistered according to an instruction from the login user. Similarly, the second storage setting area 250 for the login user is an area where an access token for the login user for the second storage service can be registered or deregistered according to an instruction from the login user.

[0143] The first storage setting area 240 for the logged-in user includes a storage name display section 241 for displaying the name of the first storage service, a connection status operation section 242 for connecting to or disconnecting from the first storage service, and a connection status display section 243 for displaying the connection status to the first storage service. Similarly, the second storage setting area 250 for the logged-in user includes a storage name display section 251 for displaying the name of the second storage service, a connection status operation section 252 for connecting to or disconnecting from the second storage service, and a connection status display section 253 for displaying the connection status to the second storage service. The appearance of the connection status operation section and the connection status display section differs depending on whether the storage service is connected or not. When connected to a storage service, the appearance of the connection status operation section and the connection status display section is the same as the appearance of the connection status operation section 242 and the connection status display section 243, respectively, shown in FIG. 23 . The appearance of the connection status operation unit and connection status display unit when not connected to a storage service is the same as the appearance of the connection status operation unit 252 and connection status display unit 253 shown in FIG.

[0144] When the connection status operation unit 242 is operated while the application utilization unit 25a is not connected to the first storage service, the application utilization unit 25a accesses the first storage service and causes the web browser 75a to display a login screen for the first storage service. Therefore, a login user of the platform 20 can log in to the first storage service by inputting account information for connecting the login user of the platform 20 to the login screen for the first storage service. Then, when the login user of the platform 20 logs in to the first storage service and obtains an access token from the first storage service, the application utilization unit 25a writes the obtained access token to the first storage management table 24j and changes the appearance of the connection status operation unit 242 and the connection status display unit 243 to an appearance when the application utilization unit 25a is connected to the first storage service. When the connection status operation unit 242 is operated while the application usage unit 25a is connected to the first storage service, the application usage unit 25a executes logging out of the logged-in user of the platform 20 for the first storage service, deletes the access token of the logged-in user of the platform 20 from the first storage management table 24j, and changes the appearance of the connection status operation unit 242 and the connection status display unit 243 to the appearance when not connected to the first storage service.

[0145] Similarly, when the connection status operation unit 252 is operated while the application utilization unit 25a is not connected to the second storage service, the application utilization unit 25a accesses the second storage service and displays a login screen for the second storage service on the web browser 75a. Therefore, a login user of the platform 20 can log in to the second storage service by entering account information for connecting the login user of the platform 20 to the login screen for the second storage service. Then, when the login user of the platform 20 logs in to the second storage service and obtains an access token from the second storage service, the application utilization unit 25a writes the obtained access token to the second storage management table 24k and changes the appearance of the connection status operation unit 252 and the connection status display unit 253 to an appearance when connected to the second storage service. When the connection status operation unit 252 is operated while the application utilization unit 25a is connected to the second storage service, the application utilization unit 25a executes logging out of the logged-in user of the platform 20 for the second storage service, deletes the access token of the logged-in user of the platform 20 from the second storage management table 24k, and changes the appearance of the connection status operation unit 252 and the connection status display unit 253 to the appearance when not connected to the second storage service.

[0146] As described above, platform 20 is equipped with application utilization unit 25a that allows a user logged in to platform 20 to utilize multiple web applications. Therefore, when a user utilizes multiple web applications, the user does not need to log in to each of the multiple web applications, thereby improving convenience.

[0147] The platform 20 generates a web page that allows settings related to the web application to be executed (see FIGS. 14, 16 to 23), thereby improving convenience.

[0148] If any of the web applications under contract with the organization to which the user who is logged in to the platform 20 belongs supports a specific function (YES in S122, YES in S133, YES in S136, YES in S143, YES in S154, or YES in S158), the platform 20 includes a specific area on the web page for performing settings related to the specific function (S123, S134, S137, S144, S155, or S159), but if none of the under contract web applications supports the specific function (NO in S122, NO in S133, NO in S136, NO in S143, NO in S154, or NO in S158), the platform 20 does not include the specific area on the web page. This can increase the likelihood that the user will perform settings that need to be performed, while reducing the likelihood that the user will perform settings that do not need to be performed, thereby improving convenience.

[0149] The platform 20 may include a specific area for performing settings related to a specific function on a web page if any of the web applications under contract with the organization to which the user logged in to the platform 20 belongs supports the specific function, but may not include the specific area on the web page if none of the under contract web applications supports the specific function. However, the platform 20 may include a specific setting operation unit for including a specific area for performing settings related to the specific function on a web page in an operable state, as shown in FIGS. 14 and 18, if any of the web applications under contract with the organization to which the user logged in to the platform 20 belongs supports the specific function, and may include the specific setting operation unit in an inoperable state, as shown in FIG. 24, if none of the under contract web applications supports the specific function. Furthermore, the platform 20 may include a specific setting operation unit for including a specific area for performing settings related to the specific function on a web page in an operable state, as shown in FIGS. 14 and 18, if any of the web applications under contract with the organization to which the user logged in to the platform 20 belongs supports the specific function, but may not include the specific setting operation unit on a web page if none of the under contract web applications supports the specific function, as shown in FIG. 25.

[0150] FIG. 24 is a diagram showing an example of the top screen 200 for the administrative user in a state in which the device setting operation section 204 and the ID card authentication setting operation section 206 are inoperable.

[0151] 24, if none of the contracted web applications supports the device management function, the application usage unit 25a grays out the device setting operation unit 204 to make it inoperable. If none of the contracted web applications supports the ID card authentication function, the application usage unit 25a grays out the ID card authentication setting operation unit 206 to make it inoperable. Similarly, if none of the contracted web applications supports the PIN authentication function, the application usage unit 25a may gray out the PIN authentication setting operation unit 205 to make it inoperable. If none of the contracted web applications supports the first storage use function and none of the contracted web applications supports the second storage use function, the application usage unit 25a may gray out the storage setting operation unit 207 to make it inoperable. While the above description has been given of the administrative user top screen 200, the same applies to the general user top screen 210.

[0152] FIG. 25 is a diagram showing an example of the top screen 200 for the administrative user in a state in which the device setting operation section 204 (see FIG. 14) and the ID card authentication setting operation section 206 (see FIG. 14) are not displayed.

[0153] 25, application use unit 25a hides device setting operation unit 204 when none of the contracted web applications supports the device management function, and hides ID card authentication setting operation unit 206 when none of the contracted web applications supports the ID card authentication function. Similarly, application use unit 25a may hide PIN authentication setting operation unit 205 when none of the contracted web applications supports the PIN authentication function, or hide storage setting operation unit 207 when none of the contracted web applications supports the first storage use function and none of the contracted web applications supports the second storage use function. While the above description has been given of top screen 200 for administrative users, the same applies to top screen 210 for general users.

[0154] Platform 20 has a specific area that indicates whether a setting has been performed or not (see Figures 20, 21 and 23), making it easier for users to recognize settings that have not been performed, thereby improving convenience.

[0155] The platform 20 can execute settings common to the print scan system 30, document management system 40, and document processing system 50 in the user setting area, i.e., settings of a user's password, user name, email address, and authority information, thereby eliminating the need to execute similar settings for each of the print scan system 30, document management system 40, and document processing system 50, improving convenience. The platform 20 can execute settings common to the print scan system 30, document management system 40, and document processing system 50 in the group setting area, i.e., settings of a group name and users belonging to the group, thereby eliminating the need to execute similar settings for each of the print scan system 30, document management system 40, and document processing system 50, improving convenience. The platform 20 can execute settings common to the print scan system 30 and document management system 40 in the PIN authentication setting area, i.e., settings for permission to use the PIN authentication function, thereby eliminating the need to execute similar settings for each of the print scan system 30 and document management system 40, improving convenience. The platform 20 can execute settings common to the print scan system 30 and the document processing system 50 in the first storage setting area, i.e., settings for permission to use the first storage service, thereby improving convenience by eliminating the need to execute similar settings for each of the print scan system 30 and the document processing system 50. The platform 20 can execute settings common to the print scan system 30, the document management system 40, and the document processing system 50 in the login user setting area, i.e., settings for the login user's password, user name, email address, and authority information, thereby eliminating the need to execute similar settings for each of the print scan system 30, the document management system 40, and the document processing system 50, thereby improving convenience.The platform 20 can execute settings common to the print scan system 30 and the document management system 40 in the login user PIN authentication setting area, i.e., setting a PIN code for the login user, thereby improving convenience, as it is not necessary to execute similar settings for each of the print scan system 30 and the document management system 40. The platform 20 can execute settings common to the print scan system 30 and the document processing system 50 in the login user first storage setting area, i.e., setting an access token for the login user for the first storage service, thereby eliminating the need to execute similar settings for each of the print scan system 30 and the document processing system 50, thereby improving convenience.

[0156] In this embodiment, the platform 20 supports three web applications: a print scan system 30, a document management system 40, and a document processing system 50, but it may also support only two web applications, or four or more web applications.

[0157] In this embodiment, the platform 20 supports two storage services, a first storage service and a second storage service, but it may also support only one storage service, or three or more storage services. [Explanation of symbols]

[0158] 20 Platform (Computer) 24a Platform Program 25a Application Usage Section 30 Printing and scanning system (web application) 40 Document Management System (Web Application) 50 Document Processing System (Web Application)

Claims

1. A platform underlying the execution of multiple web applications, comprising: A platform comprising an application utilization unit that allows a user logged in to the platform to utilize a plurality of the web applications.

2. The platform according to claim 1 , wherein the application using unit generates a web page that can execute settings related to the web application.

3. The platform described in claim 2, characterized in that the application usage unit includes a specific area on the web page for performing the settings related to a specific function if any of the web applications under contract with the organization to which the user who is logged in to the platform belongs supports the specific function, and does not include the specific area on the web page if none of the web applications under contract with the organization supports the specific function.

4. The platform of claim 3 , wherein the specific area indicates whether the setting has been performed.

5. The platform of claim 2 , wherein the web page is capable of executing the settings common to a plurality of the web applications.

6. A platform program for realizing a platform that is the basis for executing multiple web applications on a computer, The platform program is characterized in that the platform includes an application utilization unit that allows a user logged in to the platform to utilize a plurality of the web applications.

Images