JP7249461B2 - APP MOVING SYSTEM, APP MOVEMENT METHOD, AND PROGRAM - Google Patents

Description

Application of Article 30, Paragraph 2 of the Patent Law February 25, 2021, https://kintone. cybozu. co. jp/, https://kintone. cybozu. co. jp/update/main/2021-03. html#point7 March 14, 2021, https://cybozu. com/ July 26, 2021, https://kintone. cybozu. co. jp/, https://kintone. cybozu. co. jp/update/main/2021-08. html#indev

The present disclosure relates to an application moving system, an application moving method, and a program.

Conventionally, a system is known in which arbitrary information can be shared by a user group to which a plurality of users belong. For example, Non-Patent Literature 1 describes a technique for setting access rights to applications placed inside or outside a space in which at least one of a user group participates. For example, in Non-Patent Document 2, when access rights are set to a database created in a workspace that allows information to be shared by multiple users, and the database is moved to another workspace, Techniques for setting access rights according to the type are described.

"Setting access rights to apps", Internet, searched on July 30, 2021, online, https://jp.cybozu.help/k/ja/user/app_settings/rights/app_rights.html "Moving a base from one workspace to another workspace", Internet, searched on July 30, 2021, online, https://support.airtable.com/hc/en-us/articles/215589438-Moving-a-base- from-one-workspace-to-another-workspace

A system like Non-Patent Document 1 is required to move an application between a public space and a private space or between inside and outside of a space. If you were able to move the app between them, you would need to set access rights according to the destination. If access rights can be automatically set according to the destination, it would be possible to reduce the user's work. The technique cannot be applied to the technique of Non-Patent Document 1.

One of the purposes of the present disclosure is to reduce the user's trouble when moving an app.

The application transfer system according to the present disclosure includes arrangement means for arranging an application inside or outside a space in which at least one member of a user group capable of information sharing participates, moving means for moving the app between a public space and a private space or between inside and outside the space; and a second setting means for setting authority according to the destination of the movement.

According to the present disclosure, it is possible to reduce the user's trouble when moving an application.

It is a figure which shows an example of the whole structure of an application movement system. It is a figure which shows an example of a portal screen. FIG. 10 is a diagram showing an example of a space created within a user group; It is a figure which shows an example of a space screen. It is a figure which shows an example of an application screen. It is a figure which shows an example of an application setting screen. It is a figure which shows an example of an access right setting screen. It is a figure which shows an example of the application setting screen with which the dialog was displayed. FIG. 10 is a diagram illustrating an example of setting access rights before and after moving an application; FIG. FIG. 4 is a functional block diagram showing functions realized by the application transfer system; FIG. 3 is a diagram showing an example of data storage in a user group database; FIG. FIG. 4 is a diagram showing an example of data storage in an application database; FIG. 4 is a flow diagram showing an example of processing executed in the application migration system; FIG. 4 is a flow diagram showing an example of processing executed in the application migration system;

[1. Overall Configuration of Application Transfer System]
An example of an embodiment of an application moving system according to the present disclosure will be described. FIG. 1 is a diagram showing an example of the overall configuration of an application moving system. For example, the application moving system S includes a server 10 and a user terminal 20. FIG. The network N is the Internet, LAN, or the like. The application migration system S only needs to include at least one computer, and is not limited to the example of FIG. 1 .

Server 10 is a server computer. Control unit 11 includes at least one processor. The storage unit 12 includes a volatile memory such as RAM and a nonvolatile memory such as a hard disk. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

The user terminal 20 is a user's computer. For example, the user terminal 20 is a personal computer, tablet terminal, smart phone, or wearable terminal. Hardware configurations of the control unit 21, the storage unit 22, and the communication unit 23 may be the same as those of the control unit 11, the storage unit 12, and the communication unit 13, respectively. The operation unit 24 is an input device such as a mouse, keyboard, or touch panel. The display unit 25 is a liquid crystal display or an organic EL display.

Note that the programs or data described as being stored in the storage units 12 and 22 may be supplied via the network N. The hardware configurations of the server 10 and the user terminal 20 are not limited to the above examples, and various hardware can be applied. For example, a reading unit for reading a computer-readable information storage medium (for example, an optical disk drive or memory card slot) or an input/output unit for directly connecting to an external device (for example, a USB terminal) may be included. In this case, the program or data stored in the information storage medium may be supplied via the reading section or the input/output section.

[2. Overview of App Transfer System]
In this embodiment, a case where the application transfer system S is applied to cloud-type groupware will be taken as an example. Users can share arbitrary information with other users using groupware. For example, users can share text, numbers, tables, diagrams, images, documents, videos, audio, any other files, or a combination thereof. For example, information can be shared within a user group.

A user group is a collection of users who share information. A user group is a group of users who can log in to a given page. For example, an organization such as a company or government office corresponds to a user group. A department or team within an organization also corresponds to a user group. Therefore, multiple user groups may exist within one organization. At least one user belongs to a user group. A user belongs to at least one user group.

In this embodiment, a subdomain exists for each user group. There is a one-to-one correspondence between user groups and subdomains. User groups can be identified by subdomains. For example, assume that the domain of the groupware provider is "abcde.com". When XYZ Corporation uses groupware, a subdomain such as "xyzcompany.abcde.com" is assigned. In this case, a group of employees of XYZ Corporation corresponds to the user group. Employees of XYZ Corporation access the subdomain and use groupware.

For example, an administrator of a certain user group enters information such as names and email addresses of users whom he/she wants to invite to this user group. Once this information is entered, the user's user ID and password are generated and an invitation email is sent to the user. For example, the invitation email includes a user ID and password, and a URL for logging in to the subdomain of the user group. When the user selects the URL of the invitation mail, the login screen for logging into the subdomain of the user group is displayed on the display unit 25 .

