Operating authority setting apparatus and program

Abstract

To reduce the workload of setting authority for information sharing within a community.SOLUTION: An operating authority setting apparatus comprises: a member registration unit for registering members to a team, which is a group of members to which the same operating authority is given; and an authority setting unit for setting operation authority of the members registered to the team by assigning an authority group selected from a plurality of authority groups to the team based on an authority table that the authority groups in which the operation authority is defined for each type of operation related to information shared by a plurality of members are predefined for the plurality of authority groups in which operation authority granting patterns for the types of operations differ from one another.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an operation authority setting device and a program. [Background technology]

[0002] Conventionally, a technique for setting detailed access restrictions for a plurality of users has been disclosed (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] In recent years, computer systems for sharing information within a predetermined community have been provided, and in such computer systems, it is preferable to be able to reduce the workload of setting permissions for each user. [Means for solving the problem]

[0005] One embodiment of the present invention is an operation authority setting device that includes: a member registration unit that registers members into a team, which is a group of members that have been granted the same operation authority; and an authority setting unit that sets the operation authority of the members registered in the team by assigning to the team an authority group selected from a plurality of authority groups, in which operation authority is defined for each type of operation related to information shared by a plurality of members, based on an authority table that is pre-defined for a plurality of authority groups, each of which has a different pattern of granting operation authority for each type of operation.

[0006] One embodiment of the present invention is a program for causing a computer to perform the following steps: registering members into a team, which is a group of members who have been given the same operating authority; and assigning an authority group to the team, the authority group having operating authority defined for each type of operation related to information shared by multiple members, selected from a plurality of authority groups based on an authority table predefined for the plurality of authority groups, each of which has different patterns of granting operating authority for each type of operation. This sets the operating authority for the members registered in the team. [Effects of the Invention]

[0007] According to the present invention, it is possible to provide an operation authority setting device and a program that can reduce the workload of setting authority for information sharing within a community. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of the configuration of a neighborhood information sharing system according to an embodiment of the present invention. [Figure 2] FIG. 10 is a diagram showing an example of an information exchange screen displayed on the terminal device of the present embodiment. [Figure 3] FIG. 10 is a diagram illustrating an example of a notification screen displayed on the terminal device of the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of an authority setting information database according to the present embodiment. [Figure 5] FIG. 2 is a diagram illustrating an example of a team information database according to the present embodiment. [Figure 6] FIG. 2 is a diagram illustrating an example of functions of the operation authority setting device according to the present embodiment. [Figure 7] FIG. 2 is a diagram showing an example of the flow of operations of the neighborhood information sharing system of this embodiment. [Figure 8] FIG. 10 is a diagram showing a state in which a new team is registered in the team information database of the present embodiment. [Figure 9]FIG. 10 is a diagram showing a state in which authority patterns are set for teams in the team information database of the present embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a user addition screen according to the present embodiment. [Figure 11] FIG. 10 is a diagram showing an example of a situation in which a user belongs to multiple teams in the team information database of the present embodiment. [Figure 12] FIG. 10 is a diagram showing a state in which users are registered in a team in the team information database of the present embodiment. [Figure 13] FIG. 10 is a diagram illustrating an example of a member list screen according to the present embodiment. [Figure 14] A diagram showing an example of the flow of user registration and deletion when the position of chairman of a management association is handed over. [Figure 15] A figure showing another example of the flow of user registration and deletion when the position of chairman of a management association is handed over. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. 1 is a diagram showing an example of the configuration of a neighborhood information sharing system 1 according to this embodiment. The neighborhood information sharing system 1 according to this embodiment is a system for sharing information between residents in a specific community, such as an apartment complex, housing complex, neighborhood association, town association, or shopping district, and between residents and people who support the residents.

[0010] The aforementioned housing complex refers to an area that includes multiple detached houses or multiple apartment buildings, and is connected to the residents by facilities that are jointly managed by the residents, operated by a common management company, etc. For example, a housing complex is a community within a housing complex where multiple apartment buildings are located, or a community within an area where multiple detached houses are located on land developed by a common developer.

[0011] In the following description, the above-mentioned predetermined community will also be referred to as a "neighborhood." The residents of the predetermined community and the people who support the residents will also be collectively referred to as "neighbors."

[0012] For example, neighbors may include residents and building owners in a given community, caretakers who assist with various tasks and administrative procedures within a given community, management company personnel, and personnel from businesses that sell, repair, and replace equipment and consumables. "Various tasks" include, for example, cleaning the neighborhood, repairing equipment, replacing consumables, etc. "Various administrative procedures" also include, for example, collecting administrative fees, participation fees, membership fees, etc., settling expenses, and submitting documents to local governments and companies.

[0013] Neighbors can exchange information with each other by registering in advance as users in the neighborhood information sharing system 1. Neighbors registered in the neighborhood information sharing system 1 are also called users of the neighborhood information sharing system 1 (or simply users).

[0014] Users here come from a variety of backgrounds. For example, in addition to residents, users include the chairman and directors of the management association of an apartment complex, personnel from a management company entrusted with the management of the board of directors, caretakers who perform work at the request of the board of directors, personnel from companies that supply consumables such as lighting fixtures, store operators in the surrounding area, hospital personnel, government personnel, and school personnel. Among these users, there is information that should be shared based on their position and information that should not be shared (or that users do not want to share) based on their position. Therefore, when sharing information managed in the neighborhood information sharing system 1 between users, it is preferable to be able to set information sharing authority for each user's position. On the other hand, there are a wide variety of combinations of information sharing permission settings. In particular, when each user is assigned various roles, the combinations of information sharing permission settings become extremely complicated. Setting permissions for each user from among the many combinations of information sharing permission settings becomes a cumbersome task.

[0015] Therefore, the neighborhood information sharing system 1 of this embodiment aims to reduce the workload by creating teams for each user's position and setting information sharing permissions on a team-by-team basis, and by providing a system in which multiple information sharing permission setting patterns are prepared in advance and can be selected.

[0016] The neighborhood information sharing system 1 of this embodiment is prepared for each community (i.e., neighborhood). That is, there are as many neighborhood information sharing systems 1 as there are communities. Below, a specific configuration example of the neighborhood information sharing system 1 used in a specific community (i.e., a predetermined community) among multiple communities will be described.

[0017] [Configuration example of a neighborhood information sharing system] The neighborhood information sharing system 1 includes an operation authority setting device 10, a terminal device 20, and a server device 30. The operation authority setting device 10, the terminal device 20, and the server device 30 are connected to each other via a network NT such as the Internet.

[0018] The terminal device 20 is, for example, a smartphone, a tablet, or a personal computer, and is a device used by a user. The terminal device 20 is equipped with a display unit such as a liquid crystal display and an operation unit such as a touch panel (neither of which are shown), and displays information to the user and accepts user operations.

[0019] FIG. 2 is a diagram showing an example of an information exchange screen P1 displayed on the terminal device 20 of this embodiment. The information exchange screen P1 is a screen used for exchanging information between users. The information exchange screen P1 displays an information exchange tab P11 and a post reply icon P12. The information exchange tab P11 is a so-called tab image for selecting the display of the information exchange screen P1 or the display of another screen. When a user taps the information exchange tab P11, the terminal device 20 displays the information exchange screen P1. The content displayed on the information exchange screen P1 is also referred to as posted information (or simply, a post). The post reply icon P12 is an operation image for a user to reply to a post. When a user taps the post reply icon P12, the terminal device 20 displays a reply input screen (not shown). That is, the information exchange screen P1 is a screen for two-way information sharing between users.

[0020] FIG. 3 is a diagram showing an example of a notification screen P2 displayed on the terminal device 20 of this embodiment. The notification screen P2 is a screen used for notifying the user. The notification screen P2 displays a notification tab P21 and a "cannot post" icon P22. The notification tab P21 is a so-called tab image for selecting whether to display the notification screen P2 or another screen. When the user taps the notification tab P21, the terminal device 20 displays the notification screen P2. The content displayed on the notification screen P2 is also referred to as notification information (or simply, a notification). The "cannot post" icon P22 is an image indicating that the user cannot reply to the notification. In other words, the user cannot operate the "cannot post" icon P22 (or, even if the user operates it, no reply action is performed). That is, the notice screen P2 is a screen for one-way information sharing from one user to another user.

[0021] Returning to FIG. 1, the server device 30 is configured as a so-called cloud server system, and stores various programs and data used by the neighborhood information sharing system 1. The server device 30 of this embodiment includes a user data database 31, an authority setting information database 32, and a team information database 33. The user data database 31 is information for users to access the neighborhood information sharing system 1, and includes registered user identification information (for example, account ID), name (or nickname), contact information, and the like.