In this embodiment, a case where each screen such as a login screen is displayed using a browser will be described, but each screen may be displayed using a groupware application. When the user enters the user ID and password from the login screen, the user logs in to the subdomain of the user group and completes participation in the user group. When the user logs into the subdomain of the user group, the portal screen is displayed on the display unit 25 . The portal screen corresponds to the top page in the subdomain of the user group.

FIG. 2 is a diagram showing an example of a portal screen. Various images are displayed on the portal screen SC1 for the user to share information within the user group. For example, the portal screen SC1 includes a display area A10 showing a list of applications available to the user and a display area A11 showing a list of spaces in which the user is participating. In this embodiment, of the functions available in groupware, an information sharing function using an application and an information sharing function using a space will be described.

An app is a tool for supporting a user's business. An application can be said to be a business system tailored to the user's work. In this embodiment, an application having functions similar to those of spreadsheet software is taken as an example, but various known types of applications can be used. For example, an application having functions similar to word processing software, an application having functions similar to image editing software, or an application having functions similar to presentation software may be provided.

The user can use an application prepared in advance by groupware, or create an application by himself/herself. Users can also use apps created by other users or other user groups. For example, an application includes a program portion for executing some processing and an actual data portion viewed by the user. The user can specify arbitrary calculation formulas and codes for the program part. The data format of the application may be any format as long as it conforms to the functions of the application.

A space is a place where users communicate with each other. Space can also be said to be a function used for team-based communication. In the space, participants can discuss and share information with each other. Any number of spaces can be created in a user group. Space participants may be all members of a user group or part of a user group. A user does not have to participate in a space. Even if a user does not participate in the space, if he or she receives an invitation from the user group, the information in the user group can be viewed.

For example, if a company corresponds to a user group, a space is a department or team of this company. Spaces may be further divided within a certain department or team, or spaces may exist across multiple departments or teams. Furthermore, there may be a space for communicating with people outside the company. Arbitrary information is exchanged in the space. In this embodiment, information in the space means information exchanged in the space.

In this embodiment, a case will be described in which only a user who has space creation authority can create a space, but the concept of space creation authority may not exist. For example, a user with space creation privileges specifies the space participants. Any user can be designated as a participant. It is also possible to add or remove participants after creating the space. In this embodiment, a case where there are three types of spaces, a public space, a private space, and a guest space, will be taken as an example.

A public space is a space in which all users can participate. In this embodiment, a case will be described where participants in a public space of a certain user group are designated by this user group, but they may be designated by users of another user group. That is, participants in a public space of a certain user group may be users who have not been invited to this user group. Information in the public space can be viewed not only by participants but also by non-participants. Information in a public space of one user group may be viewable by users of other user groups.

A private space is a space in which all users can participate. All users can designate participants in a closed space of a certain user group. In these respects, private spaces are similar to public spaces. However, information in the private space can only be viewed by participants in the private space. In this respect, private spaces differ from public spaces. Even if a user is invited to a user group, he or she cannot view information in a non-participating private space. When the user is added as a participant in the private space, the information in the private space can be browsed.

A guest space is a space in which users who do not belong to a user group can participate. In this respect, guest spaces differ from public and private spaces. Even a user not invited to any user group can be designated as a participant in the guest space. Information in the guest space can only be viewed by participants in the guest space. Even if a user is invited to a user group, he/she cannot view information in the guest space that he/she is not participating in. The flow of invitations to guest spaces may be similar to the flow of invitations to user groups. An invitation mail including the URL of the guest space is sent to the person invited to the guest space. Hereinafter, a person invited to the guest space is referred to as a guest user. A guest user creates a guest user ID and participates in the guest space. A guest user can browse only the information in the guest space in which he or she has participated. Guest users cannot view information in public spaces, private spaces, and uninvited guest spaces. Guest users cannot view information in guest spaces that they have been invited to but have not yet joined.

Henceforth, when the public space, the private space, and the guest space are not particularly distinguished, they are simply referred to as spaces. The application described above can be placed in the space. Placing an app in a space means associating the space with the app. Hereinafter, an application placed in a space will be referred to as an in-space application. The actual data portion of an in-space app in a space corresponds to the information exchanged in this space.

In this embodiment, information sharing outside the space is also possible. For this reason, there are also apps that are placed outside the space. Hereinafter, an application placed outside the space will be referred to as an application outside the space. When there is no particular distinction between in-space apps and out-of-space apps, simply refer to them as apps. Off-space apps are apps that are not associated with any space. When an out-of-space app for a user group is updated, a notification is sent to all or some users of this user group.

FIG. 3 is a diagram showing an example of a space created within a user group. For example, user group G1 is a company in which 10 users U1 to U10 work. In the example of FIG. 3, public spaces SP1 and SP2, private spaces SP3 and SP4, and guest spaces SP5 and SP6 are created for the user group G1. Users U1-U10 can also communicate outside of these spaces.

For example, users U1 to U5 participate in public space SP1. Users U6 to U10 who have not participated in the public space SP1 and other users can also view the information in the public space SP1. Users U6 to U10 participate in public space SP2. Users U1 to U5 who do not participate in the public space SP2 and other users can also view the information in the public space SP2.

Users U1 and U2 participate in the private space SP3. The users U3 to U10 who have not participated in the closed space SP3 and other users cannot browse the information in the closed space SP3. Users U1, U3, and U4 participate in the private space SP4. The users U2, U5 to U10 and other users who have not participated in the private space SP4 cannot browse the information in the private space SP4.

Users U1, U4, U5, U9, U10 and guest users U11, U12 participate in the guest space SP5. Users U2, U3, U6 to U8 and other users who have not participated in guest space SP5 cannot view information in guest space SP5. Users U1, U6, U7 and guest users U13, U14 participate in the guest space SP6. Users U2-U5, U8-U10 and other users who have not participated in guest space SP6 cannot browse the information of guest space SP6.

In addition to the example of FIG. 3, there are various user groups and spaces in the mobile app system S. Portal screen SC1 in FIG. 2 is a screen corresponding to user U1 of user group G1 in FIG. A list of applications and spaces accessible to the user may be displayed in the display areas A10 and A11 of the portal screen SC1. A private space that the user cannot access may not be displayed in the display area A11. The user can select any space from the display area A11. For example, when the user selects the public space SP1 from the display area A11, the display unit 25 displays a space screen for viewing information in the public space SP1.

FIG. 4 is a diagram showing an example of the space screen. The space screen SC2 includes a display area A20 showing a list of in-space applications, and a display area A21 showing a list of space participants and followed users. The space screen SC2 can also display information exchanged in threads created in the public space SP1 and various other information. The user can select any in-space application from the display area A20. When the user selects an in-space application from the display area A20, the display unit 25 displays an application screen for viewing the actual data portion of the selected in-space application.

FIG. 5 is a diagram showing an example of an application screen. In the example of FIG. 5, the actual data portion of the in-space application is displayed on the application screen SC3 in tabular form. In the present embodiment, access rights are set for in-space applications. A user can perform operations according to his or her own access rights. Similarly, access rights are set for apps outside the space. In the case of a table format as shown in FIG. 5, access rights may be set for each record or field.

App access rights are one of the app settings. Application settings themselves can be publicly known settings, and various settings other than access rights are possible. The user can specify application settings from the application screen SC3. For example, when the icon I30 of the application screen SC3 is selected, the display unit 25 displays an application setting screen for setting the application displayed on the application screen SC3.

FIG. 6 is a diagram showing an example of an application setting screen. As in the application setting screen SC4, various settings can be made for the application. Here, among the settings of the application, the access rights of the application will be explained. For example, when the user selects "app" in "access right" on the app setting screen SC4, the display unit 25 displays an access right setting screen for setting the access right of the selected app.

FIG. 7 is a diagram showing an example of an access right setting screen. On the access right setting screen SC5, it is possible to specify or restrict users who can use the selected application, and change the application group to which the application belongs, which will be described later. In the present embodiment, as an example of the access rights of an application, there are an access right according to the location of the application and an access right specific to the application.

The access right according to the location of the application is the access right common to the location of the application. For example, if it is a private space, only participants can access the application, so that only the participants in the private space can access it corresponds to the access right according to the location of the private space. Since anyone can access the application in the public space or outside the space, the fact that anyone can access the application corresponds to the access right according to the arrangement location of the public space or outside the space. In this embodiment, the application group in FIG. 7 also corresponds to one of the access rights according to the location of the application.

An application group is a group for collectively managing access rights of multiple applications. By using an application group, it is possible to set application access rights to multiple applications at once. By using an application group, in addition to access rights, it is also possible to collectively manage rights such as app creation rights and management rights. Applications belonging to a certain application group have the same access right settings.

An application belongs to any one application group. In this embodiment, when an application is created, it belongs to an application group called public by default. For example, an application whose application group is public can be published to users other than the creator of the application (ie, all users). Any application group other than public can be created. In this embodiment, it is assumed that special authority is required to create an application group. You can also change the default app group from public to any other app group.

In this embodiment, it is assumed that an in-space application belongs to public and cannot change the application group. However, even if they are the same public, the users who can access the in-space app in a public space and the in-space app in a private space are different. Since the public space is viewable by all users, the public of the in-space app in the public space means that all users can access it. A private space can only be viewed by participants, so public in-space apps in a private space means that only participants can access it. In-space apps in private spaces are not accessible to all users, even if the app group is public.

The application group outside the space can be changed from the public application group to another application group. Other application groups may be private, accessible only by the creator of the application, or a unique application group created by a user who has permission to create an application group. A unique application group can permit or prohibit operations such as creation, management, use, and deletion of applications belonging to this application group for users, user groups, and groups within the user group. In the example of FIG. 7, the application group cannot be changed because it is an in-space application, but if it is an out-of-space application, it is possible to change the application group from the access right setting screen SC5.

App-specific permissions are permissions specified for individual apps. Access rights for one app are separate from access rights for other apps. Therefore, even if the applications belong to the same application group, the application-specific access rights are independent of each other. In the example of FIG. 7, it is possible to set application-specific access rights from the input form F50. For example, access rights can be set for each user, organization, or group. Access rights can include arbitrary items, such as viewing records, adding records, editing records, deleting records, managing apps, reading files, and writing files.

In this embodiment, it is also possible to change the location of the application from the application setting screen SC4 in FIG. For example, when "move application" is selected from the application setting screen SC4, a dialog for moving the application is displayed.

FIG. 8 is a diagram showing an example of the application setting screen SC4 on which a dialog is displayed. As shown in FIG. 8, the dialog D40 includes a button B41 for specifying the space to which the application should be moved, an input form F42 for searching the space to which the application should be moved, and an input form F42 for moving the application out of the space. button B43 is displayed. When the user moves an in-space application in a certain space to another space, the user selects the button B41 and then searches and designates the destination space from the input form F42.