[0022] The authority setting information database 32 is information defined in advance by the provider of the neighborhood information sharing system 1. In the following description, the authority setting information database 32 is also referred to as an authority table. An example of the authority setting information database 32 (authority table) will be described with reference to FIG. 4.

[0023] 4 is a diagram showing an example of the authority setting information database 32 of this embodiment. The authority setting information database 32 is a table in which the vertical axis defines the types of operations related to information shared by multiple members, and the horizontal axis defines the patterns of granting operation authority for each authority group.

[0024] [Type of information shared] Information shared by multiple members includes information posted on the information exchange screen P1 and the notice screen P2 described above. In the case of dwellings, shops, etc., the building owner (e.g., the person who holds ownership or leasehold rights) may be different from the resident or user (e.g., the person who holds tenancy rights). For example, if a given community (i.e., neighborhood) is a multi-family housing complex such as an apartment building, the condominium owner and the resident may be different. In this way, when the owner and resident of a certain house are different, there may be information that can be viewed by both the owner and the resident, and information that can be viewed by the owner but not the resident. For example, it is preferable that notices of changes to the cleaning schedule within the building be accessible to both the owner and the resident. On the other hand, there are cases where it is preferable that documents regarding the details and costs of major building repairs be accessible only to the homeowner, and not to the resident.

[0025] In other words, the information referred to here is information that can be viewed by the owners and residents of the apartment complex or the homes in the apartment complex. The information includes first information that can be viewed by both the owner and the residents, and second information that can be viewed by the owner but not the residents.

[0026] The division of teams into owners and residents is an example and is not limiting. For example, within an apartment complex, teams may be divided into those who participate in the neighborhood association and those who do not. In this example, there are a team of apartment complex residents and a team of neighborhood association participants. In this case, the first information may be information that can be viewed by all members who belong to a predetermined team (for example, a team of residents of an apartment complex). The second information may be information that can be viewed by members who belong to some of the teams (for example, a team of residents of a neighborhood association) among the members of the predetermined team (for example, a team of residents of an apartment complex), but cannot be viewed by members who do not belong to some of the teams. That is, the information includes first information that can be viewed by all members belonging to a predetermined team, and second information that can be viewed by members belonging to some of the predetermined teams among the members belonging to the plurality of teams, but cannot be viewed by members not belonging to some of the teams.

[0027] [Type of actions regarding shared information] The types of operations related to information shared by multiple members include posting, viewing, replying to, rating such as "Like" and deleting posts on the information exchange screen P1 described above. The types of operations may also include uploading and downloading electronic files such as photographs and documents. Further, the types of operations may include creating a team, viewing, editing, and deleting information in a team, registering a user as a member to a team, and deleting a member from a team.

[0028] [Operation permission granting pattern] The authority table contains predetermined patterns of granting operation authority for each type of operation, such as "operation authority for any team," "operation authority for only the team to which the user belongs," and "operation authority for no team." In the authority table, operation authority is defined for each of the pre-expected granting patterns, such as pattern A, pattern B, pattern C, etc., as shown in the figure.

[0029] That is, in the authority table, authority groups in which operation authority is defined for each type of operation related to information shared by multiple members are predefined for multiple authority groups each having different patterns of granting operation authority for each type of operation.

[0030] Pattern A shown in the figure is a granting pattern that is assumed to be granted to the privileged administrator team. Pattern A is granted more operation authority (i.e., the range of operations that can be performed) than other granting patterns. In particular, Pattern A has the following:

[0031] In other words, there is a privileged administrator team that is given more operational authority than other teams. The privileged administrator team is given at least one of operational authority for team creation operations and operational authority for team deletion operations.

[0032] [Team Information Database] 5 is a diagram showing an example of the team information database 33 of this embodiment. The team information database 33 is a table in which the team name, operation authority granting pattern, and members are registered for each team. The contents of this team information database 33 are set by the operation authority setting device 10. An example of the functional configuration of the operation authority setting device 10 for setting the team information database 33 will be described below.