The user selects the button B43 when moving the in-space application out of the space. FIG. 8 shows a case where the selected application is an in-space application, but if an out-of-space application is selected, the button B43 may not be displayed. In this embodiment, movement of applications within the guest space is prohibited. Also, specifying a guest space as a destination is prohibited. When the user selects the destination of the application from the dialog D40, the application can be moved after a notice is displayed. When the app is moved, access rights are set according to the destination.

FIG. 9 is a diagram illustrating an example of setting access rights before and after moving an application. The example of FIG. 9 shows a case where the application in the public space SP1 is moved to the private space SP4. As shown in FIG. 9, the application group remains public before and after the move. Public of space SP4 means that it is accessible only to users U1, U3 and U4 who are participants. On the other hand, application-specific access rights do not change before and after movement. When actually controlling access to an application, the access right determined by the application group and the access right specific to the application are logically multiplied.

In the example of FIG. 9, the access right corresponding to the destination private space SP4 is set such that only users U1, U3, and U4 can access. As application-specific access rights, settings for users U1 and U2 and settings for Everyone common to all users are set. Since user U1's settings exist in both, the app-specific user U1 settings are applied to user U1. Everyone settings are applied to users U3 and U4. Although user U2 has access rights specific to the application, he cannot access the application because he is not a participant in the private space SP4. Similarly, other users are Everyone, but are not participants in the private space SP4, and cannot access the app.

As described above, in the application moving system S of the present embodiment, an access right corresponding to a location and an access right unique to each application are set for each application. Applications placed outside the guest space can be moved to any location other than the guest space. When an app is moved, permissions are set according to the destination, but app-specific permissions remain unchanged. By adopting such a configuration, the user's work is reduced when the application is moved. Hereinafter, the details of the application transfer system S will be described.

[3. Functions Realized by Application Transfer System]
FIG. 10 is a functional block diagram showing functions realized by the application transfer system S. As shown in FIG. In this embodiment, a case where the main functions are realized by the server 10 will be described. The data storage unit 100 is realized mainly by the storage unit 12 . Other functions are realized mainly by the control unit 11 .

[Data storage part]
The data storage unit 100 is realized mainly by the storage unit 12 . The data storage unit 100 stores data necessary for functions provided by groupware. In this embodiment, the user group database DB1 and the application database DB2 will be described as examples of this data.

FIG. 11 is a diagram showing an example of data storage in the user group database DB1. The user group database DB1 is a database that stores information on user groups. For example, the user group database DB1 stores user group IDs, user group names, portal URLs, user IDs, passwords, space IDs, space names, space types, and participants. When a new user group is created, a record corresponding to this user group is newly created, and information such as the user group ID of this user group is stored.

A user group ID is an ID that can identify a user group. A user group ID of a certain user group is associated with a user ID that can identify a user belonging to this user group. A user group ID of a certain user group is associated with a space ID that can identify a space created for this user group. The space type is information that can identify the type of space. In this embodiment, the space type indicates one of three types: public space, private space, or guest space. The space ID of a space is associated with the user IDs of the participants of this space. Note that the guest space may be separated from the user group as data.

FIG. 12 is a diagram showing a data storage example of the application database DB2. The application database DB2 is a database that stores information on applications. For example, the application database DB2 stores user group IDs, application IDs, application names, location information, actual data portions of applications, and application setting information. When a new application is created, a new record corresponding to this application is created, and information such as the user group ID and application ID of the user group in which this application was created is stored.

The placement location information is information that can identify the placement location of the application. If the application is an in-space application, the space ID is stored as the placement location information. If the application is outside the space, the location information indicating that the application is outside the space is stored. Placement information may not be stored for applications outside the space. In this case, the fact that the location information is not stored means that the application is outside the space.

The application setting information is information indicating the setting contents of the application. In this embodiment, the application setting information includes application group information that can identify an application group, and unique information that can identify an access right specific to an application. In this embodiment, the application setting information of the in-space application includes application group information indicating that the in-space application is public, and unique information set for this in-space application. The application setting information of the out-of-space application includes application group information indicating a public or other application group, and unique information set for this out-of-space application. The unique information indicates access rights unique to the application described with reference to FIG.

Note that the data stored in the data storage unit 100 is not limited to the above examples. The data storage unit 100 may store data necessary for the functions provided by the groupware. For example, the data storage unit 100 may store a user database in which information about individual users is stored. The data storage unit 100 may store a database in which actual data of information shared within individual user groups or spaces is stored. Alternatively, for example, the data storage unit 100 may store authority settings defined in individual application groups.

[Placement part]
The arranging unit 101 arranges the application inside or outside a space in which at least one member of a user group capable of sharing information participates. For example, in the application database DB2, setting the space ID of a certain space as placement location information associated with the application ID of a certain application corresponds to arranging this application in this space. In the application database DB2, setting information indicating outside the space as the placement location information associated with the application ID of a certain application corresponds to placing the application outside the space.

For example, when an application is created from the space screen SC2 of a certain space, the arrangement unit 101 arranges this application in this space as an in-space application. When an application is created from the portal screen SC1, the arrangement unit 101 arranges this application outside the space as an out-of-space application. If the placement location is specified when creating the application, the placement unit 101 may place the created application in the specified placement location.

[First setting part]
The first setting unit 102 sets authority according to the location of the application to the application. This authority can be any authority related to the app and is not limited to access rights. For example, it may be application management authority, movement authority, deletion authority, setting change authority, or a combination thereof. It is assumed that the relationship between the placement location and the authority corresponding to this placement location is defined in the data storage unit 100 . The first setting unit 102 sets the authority of a certain application so that the authority associated with the location of the application is set.

For example, in the case of an intra-space application placed in a certain private space, the first setting unit 102 sets access rights for this intra-space application so that only participants in this private space have access rights. . If it is an in-space application placed in a certain guest space, the first setting unit 102 sets access rights for this in-space application so that only participants in this guest space have access rights.

For example, in the case of an in-space application placed in a certain public space, the first setting unit 102 sets access rights for this in-space application so that all users have access rights. If it is an out-of-space app placed outside the space, the first setting unit 102 sets the access right of this out-of-space app so that it has the access right defined in the app group to which this out-of-space app belongs.

In the present embodiment, the first setting unit 102 sets permissions specific to the application to the application. Even if the application is moved by the moving unit 108, which will be described later, the setting of authority specific to the application is maintained. That is, permissions specific to an app do not change when the app is moved. App-specific permissions are changed by user operations.

[Determination part]
The determination unit 103 determines whether the user who instructs the movement of the application has application management authority and whether or not the user has application creation authority at the destination of the application movement. The user who instructs the movement of the application is the user who displayed the application setting screen SC4. The application management authority is permission to perform actions such as changing application settings and deleting the application. App creation authority is permission to create apps inside or outside the space. Users, organizations, etc. who have application management authority and application creation authority are defined in application groups. For example, in the case of an in-space application, the determination unit 103 determines whether or not the user who instructs the movement of the application has such authority based on the management authority and creation authority associated with the public application group. .

For example, when the source of movement of the application is within a space, the determination unit 103 may further determine whether or not the user who instructs the movement of the application has management authority for the space. Space management authority permits actions such as space setting change and deletion. Users, organizations, and the like having space management authority are defined in the user group database DB1 and the like. For example, the determination unit 103 refers to the application database DB2 and identifies the current location of the application to be set on the application setting screen SC4. If the specified placement location is within the space, the determination unit 103 refers to the user group database DB1 and determines whether or not the user instructing the movement of the application has management authority for the space. do.

[Restrictions]
The restriction unit 104 restricts movement of applications based on predetermined conditions. Any condition can be set as this condition as long as it is a condition for determining whether or not to permit movement of the application. For example, the restriction unit 104 restricts movement of the application with respect to the space set so that shared information is separated. Separation of information means that the disclosure range of information is different from other places. In this embodiment, the guest space corresponds to one example of this space. Information in the guest space can be viewed only by participants in the guest space, even if the user is invited to the user group.

For example, the space of this embodiment includes a guest space in which guest users who do not belong to a user group can participate. A restriction unit 104 restricts movement of apps between the guest space and other spaces. Moving an app between a guest space and another space is at least one of moving an app from a guest space to another space or moving an app from another space to a guest space.

For example, the restricting unit 104 restricts movement of an in-space application if the current location of the in-space application is the guest space. A restriction unit 104 restricts movement of an application so that the application does not move to the guest space. Any method can be used to restrict the movement of apps. The item can be selected but the dialog D40 is not displayed, the dialog D40 is displayed but the button for instructing movement cannot be selected, or the button can be selected but an error occurs afterwards.

Note that any condition other than the condition regarding the guest space can be set as the condition for moving the application. For example, the application itself may be set to enable or disable the change function of the assigned space. In this case, the condition is that the space function of the application is turned on and that the function is turned on as an opt-in setting. In addition, for example, the management authority determined by the determining unit 103 is also one of the conditions. In addition, you must have permissions to create apps in the public app group, you must have permissions to create apps in system administration, and you must be a participant in a private space if the destination space is a private space. In other words, the condition may be that the destination is not the same as the current location.

[Notification part]
The notification unit 105 notifies the reason when movement of the application is restricted. In this embodiment, the moving unit 108 moves the application when a predetermined condition is satisfied. to inform you why the condition of is not met. The reason for this is the content of the condition that was not met. Any method may be used to notify the reason. Display a message indicating the reason when is displayed, display a message indicating the reason in the dialog D40, or display a message indicating the reason on the error screen after the dialog D40. . The reason is not limited to visual notification, and may be auditory notification using sound. Note that the item "move application" may be displayed only when the function to move the application is turned on.

[Movable search unit]
The movable search unit 106 searches for a space in which the application can be moved based on a predetermined condition. For example, the moveability search unit 106 searches for a space in which the application specified as the move target can be moved, and displays the search result in the dialog D40. In this embodiment, the app can be moved in any space other than the guest space. as a movable space. For example, when the user inputs some character string in the input form F42, the movable search unit 106 searches for spaces that include this character string as the space name. A space that does not satisfy the conditions described in the processing of the restriction unit 104 does not hit the search result.

[Reception Department]
The accepting unit 107 accepts designation of a destination by a user who instructs to move the application. In this embodiment, a search is executed by the movable search unit 106, so the receiving unit 107 receives designation of a destination from among the search results of the movable search unit 106 by the user who instructs to move the application. . For example, search results are displayed on the pull-down menu of the input form F42. The user can specify any space from the pull-down menu. The accepting unit 107 accepts designation of one of the search results displayed in the pull-down menu. Various known methods can be used for the method of displaying the search results, and the method is not limited to a pull-down menu.

[moving part]
The moving unit 108 moves the application between the public space and the private space or between inside and outside the space. Moving an application means changing the location of the application. The moving unit 108 moves the application by updating the location information stored in the application database DB2. The moving unit 108 changes the placement location of the application specified as the move target from the current placement location to the destination. In this embodiment, the destination is specified from among the search results of the movable search unit 106, so the move unit 108 moves the application to the destination specified by the user.

Moving the app between the public space and the private space is at least one of moving the app from the public space to the private space and moving the app from the private space to the public space. Moving an app between inside and outside a space is at least one of moving an app from inside the space to outside the space and moving the app from outside the space to inside the space.