[0033] [Functional configuration of the operation authority setting device] Returning to FIG. 1, the operation authority setting device 10 is, for example, a personal computer or a tablet, and is a device used by an administrator of the neighborhood information sharing system 1 (for example, a user with special authority, a privileged administrator). Here, a user with special authority (privileged administrator) is, for example, the chairman or director of the management association if the predetermined community is a management association for an apartment complex or a residential area.

[0034] The operation authority setting device 10 is connected to an operation unit 11 such as a keyboard or a touch panel, and a display unit 12 such as a liquid crystal display. The operation unit 11 accepts operations from the user. The display unit 12 displays information to the user. The functions of the operation authority setting device 10 will be described in detail with reference to FIG.

[0035] 6 is a diagram showing an example of the functions of the operation authority setting device 10 of this embodiment. The operation authority setting device 10 includes a calculation unit 110 and a storage unit 150. The calculation unit 110 includes, for example, a CPU (Central Processing Unit) and provides various functions based on the programs and data stored in the storage unit 150. The storage unit 150 includes, for example, a nonvolatile semiconductor memory or a hard disk drive, and stores programs and data used in the operation of the calculation unit 110.

[0036] The calculation unit 110 includes, as its functional units, an operation reception unit 111, a member registration unit 112, an authority setting unit 113, and a display control unit 114.

[0037] The operation receiving unit 111 receives user operations on the operation unit 11. The operation receiving unit 111 outputs the received operations to the member registration unit 112 and the authority setting unit 113.

[0038] The user's operation may include a team deletion operation. The team deletion operation is an operation for deleting a team from a team group including multiple teams. In this case, the operation receiving unit 111 receives the team deletion operation for deleting a team from a team group including multiple teams.

[0039] The member registration unit 112 registers members into a team, which is a group of members who are given the same operating authority. The authority setting unit 113 assigns an authority group selected from a plurality of authority groups to the team based on the authority table described above, thereby setting operation authority for the members registered in the team. The display control unit 114 controls the image display on the display unit 12 .

[0040] [Neighborhood information sharing system in action] Next, the operation of the neighborhood information sharing system 1 will be described with reference to FIGS. FIG. 7 is a diagram showing an example of the flow of operations of the neighborhood information sharing system 1 of this embodiment.

[0041] [User Registration] (Step S210) When joining a community, for example, a user registers as a user in the neighborhood information sharing system 1. Specifically, the user operates the terminal device 20 to input user data such as their name and contact information. The terminal device 20 transmits the input user data to the server device 30. (Step S310) Based on the user data transmitted from the terminal device 20, the server device 30 creates a record of the user data of the user in the user information database 31.

[0042] [Create a team and select permission pattern] For example, within a community in which a user participates, a team may be formed for a hobby club activity, cleaning activities, or the like. In such a case, a new team can be created in the neighborhood information sharing system 1. In the following example, a case will be described in which a team for cleaning activities is formed within a community, with residents participating as members.

[0043] (Step S110) An administrator of the neighborhood information sharing system 1 (for example, a privileged administrator who has been given the authority to create a team, such as the chairman of the management association; hereinafter, simply referred to as the administrator) creates a team by operating the operation authority setting device 10. When a team is created, the neighborhood information sharing system 1 generates a new record in the team information database 33 and stores the team ID and team name.

[0044] 8 is a diagram showing a state in which a new team is registered in the team information database 33 of this embodiment. The example shown in the figure shows a state in which existing teams (privileged administrator team, resident team) are registered in the team information database 33, and a new cleaning activity team is registered.

[0045] (Step S120) Returning to FIG. 7, the administrator selects the authority of the team created in step S110. As described above, a plurality of authority patterns are registered in advance in the authority setting information database 32. The administrator selects an authority pattern that corresponds to the attributes of the team from the authority patterns registered in the authority setting information database 32. The operation authority setting device 10 associates the authority pattern with the team based on the selection operation of the authority pattern by the administrator. (Step S320) The server device 30 creates team data based on the team creation operation and operation authority selection operation performed by the operation authority setting device 10, and updates the team information database 33.

[0046] 9 is a diagram showing a state in which an authority pattern is set for a team in the team information database 33 of this embodiment. The example shown in the figure shows a state in which pattern B is set for a cleaning activity team that is newly registered in the team information database 33.

[0047] According to the neighborhood information sharing system 1 configured in this manner, the administrator can set authority for a team by selecting a predetermined authority pattern. Therefore, according to the neighborhood information sharing system 1, the administrator's operational effort can be reduced compared to when the administrator has to create an authority pattern corresponding to the team, for example.