For example, when the out-of-space application is in an application group other than public, the moving unit 108 may move the application into the space on condition that the application group of the application is changed to public. If the out-of-space application belongs to an application group other than public, the moving unit 108 does not move the out-of-space application. The moving unit 108 moves the out-of-space application to the space on condition that the out-of-space application belongs to a public application group. The application group must be changed manually by the user before the application outside the space is moved, but it may be changed automatically after some kind of confirmation dialog is displayed.

In this embodiment, the moving unit 108 moves the application based on the determination result of the determining unit 103 . The moving unit 108 does not move the application unless it is determined that the user instructing the movement of the application has the authority to manage the application and that the user has the authority to create the application at the destination of the movement of the application. The moving unit 108 moves the application when it is determined that the user instructing the movement of the application has the authority to manage the application and that the user has the authority to create the application at the destination of the movement of the application.

In the present embodiment, when the application is moved from within a space, it is further determined whether or not the user instructing the movement of the application has management authority for the space. As conditions, there will be at least three conditions. The moving unit 108 does not move the application if at least one of these three conditions is not satisfied. The moving unit 108 moves the application when all of these three conditions are satisfied. If the other conditions described above also exist, the moving unit 108 moves the application, in principle, when all the conditions are satisfied. In principle, the moving unit 108 does not move the application if some of the conditions are not satisfied.

Note that the moving unit 108 can also move an application between a plurality of private spaces. Moving an app between multiple private spaces is moving an app from one private space to another private space. The moving unit 108 can also move apps between multiple public spaces.

[Second setting part]
The second setting unit 109 sets authority for the application moved by the moving unit 108 according to the destination of the application. The meaning of authority is as explained in the first setting unit 102 . For example, if the destination is a private space, the second setting unit 109 sets access rights for the in-space application that has moved to the private space so that only participants in this private space have access rights. do. If the destination is a public space, the second setting unit 109 sets the access rights of the in-space applications that have moved to the public space so that all users have access rights. If the destination is outside the space, the second setting unit 109 sets the access rights of the out-of-space application such that the access right is defined for the app group to which the out-of-space application belongs. Note that when the application is moved between a plurality of closed spaces, the second setting unit 109 sets access rights so that the participant in the closed space to which the application is moved can access.

[Third setting part]
The third setting unit 110 can set authority common to a plurality of applications. In this embodiment, this permission is a permission defined by an app group. This common authority may be authority called by a name other than the application group. For example, the third setting unit 110 sets the in-space application to a public application group indicating that the application can be opened to all users. In the present embodiment, only public application groups are possible for in-space applications, so the third setting unit 110 sets the in-space applications to public. Out-of-space apps also default to the public app group.

For example, the third setting unit 110 sets a public application group or another application group to the out-of-space application. Since an out-of-space application can belong to any application group including public, the third setting unit 110 sets the out-of-space application so that it belongs to an application group specified by a user who has application management authority. . It is assumed that detailed settings for individual application groups are stored in the data storage unit 100 . For example, access rights may be specified for each user or organization as detailed settings for the application group.

[Access control part]
The access control unit 111 controls access to applications based on the authority set for the applications. In the present embodiment, the access control unit 111 accesses the app moved by the moving unit 108 based on a logical product (AND condition) of the authority corresponding to the destination of the movement of the application and the authority specific to the application. Control access. The access control unit 111 permits a user to access an application when the user has authority corresponding to the destination of the application and authority specific to the application. The application control unit does not allow a user to access an application if the user does not have at least one of authority corresponding to the destination of the application and authority specific to the application.

For example, the access control unit 111 controls access to an application whose authority is set by the third setting unit 110, based on the AND of the authority set by the third setting unit 110 and another authority. . The other authority may be authority other than the authority set by the third setting unit 110 , and is the authority set by the first setting unit 102 or the second setting unit 109 . If there is a function for setting authority other than the first setting section 102 and the second setting section 109, the authority set by this function may correspond to other authority. For example, the access control unit 111 permits a user who is permitted access by both the authority set by the third setting unit 110 and another authority to access the application.

[In-space search part]
The in-space search unit 112 searches for the app in the space when the destination of the app is in the space. The in-space search is a search for information in a space. In space search, all or part of the information in the space serves as an index. In the space, other information such as threads are exchanged in addition to the application, so other information is also searched for in the space search. The in-space search unit 112 creates an index for in-space search so that, when the destination of the application is a space, this application is a search target in an in-space search of this space. If the app moves, it will no longer hit the search in the space of the move source. A message to that effect may be displayed when the processing for reflecting the search in the destination space is completed.

For example, the in-space search unit 112 executes an in-space search based on a query input from the "search in space" input form on the space screen SC2 in FIG. The in-space search unit 112 also uses the actual data of the application moved to the space being displayed on the space screen SC2 as an index for in-space search. In this embodiment, there are also a general search performed from the portal screen SC1 in FIG. 2 and an in-app search performed from the application screen SC3 in FIG. A full-text search targets all information within a user group. The in-app search targets the actual data within the app.

[4. Processing Executed in the Application Transfer System]
13 and 14 are flow charts showing an example of processing executed in the application moving system S. FIG. The processes of FIGS. 13 and 14 are implemented by the control units 11 and 21 executing programs stored in the storage units 12 and 22, respectively. It is assumed that the user has received an invitation to some user group when the processes of FIGS. 13 and 14 are executed.

The user terminal 20 accesses the subdomain of the user group to which the user has been invited, and performs login processing with the server 10 based on the user ID and password entered by the user (S1). When the login process is successful, the user terminal 20 causes the display unit 25 to display the portal screen SC1 (S2). The user terminal 20 accepts the user's operation on the portal screen SC1 (S3). Any operation can be performed from the portal screen SC1, but here, an operation to create an application, an operation to select an application in the display area A10, an operation to create a space, or a space in the display area A11 is selected. An operation shall be performed. When the user performs a predetermined logout operation (S3; logout), this process ends.

In S3, when the user performs an operation to create an application (S3; create application), the user terminal 20 executes processing for creating an application with the server 10 (S4). This process itself may be a known process, and the server 10 updates the application database DB2 so that the newly created application is arranged outside the space. In S3, when the user performs an operation to select an application within the display area A10 (S3; application selection), the user terminal 20 executes processing for displaying the application screen SC3 with the server 10 ( S5). In S5, the server 10 refers to the application database DB2, acquires information about the application selected by the user, and generates data for displaying the application screen SC3.

Thereafter, information sharing processing using the application is executed. Here, processing for changing application settings will be described. When the icon I30 is selected, the user terminal 20 performs processing for displaying the application setting screen SC4 with the server 10 (S6). The user terminal 20 accepts the user's operation on the application setting screen SC4 (S7). Any operation can be performed from the application setting screen SC4, but here, an operation to set the access right of the application or an operation to move the application shall be performed.

When an operation to set the access right of the application is performed (S7; access right setting), the user terminal 20 executes a process for displaying the access right setting screen SC5 with the server 10 (S8). . The current settings stored in the application database DB2 are displayed on the access right setting screen SC5. The user terminal 20 accepts the user's operation on the access right setting screen SC5 (S9). Any operation can be performed from the access right setting screen SC5, but here, an operation to change the application group or an operation to set the access right specific to the application is performed. An application in a group can only be public, so an operation to change the application group is not accepted.

When the user performs an operation to change the application group (S9; change application group), the user terminal 20 executes processing for changing the application group with the server 10 (S10). In S10, the server 10 updates the application database DB2 so that the application group specified by the user is set. In S9, when the user performs an operation to set application-specific access rights (S9; unique setting), the user terminal 20 executes processing for setting application-specific access rights with the server 10. (S11). In S11, the server 10 updates the application database DB2 so that the unique access rights specified by the user through the input form F50 are set for the users, organizations, etc. specified by the user through the input form F50.

In S7, when the user performs an operation to move the application (S7; application move), the user terminal 20 executes processing for displaying the dialog D40 with the server 10 (S12). In S12, the server 10 refers to the application database DB2, acquires information such as the location of the application to be moved, and generates data for the dialog D40. The user terminal 20 executes processing for moving the application with the server 10 based on the user's operation on the dialog D40 (S13). In S13, the server 10 updates the application database DB2 so that the application to be moved is moved to the destination specified by the user in the dialog D40.

The server 10 sets access rights according to the destination of the application moved in S14 (S14). In S14, the server 10 updates the application database DB2 so that an application group corresponding to the destination is set. As mentioned earlier, even if it is the same public, if the destination is a private group, it will be set so that only the participants of the private group can access it.

In S3, when the user performs an operation to create a space (S3; create space), the user terminal 20 executes processing for creating a new space with the server 10 (S15). A known process can be used for the process itself for creating a space. In S3, when the user performs an operation to select a space within the display area A11 (S3; space selection), the user terminal 20 executes processing for displaying the space screen SC2 with the server 10 ( S16). In S16, the server 10 refers to the user group database DB1, acquires information about the space specified by the user, and generates data for the space screen SC2.

The user terminal 20 accepts the user's operation on the space screen SC2 (S17). Any operation can be performed from the space screen SC2, but here, an operation to create an in-space application or an operation to select an in-space application is performed. When the user performs an operation to create an in-space application (S17; create application), the user terminal 20 executes processing for creating an application with the server 10 (S18). At S18, the newly created app is placed in the space. In S17, when the user performs an operation to select an in-space application (S17; select application), the process proceeds to S5, and the application screen SC3 is displayed.

According to the application moving system S of the present embodiment, an application that has been moved between a public space and a private space or between inside and outside of a space is set with authority corresponding to the destination of this application. As a result, the authority corresponding to the destination of the movement is automatically set for the application moved between them, so that the user's trouble of manually setting the authority can be reduced. Furthermore, when users manually set permissions, there is a possibility that information may be disclosed to unintended parties due to setting errors. can be prevented. As a result, the risk of leakage of confidential information and the like is reduced, and the security of confidential information and the like is enhanced. In addition, by allowing the application to be moved between arbitrary spaces or outside the space, the trouble of copying the application and creating a new one can be eliminated.

Further, in the application movement system S, even if the application is moved, the setting of authority unique to the application is maintained. As a result, it is possible to prevent the information from being disclosed to an unintended person by rewriting the authority unique to the application without permission. As a result, it is possible to prevent confidential information from being leaked and important information from being rewritten by someone else.

In addition, the application movement system S controls access to the application based on the logical product of the authority corresponding to the destination of the application and the authority specific to the application. As a result, users need only be aware of these two permissions without having to set complicated permissions for individual applications, thereby reducing the user's work. In addition, since the logical product of authority narrows the range of disclosure of information, it is possible to more effectively reduce the risk of disclosure of information to an unintended person.

Also, the application transfer system S controls access to an application based on a logical product of authority common to a plurality of applications and other authority. As a result, it is possible to collectively set permissions common to a plurality of applications, thereby reducing the burden on the user who sets permissions for the applications. Furthermore, the security of the application can be ensured by controlling access to the application in consideration of other authorities.