[0048] [Member Registration] (Step S130) Returning to FIG. 7, the administrator invites users to register as members of the newly created team (cleaning activity team) to the team.

[0049] 10 is a diagram showing an example of a user addition screen P3 of this embodiment. The administrator inputs information about the user to be invited into the user addition screen P3 displayed on the display unit 12 of the operation authority setting device 10. In this example, the user to be invited has been registered in the user information database 31 in step S210 described above. In this case, the administrator selects users to invite to the team from among the users registered in the user information database 31. The neighborhood information sharing system 1 configured in this way can reduce the effort required to input user data at the stage of inviting a user to a team.

[0050] In addition, on the user addition screen P3 of this embodiment, a user can be invited to join multiple teams at once.

[0051] 11 is a diagram showing an example of a situation in which users belong to multiple teams in the team information database 33 of this embodiment. The example shown in the figure shows a situation in which user A belongs to the resident team, and users B and C belong to two teams, the resident team and the condominium owner team. In other words, this shows an example of a case in which user A is a resident who is not a condominium owner, and users B and C are condominium owners.

[0052] Returning to FIG. 7, the operation authority setting device 10 notifies the terminal device 20 used by the inviting user that the user has been invited to join the team.

[0053] (Step S220) When the terminal device 20 receives the team invitation notification from the operation authority setting device 10, the terminal device 20 displays an operation screen (not shown) requesting the user's approval of the invitation. The user operates the terminal device 20 to approve the invitation to the team. When the terminal device 20 accepts the user's invitation operation, it notifies the server device 30 that the user has approved.

[0054] (Step S330) When the server device 30 receives the notification of approval from the terminal device 20, it registers the user in the team.

[0055] 12 is a diagram showing a state in which users are registered in a team in the team information database 33 of this embodiment. The example shown in the figure shows a state in which two users (e.g., user 06 and user 07) are set as members of the cleaning activity team in the team information database 33.

[0056] 13 is a diagram showing an example of the member list screen P4 of this embodiment. The administrator or the like can check the status of the registration of members to the team by operating the operation authority setting device 10 to display the member list screen P4.

[0057] (Step S230) A user registered as a member of a team can view and post information by operating the terminal device 20 within the scope of the restrictions of the authority pattern set for the team.

[0058] As described above, the neighborhood information sharing system 1 of this embodiment manages operational permissions for users to view and post shared information within a community using teams and permission patterns assigned to the teams. In conventional technology, it is possible to grant users the right to operate, such as viewing or posting, public information, by setting operation rights for each user. However, with such conventional technology, the administrator's operation of setting the rights becomes cumbersome. In particular, in the case where members of a community (e.g., residents) themselves act as administrators and operate the system, as is assumed in the neighborhood information sharing system 1 of this embodiment, the cumbersome operation of setting the rights may result in a situation where the system is not operated properly. The neighborhood information sharing system 1 of this embodiment reduces the effort required for such operations by adopting a method of selecting predefined permission patterns and assigning them to teams, thereby reducing the effort required for setting permissions for individual users.

[0059] [Variations] In the neighborhood information sharing system 1, it is also possible to delete a team registered in the team information database 33 or delete a member registered in a team. When such a team deletion operation or member deletion operation is performed, the display control unit 114 may function as a warning unit that warns the operator if the privileged administrator team (or a member belonging to the privileged administrator team) is deleted by the deletion operation, and if the privileged administrator team (or a member belonging to the privileged administrator team among the users) no longer exists in the team group.

[0060] FIG. 14 is a diagram showing an example of the flow of user registration and deletion when the position of chairman of a management association is handed over. For example, there may be a case where the position of chairman of a management association is handed over. The figure shows a situation where the chairman of the current term is handed over to the chairman of the next term at the board meeting held at the end of the association's term (for example, the last board meeting of the current term). Specifically, in a situation where the chairman of the current term is registered as a member of the privileged administrator team ([A] in the figure), the chairman of the next term is registered as a member of the privileged administrator team ([B] in the figure), and then the chairman of the current term is removed from the privileged administrator team ([C] in the figure). If the flow shown in the diagram is followed, there will be no absence of members of the privileged administrator team.