In addition, the application moving system S determines whether the user who instructs the movement of the application has application management authority and whether or not the user has the application creation authority at the destination of the application movement. As a result, it is possible to prevent the application from being moved by an unintended person and the information to be disclosed. As a result, it is possible to prevent confidential information from being leaked and important information from being rewritten by someone else.

Further, when the application is moved from within a space, the application movement system S determines whether the user who instructs the movement of the application has management authority for the space. As a result, it is possible to prevent the application from being moved by an unintended person and the information to be disclosed. In particular, applications placed in private spaces often have high confidentiality, so it is possible to prevent such information from being leaked or important information from being rewritten by someone else.

Also, the application movement system S restricts the movement of applications between the guest space and other spaces. As a result, it is possible to prevent the application from being disclosed to an unintended person and to prevent the application from being taken out by an unintended person. In particular, since the guest space is a space that can be accessed by outsiders of the user group, it is possible to more effectively reduce the risk of information being disclosed to such a space due to setting errors or the like.

In addition, when the conditions for moving the application are not satisfied, the application moving system S notifies the user instructing the movement of the application of the reason. This makes it easier for the user to understand the reason why the application cannot be moved, thereby enhancing the user's convenience.

In addition, the application moving system S accepts designation of a movement destination by the user who gives an instruction to move the application from among the search results of spaces to which the application can be moved. This makes it easier for the user to grasp the space in which the application can be moved, thereby enhancing the user's convenience.

In addition, when the destination of the application is within the space, the application moving system S makes the application a search target within the space. Accordingly, after the application is moved, the information of the application can be searched in the destination space, so that information can be shared more quickly in the destination space.

[5. Modification]
Note that the present disclosure is not limited to the embodiments described above. Modifications can be made as appropriate without departing from the gist of the present disclosure.

For example, the application movement system S may be capable of moving applications between multiple spaces regardless of the type of space. In this case, the moving unit 108 moves the application between multiple spaces. For example, the moving unit 108 moves an application from one public space to another public space. In this case as well, the first setting unit 102 may set access rights to the app according to the public space of the destination. The application moving system S of the modified example may have a placement unit 101 , a first setting unit 102 , a moving unit 108 , a second setting unit 109 , and an intra-space search unit 112 . These details are as described in the embodiment.

According to the application movement system S of the modified example, when the movement destination of an application is within a space, the application is set as a search target within the space. Accordingly, after the application is moved, the information of the application can be searched in the destination space, so that information can be shared more quickly in the destination space.

For example, in the embodiments, the case where the app move source is the guest space and the app move destination is the guest space, and the case where the move of the app is prohibited have been described. Movement may be permitted. For example, the type of space is not limited to the example of the embodiment, and any type of space may exist. Any authority may be set according to the location of the application. For example, a unique authority may be set for each public space, or a unique authority may be set for each private space. In addition, for example, unique authority may be set for each guest space.

For example, each function described above may be realized by any computer in the application moving system S. FIG. For example, the functions described as being implemented by the server 10 may be implemented by the user terminal 20 . The functions described as being implemented by the user terminal 20 may be implemented by the server 10 . Each function may be shared by multiple computers. Each function may be implemented by one computer.

S application mobile system, N network, 10 server, 11, 21 control unit, 12, 22 storage unit, 13, 23 communication unit, 20 user terminal, 24 operation unit, 25 display unit, 100 data storage unit, 101 placement unit, 102 first setting unit 103 determination unit 104 restriction unit 105 notification unit 106 movable search unit 107 reception unit 108 movement unit 109 second setting unit 110 access control unit 111 in-space search unit A10 , A11, A20, A21 display area, D40 dialog, DB1 user group database, DB2 application database, I30 icon, SC1 portal screen SC2 space screen, SC3 application screen, SC4 application setting screen, SC4 application setting screen, SC5 access right setting screen .

Claims (6)

It is possible to configure the group associated with a plurality of spaces that are places where the users participate in order to share information among users belonging to the group, and the group is based on user identification information of each of the plurality of users. arranging means for arranging an application in a first space of the plurality of spaces in a service capable of restricting access to
a first setting means for setting authority according to the first space to the application;
moving means for moving the app from the first space to a second space among the plurality of spaces;
a second setting means for setting authority according to the second space to the application moved to the second space;
App moving system including. the moving means moves the app from the first space in the group to outside the first space;
The second setting means sets authority according to a destination of the application to the application that has been moved outside the first space.
The application moving system according to claim 1. The application moving system further includes access restriction means for performing the access restriction based on user identification information of users participating in the space, which is associated with the space identification information of each of the plurality of spaces.
The application moving system according to claim 1 or 2. The application moving system further includes search means for making the application moved to the second space a search target in the second space,
The application moving system according to any one of claims 1 to 3. the computer
It is possible to configure the group associated with a plurality of spaces that are places where the users participate in order to share information among users belonging to the group, and the group is based on user identification information of each of the plurality of users. a placement step of placing an app in a first space among the plurality of spaces in a service capable of restricting access to
a first setting step of setting authority according to the first space to the application;
a moving step of moving the app from the first space to a second space of the plurality of spaces;
a second setting step of setting authority according to the second space to the application moved to the second space;
How to move the app to run. It is possible to configure the group associated with a plurality of spaces that are places where the users participate in order to share information among users belonging to the group, and the group is based on user identification information of each of the plurality of users. arrangement means for arranging an application in a first space among the plurality of spaces in a service capable of restricting access to
a first setting means for setting authority according to the first space to the application;
moving means for moving the app from the first space to a second space among the plurality of spaces;
a second setting means for setting authority according to the second space to the application moved to the second space;
A program that allows a computer to function as a

Images