[0061] FIG. 15 is a diagram showing another example of the flow of user registration and deletion when the position of chairman of a management association is handed over. The figure shows the process of removing the current chairman from the privileged administrator team ([B]) before registering the next chairman as a member of the privileged administrator team ([A]). As shown in the figure, there may be a case where the privileged administrator team (or the members belonging to the privileged administrator team among the users) no longer exists in the group of teams. According to the neighborhood information sharing system 1 configured as described above, it is possible to prevent a user having the authority pattern of a privileged administrator from being absent. In particular, when an event occurs extremely infrequently, such as the handover of the position of chairman of a condominium association once every year to once every few years, it is conceivable that an administrator who is unfamiliar with registering or deleting users from a team may make an erroneous operation. When a resident who is a member of such a community operates the system as an administrator, the neighborhood information sharing system 1 of this embodiment can reduce the operational effort while issuing a warning against possible erroneous operations.

[0062] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and can be appropriately modified without departing from the spirit of the present invention. The configurations described in the above-described embodiments may be combined.

[0063] Each unit included in each device in the above-described embodiments may be realized by dedicated hardware, or may be realized by a memory and a microprocessor.

[0064] In addition, each part of each device may be composed of a memory and a CPU (central processing unit), and the functions of each part of each device may be realized by loading a program into memory and executing it.

[0065] In addition, a program for realizing the functions of each unit of each device may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing by each unit of the control unit. Note that the term "computer system" here includes hardware such as an OS and peripheral devices.

[0066] Furthermore, if a WWW system is used, the "computer system" also includes the homepage provision environment (or display environment). "Computer-readable recording media" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording media" also includes devices that dynamically store programs for a short period of time, such as communication lines used when transmitting programs over networks like the Internet or over communication lines like telephone lines, and devices that store programs for a fixed period of time, such as volatile memory within computer systems that serve as servers or clients. Furthermore, the programs may be programs that implement some of the aforementioned functions, or may be programs that can realize the aforementioned functions in combination with programs already stored in the computer system. [Explanation of symbols]

[0067] 1...neighborhood information sharing system, 10...operation authority setting device, 11...operation unit, 110...calculation unit, 111...operation reception unit, 112...member registration unit, 113...authority setting unit, 114...display control unit, 12...display unit, 150...storage unit, 20...terminal device, 30...server device, 31...user information database, 32...authority setting information database, 33...team information database, NT...network, P1...information exchange screen, P11...information exchange tab, P12...post reply icon, P2...notification screen, P21...notification tab, P22...posting not allowed icon, P3...user addition screen, P4...member list screen

Claims

1. a member registration unit that registers members into a team, which is a group of members that are given the same operating authority; an authority setting unit that sets operation authorities of members registered in the team by assigning an authority group selected from a plurality of authority groups to the team based on an authority table that is predefined for a plurality of authority groups, each authority group having an operation authority defined for each type of operation related to information shared by a plurality of members, and the plurality of authority groups having different patterns of granting operation authorities for the types of operation; An operation authority setting device comprising:

2. The team includes a privileged administrator team that has more operational authority than other teams. The privileged administrator team is given at least one of the authority to create the team and the authority to delete the team. The operation authority setting device according to claim 1 .

3. an operation receiving unit that receives a team deletion operation to delete the team from a team group that includes a plurality of the teams; a warning unit that issues a warning to an operator when the privileged administrator team is deleted by the team deletion operation and the privileged administrator team no longer exists in the group of teams; The operation authority setting device according to claim 2 , further comprising:

4. The information includes first information that can be viewed by all members belonging to a predetermined team, and second information that can be viewed by members belonging to some of the predetermined teams but cannot be viewed by members not belonging to the some teams. The operation authority setting device according to claim 1 .

5. The information is information that is available to owners and residents of apartment buildings or housing complexes, The predetermined plurality of teams are the owner's team and the resident's team, the first information is information that can be viewed by both the owner and the resident, The second information is information that can be viewed by the owner but cannot be viewed by the resident. The operation authority setting device according to claim 4.

6. On the computer, Registering members into a team, which is a group of members who are given the same operating authority; setting operation authority of members registered in the team by assigning to the team an authority group selected from a plurality of authority groups, in which operation authority is defined for each type of operation related to information shared by a plurality of members, based on an authority table predefined for a plurality of authority groups, in which operation authority granting patterns for the types of operation differ from one another; A program to execute.

Images