JP7749982B2 - Information processing device and program - Google Patents

Description

The present invention relates to an information processing device and a program.

Users may be provided with services that allow them to exchange messages between multiple users, such as group chats, and files may be sent to these services.

Patent document 1 describes a system that determines whether or not to allow access to an image file based on the access rights granted to the user type making the access request to the image file.

Patent document 2 describes a device that controls access rights to each application based on the operator's role information.

Patent document 3 describes a system that controls access to data based on the user's role and attributes, as well as changes in the data's status.

Japanese Patent Application Laid-Open No. 2002-140685 Japanese Patent Application Laid-Open No. 2006-202009 JP 2013-114598 A

When a file is sent to a service that allows multiple users to exchange messages, it is possible to set access rights for the file to prevent it from being disclosed to users who do not need to see it. For example, a user could manually set the range of users who are allowed to access the file for each file. However, this requires a lot of effort from the user.

The object of this invention is to reduce the user's effort in setting access rights when a file is sent to a service that allows multiple users to exchange messages, compared to when users individually set access rights to files.

The invention of claim 1 is an information processing device having a processor that provides users with a service for exchanging messages between multiple users assigned roles in a specific activity, and when a first user sends a first message to a second user in the service that has a file associated with it, sets access rights to the file according to the role of the second user, and when the first message includes information regarding a deadline, sets access rights to the file according to the deadline .

The invention of claim 2 is the information processing device described in claim 1, characterized in that the processor further grants access rights to the file to a user assigned the same role as the second user.

The invention of claim 3 is an information processing device described in claim 1 or claim 2, characterized in that the processor further revokes the access rights granted to the role of the second user when work corresponding to the role of the second user on the file is completed.

The invention of claim 4 is an information processing device described in any one of claims 1 to 3, characterized in that the processor further grants access rights to the file to a third user who has a role corresponding to the next task in the activity after the task corresponding to the role of the first user.

The invention of claim 5 is an information processing device described in any one of claims 1 to 4 , characterized in that the processor further sets access rights to the file according to keywords included in the first message.

The invention of claim 6 is a program for causing a computer to operate in such a way that it provides a service to users that allows messages to be exchanged between multiple users assigned roles in a specific activity, and when a first user sends a first message to a second user in the service that has a file associated with it, it sets access rights to the file according to the role of the second user, and when the first message includes information regarding a deadline, it sets access rights to the file according to the deadline .

According to the inventions of claims 1, 2 and 6 , when a file is sent to a service that allows multiple users to exchange messages, the effort required of the user to set access rights to the file is reduced compared to when the user sets access rights to the file individually.

Furthermore , access rights according to the expiration date can be set to a file without the user having to set access rights according to the expiration date to the file.

According to the third aspect of the present invention, it is possible to prevent a user who has completed the work corresponding to his/her role from accessing a file.

According to the fourth aspect of the present invention, access rights can be set to files according to the workflow.

According to the fifth aspect of the present invention, access rights can be set for a file by sending a message.

FIG. 1 is a block diagram showing a configuration of an information processing system. FIG. 2 is a block diagram showing the hardware configuration of a collaboration server. FIG. 2 is a block diagram showing the hardware configuration of the terminal device. FIG. 1 is a diagram illustrating roles. FIG. 10 is a diagram illustrating file access rights. FIG. FIG. 10 is a diagram showing a message screen. FIG. 10 is a diagram showing a message screen. FIG. 10 is a diagram showing a message screen. FIG. 10 is a diagram showing a message screen.

An information processing system according to an embodiment will be described with reference to Figure 1. Figure 1 shows an example of the configuration of an information processing system according to an embodiment.

As an example, the information processing system according to the embodiment includes a link server 14, K file management servers (where K is an integer greater than or equal to 1), L messaging servers (where L is an integer greater than or equal to 1), and M terminal devices (where M is an integer greater than or equal to 1).

In the example shown in FIG. 1, the information processing system according to the embodiment includes file management servers 10A, 10B, ..., 10K, messaging servers 12A, 12B, ..., 12L, and terminal devices 16A, 16B, ..., 16M. These are merely examples, and one or more file management servers, one or more messaging servers, and one or more terminal devices are included in the information processing system according to the embodiment.

In the following, when there is no need to distinguish between file management servers 10A, 10B, ..., 10K, they will be referred to as "file management servers 10." When there is no need to distinguish between messaging servers 12A, 12B, ..., 12L, they will be referred to as "messaging servers 12." When there is no need to distinguish between terminal devices 16A, 16B, ..., 16M, they will be referred to as "terminal devices 16."

The file management server 10, messaging server 12, link server 14, and terminal device 16 have the ability to communicate with other devices. This communication may be wired communication using a cable, or wireless communication. Examples of wireless communication include short-range wireless communication and Wi-Fi (registered trademark). Examples of short-range wireless communication include Bluetooth (registered trademark) and RFID (Radio Frequency Identifier). Each device may communicate with other devices via a communication path N, such as a LAN (Local Area Network) or the Internet.

The file management server 10 provides a service for managing files (hereinafter referred to as the "file management service"). For example, as a file management service, the file management server 10 provides one or more repositories, which are areas where files are stored. A repository is an example of a storage area, and is realized, for example, by memory.

Users are given access rights (hereinafter referred to as "first access rights") in advance, which are the authority to access and use repositories. Using a terminal device 16, users access repositories to which they have first access rights, and store files in the repository or retrieve files from the repository.

For example, user account information (hereinafter referred to as "first account information") for logging in to the file management server 10 is defined for each user and registered on the file management server 10. The first account information may include, for example, a user ID, password, or user biometric information. To log in to the file management server 10, a user uses a terminal device 16 to send their first account information to the file management server 10 and request login to the file management server 10. The file management server 10 authenticates the user who requested login by comparing the first account information sent from the user's terminal device 16 with first account information pre-registered on the file management server 10. If the first account information sent from the user's terminal device 16 is registered on the file management server 10, the file management server 10 permits the user to log in to the file management server 10. A user who is permitted to log in is permitted to log in to the file management server 10 and use a repository to which the user has first access rights. If the first account information sent from the user's terminal device 16 is not registered in the file management server 10, the file management server 10 does not allow the user to log in to the file management server 10. In this case, the user is not permitted to log in to the file management server 10 and use the repository. As an alternative control, the file management server 10 may allow the user to create a new repository to which the user has access rights, even if the file management server 10 does not allow the user to log in to the file management server 10. Furthermore, the file management server 10 may allow the user to use or create a repository regardless of whether the user is logged in.

The process of authenticating a user may be performed by a device other than the file management server 10 (for example, an authentication server). In this case, the file management server 10 receives the results of the authentication process by the authentication server and, depending on the results, allows or does not allow the user to log in to the file management server 10.

The file management server 10 may provide file management services to users (e.g., guest users) who do not log in to the file management server 10 using the first account information.

First account information is defined for each file management server 10 or for each file management service and registered on each file management server 10. The first account information registered on each file management server 10 may be the same or different. For example, the first account information used to log in to file management server 10A and the first account information used to log in to file management server 10B may be the same or different. The same applies to first account information registered on other file management servers 10. The same first account information may be shared among multiple file management servers 10 to authenticate users.

A first access right may be set for each individual repository, or multiple repositories may be managed together and a first access right may be set for each of the multiple repositories. A first access right for a single repository may be set for one piece of first account information, or a first access right for multiple repositories may be set for one piece of first account information. Furthermore, multiple different first account information may be grouped together and the multiple different first account information (i.e., the single group) may be set with first access rights for one or multiple repositories. The first access right may be set or changed when the first account information is registered in the file management server 10, or may be set or changed after the first account information is registered in the file management server 10. A repository without a first access right may be created and all users may be permitted to access the repository. "All users" includes users who are logged in to the file management server 10 and users who are not logged in to the file management server 10 (e.g., guest users).

A user may use a terminal device 16 to log in to the file management server 10 and use the file management service without going through the linking server 14, or may use the file management service via the linking server 14 as described below.

The concept of a file includes image data, video data, graphic data, audio data such as music data and voice data, document data such as text data, programs, and combinations of at least two of these. There are no particular restrictions on the file format, and files managed by the file management server 10 may have any format. Of course, the format of files managed by the file management server 10 may be limited, and only files having a specific format may be managed by the file management server 10.

For example, the file management server 10 is operated by a file management service provider. In other words, the file management service provider provides the file management service by operating the file management server 10. Multiple different file management servers 10 may be operated by the same provider. For example, each file management server 10 may provide a different file management service, and multiple different file management services may be provided by the same provider. Of course, each file management server 10 may be operated by a different provider, and each file management service may be provided by a different provider.

The messaging server 12 provides a service (hereinafter referred to as a "messaging service") that allows at least messages to be exchanged between multiple users. Messages include characters, symbols or codes other than characters, images, videos, figures, sounds, or at least two of these. For example, messaging services include services that send and receive email, SNS (Social Networking Service), groupware, voice calls such as telephones, services that provide online conferences (e.g., services that use audio, images, videos, etc.), or services that provide online games. Online conferences are sometimes called web conferences, remote conferences, video conferences, etc.

Users are given access rights (hereinafter referred to as "second access rights") in advance, which are the authority to use messaging services. Using terminal device 16, users participate in messaging services to which they have second access rights and exchange messages with other users who use the messaging service. For example, when a user sends a message to a messaging service using terminal device 16, the message is sent to other users who use the messaging service. The sent message is, for example, displayed on the display of terminal device 16 or played as audio from a speaker.

For example, user account information (hereinafter referred to as "second account information") for logging in to the messaging server 12 is defined for each user and registered in the messaging server 12. The second account information is, for example, a user ID, password, or user biometric information. When logging in to the messaging server 12, the user uses the terminal device 16 to send their second account information to the messaging server 12 and request login to the messaging server 12. The messaging server 12 authenticates the user who requested login by comparing the account information sent from the user's terminal device 16 with account information pre-registered in the messaging server 12. If the second account information sent from the user's terminal device 16 is registered in the messaging server 12, the messaging server 12 permits the user to log in to the messaging server 12. A user who is permitted to log in is permitted to log in to the messaging server 12 and send, receive, and view messages. If the second account information sent from the user's terminal device 16 is not registered in the messaging server 12, the messaging server 12 does not permit the user to log in to the messaging server 12. In this case, the user is not permitted to log in to the messaging server 12 and exchange messages.

The process of authenticating a user may be performed by a device other than the messaging server 12 (e.g., an authentication server). In this case, the messaging server 12 receives the results of the authentication process by the authentication server and, depending on the results, allows or does not allow the user to log in to the messaging server 12.

The messaging server 12 may provide messaging services to users (e.g., guest users) who do not log in to the file management server 10 using the second account information.

Second account information is defined for each messaging server 12 or each messaging service and registered in each messaging server 12. The second account information registered in each messaging server 12 may be the same or different. For example, the second account information used to log in to messaging server 12A and the second account information used to log in to messaging server 12B may be the same or different. The same applies to second account information registered in other messaging servers 12. The same second account information may be shared among multiple messaging servers 12 to authenticate users. The same information as the first account information may be used as the second account information.

For example, a group made up of multiple users (e.g., a group on a social networking site (e.g., group chat), a mailing list (ML), groupware, etc.), a thread on an electronic bulletin board, a topic, or a collection of messages related to a particular topic are defined as channels in a messaging service. Users join one or more channels and exchange messages with other users who join the same channel. For example, in a messaging service, a channel is created by a user or administrator, and one or more users are permitted to join that channel and exchange messages.

The second access right may be set for each individual channel, or multiple channels may be managed together and the second access right may be set for each of the multiple channels. The second access right for one channel may be set for one piece of second account information, or the second access right for multiple channels may be set for one piece of second account information. Furthermore, multiple different second account information may be grouped together and the second access right for one or multiple channels may be set for the multiple different second account information (i.e., the single group). The second access right may be set or changed when the second account information is registered with the messaging server 12, or may be set or changed after the second account information is registered with the messaging server 12.

A user may use a terminal device 16 to log in to the messaging server 12 and use the messaging service without going through the linking server 14, or may use the messaging service through the linking server 14 as described below.

For example, the messaging server 12 is operated by a messaging service provider. That is, the messaging service provider provides a messaging service by operating the messaging server 12. Multiple different messaging servers 12 may be operated by the same provider. For example, each messaging server 12 may provide a different messaging service, and multiple different messaging services may be provided by the same provider. Of course, each messaging server 12 may be operated by a different provider, and each messaging service may be provided by a different provider.

The linking server 14 links one or more services included in one or more file management services and one or more messaging services to each activity set by the user for a specific purpose, and provides the linked file management service and messaging service. The linking server 14 may link one or more file management services to an activity, may link one or more messaging services to an activity, or may link one or more file management services to one or more messaging services.

For example, multiple users participate in an activity to achieve a specific goal. Hereinafter, users participating in an activity will be referred to as "participants." There are various types of activities, such as work-related activities, sports and other physical activities, and hobby activities. Work-related activities include work projects and tasks in which multiple participants (e.g., employees, contractors, workers, etc.) perform tasks, operations, or actions. There are various types of specific goals, such as work-related goals (e.g., project or task goals), physical activities, and hobby goals.

The user who sets up an activity may be a participant of that activity or an administrator. An administrator may also participate in that activity.

For example, user account information for logging in to the link server 14 (hereinafter referred to as "third account information") is defined for each user and registered in the link server 14. The third account information is, for example, a user ID, password, or user biometric information. When logging in to the link server 14, the user uses the terminal device 16 to send their own third account information to the link server 14 and request login to the link server 14. The link server 14 authenticates the user who requested login by comparing the third account information sent from the user's terminal device 16 with third account information pre-registered in the link server 14. If the third account information sent from the user's terminal device 16 is registered in the link server 14, the link server 14 allows the user to log in to the link server 14. If the account information sent from the user's terminal device 16 is not registered in the link server 14, the link server 14 does not allow the user to log in to the link server 14.

The process of authenticating a user may be performed by a device other than the linked server 14 (for example, an authentication server). In this case, the linked server 14 receives the results of the authentication process by the authentication server and, depending on the results, allows or does not allow the user to log in to the linked server 14.

Account information common to the file management server 10, messaging server 12, and linking server 14 may be used, and a single account may be used to permit login to each of the file management server 10, messaging server 12, and linking server 14. Common account information may also be used by at least two of the file management server 10, messaging server 12, and linking server 14.

The file management server 10, messaging server 12, and linking server 14 may be configured as a single server. The file management server 10 and messaging server 12 may link the file management service and messaging service without going through the linking server 14.

The linkage server 14 does not have to be used. In this case, the file management server 10 or messaging server 12 provides both the file management service and the messaging service. For example, the file management server 10 or messaging server 12 may provide a messaging service with a file management function (i.e., the function of providing a file management service), or a file management service with a messaging function (i.e., the function of providing a messaging service).

If either the file management server 10 or the messaging server 12 provides a messaging service with file management functionality, or a file management service with messaging functionality, the other server and the linking server 14 do not need to be included in the information processing system.

The following describes an example in which a file management service and a messaging service are linked and provided to the user by the linking server 14, but a messaging service with a file management function, or a file management service with a messaging function, may also be provided to the user.

The terminal device 16 may be, for example, a personal computer (hereinafter referred to as a "PC"), a tablet PC, a smartphone, or a mobile phone.

The hardware configuration of the linkage server 14 will be described below with reference to Figure 2. Figure 2 shows an example of the hardware configuration of the linkage server 14.

The linkage server 14 includes, for example, a communication device 18, a UI 20, a memory 22, and a processor 24.

The communication device 18 is a communication interface that includes a communication chip, communication circuit, etc., and has the function of transmitting information to other devices and the function of receiving information from other devices. The communication device 18 may have wireless communication capabilities or wired communication capabilities. The communication device 18 may communicate with other devices using, for example, short-range wireless communication, or may communicate with other devices via communication path N.

UI20 is a user interface and includes at least one of a display and an operation device. The display is an LCD display or an EL display, etc. The operation device is a keyboard, mouse, input keys, operation panel, etc. UI20 may be a UI such as a touch panel that combines a display and an operation device. UI20 may also include a microphone and a speaker.

Memory 22 is a device that constitutes one or more storage areas for storing data. Memory 22 is, for example, a hard disk drive (HDD), a solid state drive (SSD), various types of memory (e.g., RAM, DRAM, ROM, etc.), other storage devices (e.g., optical disks, etc.), or a combination thereof. One or more memories 22 are included in the linked server 14.

The processor 24 is configured to control the operation of each component of the linked server 14. The processor 24 may have memory.

The processor 24 associates multiple participants in each activity set by the user for each specific purpose. The processor 24 associates and manages each activity with each participant in that activity. For example, the processor 24 associates, for each activity, activity identification information (e.g., the name or ID of the activity) for identifying the activity with account information (e.g., third account information) of each participant in the activity, and stores activity management information including this information in the memory 22 to manage the activity and the participants. The processor 24 may further link the activity identification information with the first account information and second account information of each participant. Furthermore, account information common to the file management server 10, messaging server 12, and linking server 14 may be associated with the activity identification information.

Participants in an activity are assigned a role to be performed by that participant in that activity. For each participant in the activity, processor 24 associates activity identification information for identifying the activity, account information (e.g., third account information) of the participant in that activity, and role identification information (e.g., role name, ID, etc.) for identifying the role of that participant, and stores role management information including this information in memory 22 to manage the role of each participant in each activity. Roles are assigned to participants, for example, by an activity administrator, etc. For example, roles are assigned to participants in advance, and role information for each participant is stored in memory 22 in advance.

An activity may also include multiple phases. A phase is work to be performed in an activity and corresponds to the role of a participant. For each activity, processor 24 associates activity identification information for identifying the activity with phase identification information for identifying each phase included in the activity (e.g., phase name, ID, etc.), stores phase management information including this information in memory 22, and manages the phases of each activity. For example, when an activity includes multiple phases whose execution order is predetermined, and the activity is performed, each phase is executed by the participants in that order.

Activity management information, role management information, and phase management information may be integrated and stored in memory 22 as a single piece of management information (e.g., integrated management information) to manage activities, participants, participant roles, and phases.

The processor 24 also associates each activity with one or more services included in one or more file management services and one or more messaging services.

For example, the processor 24 links a repository of a file management service to which at least one participant has first access rights to an activity. The processor 24 manages each activity by linking it to one or more repositories of the file management service linked to that activity. For example, the processor 24 links, for each activity, activity identification information for identifying the activity with an address (e.g., a URL) for accessing each repository linked to that activity, and stores and manages this information in the memory 22.

The processor 24 also links a messaging service to which at least one participant has second access rights to the activity. For example, the processor 24 links a channel to which at least one participant has second access rights to the activity. The processor 24 associates and manages, for each activity, the channel of the messaging service associated with that activity. For example, the processor 24 associates, for each activity, activity identification information for identifying the activity with an address (e.g., a URL) for accessing the channel of the messaging service associated with that activity, and stores and manages this information in the memory 22.

In this way, the processor 24 links file management services and messaging services to a specific activity and provides them to participants in that activity.

The processor 24 also controls the setting of access rights for files. Hereinafter, the access rights set for files will be referred to as "file access rights."

For example, in a messaging service, when a first participant sends a first message to a second participant that has a file associated with it, the processor 24 sets file access rights for the file according to the role of the second participant. Note that the first participant corresponds to an example of a first user, and the second participant corresponds to an example of a second user.

Setting role-based file access rights to a file involves, for example, associating role identification information for identifying the role of the second participant to whom the first message is addressed with the file.

When a participant requests access to a file using their own terminal device 16, if role identification information for identifying the participant's role is associated with the file, the participant is permitted to access the file. If role identification information for identifying the participant's role is not associated with the file, the participant is not permitted to access the file. The decision on whether to permit access to the file may be made by the processor 32 of the terminal device 16 used by the participant, or by the processor 24 of the linking server 14. Files sent to a messaging service are stored in the file management server 10 that provides the messaging service. The file may be stored in the linking server 14, or in the terminal device 16 used by the destination participant.

Files with file access rights set according to roles are permitted to be accessed by participants to whom that role is assigned. In other words, participants assigned a certain role are permitted to access files with file access rights set according to that role. Participants who are permitted to access a file are permitted to open the file and view its contents, copy or move the file, and download the file, among other things.

The processor 24 may set file access rights to the file for other participants who have the same role as the second participant. For example, the processor 24 sets file access rights to the file for other participants who participate in the same activity as the second participant and have the same role as the second participant.

The processor 24 may set file access rights corresponding to keywords included in the first message to a file associated with the first message. For example, the processor 24 analyzes the first message by applying language processing such as morphological analysis to the character strings included in the first message, extracts keywords included in the first message, and sets file access rights corresponding to the extracted keywords to the file.

The hardware configuration of the terminal device 16 will be described below with reference to Figure 3. Figure 3 shows an example of the hardware configuration of the terminal device 16.

The terminal device 16 includes, for example, a communication device 26, a UI 28, a memory 30, and a processor 32.

The communication device 26 is a communication interface that includes a communication chip, communication circuit, etc., and has the function of transmitting information to other devices and the function of receiving information transmitted from other devices. The communication device 26 may have wireless communication capabilities or wired communication capabilities. The communication device 26 may communicate with other devices using, for example, short-range wireless communication, or may communicate with other devices via communication path N.

UI28 is a user interface and includes at least one of a display and an operating device. The display is an LCD display or an EL display, etc. The operating device is a keyboard, mouse, input keys, operating panel, etc. UI28 may be a UI such as a touch panel that combines a display and an operating device. UI28 may also include a microphone and a speaker.

Memory 30 is a device that constitutes one or more storage areas for storing data. Memory 30 is, for example, a hard disk drive (HDD), a solid state drive (SSD), various types of memory (e.g., RAM, DRAM, ROM, etc.), other storage devices (e.g., optical disks, etc.), or a combination thereof. One or more memories 30 are included in terminal device 16.

The processor 32 is configured to control the operation of each part of the terminal device 16. The processor 32 may have memory.

The following describes the embodiments in detail, using specific examples. As an example, the following describes the embodiments assuming a scenario in which a work project is launched as an activity and the project is carried out. For example, the project involves an administrator who manages the project and participants who join the project and perform tasks and operations. The administrator may also join the project as a participant. The administrator and participants use their own terminal devices 16 to use the file management service provided by the file management server 10 and the messaging service provided by the messaging server 12. The administrator and participants also use their own terminal devices 16 to use services (e.g., file management services and messaging services) linked to the activity by the link server 14.

The roles of participants will be explained with reference to Figure 4. Figure 4 shows an example of a role. Roles include, for example, sales, requirements analysis/definition, system design, detailed design, implementation, testing, and project management. One or more of these roles are pre-defined for each participant taking part in the project. Information indicating the role of each participant is included in the integrated management information described above, and the role of each participant is managed. Note that the same role may be assigned to multiple participants.

Referring to Figure 5, we will explain the file access rights set for a file. Figure 5 shows an example of file access rights set for a file. File access rights are set for each role. A file for which file access rights for a certain role are set is a file that participants assigned that role are permitted to access. Examples of file access rights include file access rights for sales, file access rights for requirements definition, file access rights for detailed design, file access rights for implementation, file access rights for testing, and file access rights for project management.

Files with file access rights set for sales are files that participants assigned the role of "sales" are permitted to access. Files with file access rights set for requirements analysis/requirements definition are files that participants assigned the role of "requirements analysis/requirements definition" are permitted to access. The same applies to other file access rights.

Referring to Figure 6, we will explain the phases included in a project, which is an example of an activity. Figure 6 shows an example of the phases included in Project α. Project α includes the following phases: "1. Sales," "2. Requirements Analysis/Requirements Definition," "3. System Design," "4. Detailed Design," "5. Implementation," and "6. Testing." In Project α, these phases are scheduled to be executed in the numerical order shown in Figure 6. That is, each phase (i.e., each task) is scheduled to be executed in the following order: "Sales," "Requirements Analysis/Requirements Definition," "System Design," "Detailed Design," "Implementation," and "Testing." A phase represents work to be performed by a participant assigned a role corresponding to that phase. For example, the "Sales" phase represents work to be performed by a participant assigned the role "Sales." The "Requirements Analysis/Requirements Definition" phase represents work to be performed by a participant assigned the role "Requirements Analysis/Requirements Definition." The same applies to other phases.

Below is an example of a rule for setting file access rights for a file.

As an example, assume that a participant who has created a file uses their own terminal device 16 to post the file to a message service associated with project α in which the participant is participating. Posting a file means sending the file to the message service, either associated with a message or not. Participants are permitted to access files posted to the message service according to the file access rights set for the file.

(Rule 1)
In setting access rights in accordance with Rule 1, the processor 24 sets, to the file, file access rights for roles corresponding to phases later than the phase corresponding to the role of the participant who posted the file. For example, if a participant assigned the role "Sales" posts a file, the processor 24 sets, to the file, file access rights for roles corresponding to phases later than the phase "Role". As a result, participants assigned roles corresponding to phases later than the phase "Role" are permitted to access the file for which the file access rights are set. For example, file access rights for roles corresponding to the phases "Requirements Analysis/Requirements Definition", "System Design", "Detailed Design", "Implementation", and "Test" are set to the file, and participants assigned each of the roles are permitted to access the file.

(Rule 2)
In setting access rights according to Rule 2, the processor 24 sets file access rights to a file according to keywords included in the first message associated with the file. Examples of keywords include the name of a role, the name of a phase, the name of a file type, the name of a file, and comments about work performed on the file.

For example, the processor 24 extracts the string "phase name" included in the first message as a keyword, and sets file access rights for the role corresponding to the phase having that "phase name" to the file associated with the first message. To give a specific example, if the keyword included in the first message associated with a file is the string "system design," the processor 24 sets file access rights for the role "system design" to the file. This allows participants assigned the role "system design" to access the file.

The processor 24 may also set file access rights corresponding to the file type name or file name for the file. For example, roles and phases corresponding to file type names and file names are predetermined, and the processor 24 sets file access rights for the role and phase corresponding to the posted file type name or file name for the file in accordance with those definitions.

The processor 24 may also extract the character string "comment regarding work performed on the file" included in the first message as a keyword, and set file access rights related to the "comment" to the file. Examples of comments include "creation," "completion," and "storage" of the file. For example, if the first message includes a character string indicating "phase completion," the processor 24 extracts the character string as a keyword and analyzes it to recognize that the phase has been completed. In this case, the processor 24 sets file access rights to the file for the role corresponding to the phase following the current phase. To give a specific example, if a character string such as "system design completion" is extracted from the first message, the processor 24 sets file access rights to the file for the role "detailed design," which corresponds to the phase "detailed design" following the phase "system design." As a result, participants assigned the role "detailed design" are permitted to access the file.

(Rule 3)
In setting access rights in accordance with Rule 3, when a first participant sends a first message associated with a file to a second participant in a messaging service corresponding to project α in which the first and second participants are participating, processor 24 sets file access rights to the file according to the role of the second participant.

For example, if the role of the second participant is the role "system design," the processor 24 sets the file access rights for the role "system design" to the file. This allows the second participant to access the file.

Even if another participant is participating in project α in which the first and second participants are participating, a file sent to the second participant via the messaging service corresponding to project α will only be sent to the second participant, and not to the other participant. If the other participant is included in the recipient list of the file, the file will also be sent to the other participant.

(Rule 4)
If the role to which file access rights to a posted file are granted is not identified based on messages exchanged on the messaging service corresponding to project α, the processor 24 may grant file access rights to all participants participating in project α, may grant file access rights only to the participant who posted the file, or may grant file access rights to the role of the participant who posted the file. In other words, the processor 24 may set file access rights for all roles in project α to the file, may set file access rights that are accessible only to the participant who posted the file, or may set file access rights for the role of the participant who posted the file to the file.

The above rules 1 to 4 are examples of rules for setting access rights, and access rights may be set for files according to other rules.

The processing according to the embodiment will be described in detail below using a specific example. As an example, assume that project α is being carried out as an example of an activity, and participants A, B, C, D, E, F, and G are participating in project α.

Participant A is assigned the role of "sales," Participant B is assigned the role of "requirements analysis/definition," Participant C is assigned the role of "system design," Participant D is assigned the role of "detailed design," Participant E is assigned the role of "implementation," Participant F is assigned the role of "testing," and Participant G is assigned "project management." Information regarding these participants is, for example, registered in advance in the integrated management information described above.

For example, each participant uses their own terminal device 16 to send their account information (e.g., third account information) to the linking server 14, requesting login to the linking server 14 and access to project α. Participants who are successfully authenticated are permitted to log in to the linking server 14 and access the file management service and messaging service associated with project α. Participants who are successfully authenticated are permitted to access, for example, a repository provided by the file management service associated with project α and to exchange information with other participants using the messaging service associated with project α. Note that each participant may access the linking server 14 using their own terminal device 16 and use the file management service and messaging service associated with project α without logging in to the linking server 14 or being authenticated.

For example, the processor 24 of the link server 14 displays a screen for using the messaging service associated with project α on the display of the terminal device 16 used by the participants of project α. Note that a file management service may also be used via this screen. Hereinafter, the screen for using the messaging service will be referred to as the "message screen." The message screen displays messages sent by each participant to the messaging service.

For example, a group chat may be formed with multiple participants, and messages may be exchanged between the multiple participants in the group chat on a message screen. Also, multiple threads (e.g., multiple channels for exchanging messages about a specific topic) may be formed for Project α, and messages may be exchanged in each thread. Each thread may involve all participants in Project α, or only some of the participants. Each thread may involve the same or different multiple participants.

Figure 7 shows an example of a message screen. The message screen 34D shown in Figure 7 is a message screen displayed on the display of participant D's terminal device 16D.

The processor 24 displays messages sent to the messaging service associated with project α (more specifically, channels linked to project α) on the message screen 34D. For example, each message is displayed in a timeline format. That is, each message is displayed in order according to the date and time the message was sent to the channel. For example, each message is displayed in order from top to bottom on the message screen 34D according to the date and time the message was sent to the channel. Note that information for identifying the participant who sent the message (for example, name, nickname, ID, or an image such as an icon) may be associated with the message and displayed on the message screen 34D. For example, the information is displayed near the message.

Messages that cannot be displayed on message screen 34D can be displayed within message screen 34D by moving message screen 34D up or down (for example, by scrolling message screen 34D up or down).

Furthermore, if a file associated with a message is sent to a messaging service, an image (e.g., an icon) representing the file will be displayed on message screen 34D.

When a participant other than participant D accesses project α, a message screen similar to message screen 34D will be displayed on the display of the other participant's terminal device 16.

In the example shown in FIG. 7, messages 36, 40, 42, and 44 are displayed on message screen 34D. Messages 36 and 44 are messages sent by participant D to the message service associated with project α. Messages 40 and 42 are messages sent by participant C to the message service associated with project α. File 38 is attached to message 36. In other words, message 36, which has file 38 associated with it, was sent to the messaging service by participant C.

An input field 46 is also displayed on message screen 34D. Input field 46 is a field for sending a message to the messaging service. When a message is entered in input field 46 and an instruction to send is given (for example, when the send button displayed on message screen 34D is pressed), processor 24 displays the entered message on message screen 34D as a message from participant D. Processor 24 also sends the entered message to other participants accessing the messaging service associated with project α.

Messages sent to the messaging service associated with Project α may be viewable by all participants in Project α. In other words, messages sent to the messaging service associated with Project α may be displayed on the message screens displayed on the displays of the terminal devices 16 of all participants.

As another example, in a messaging service associated with project α, a message sent to a specific participant may be viewable only by the participant who sent the message and the specific participant. In other words, the message may be displayed only on the message screen displayed on the display of the terminal device 16 of the participant who sent the message and the specific participant. For example, when a participant specifies a message destination and sends a message, the message is sent to the participant specified as the destination, and the message is displayed only on the message screen displayed on the display of the terminal device 16 of the participant who sent the message and the destination participant.

In the example shown in FIG. 7, messages 36 and 44 are messages sent from participant D to participant C, and messages 40 and 42 are messages sent from participant C to participant D. Therefore, messages 36, 40, 42, and 44 are displayed only on the message screens displayed on the displays of the terminal devices 16 of participants C and D, respectively, and are not displayed on the message screens displayed on the displays of the terminal devices 16 of other participants such as participant A.

If the destination of message 36 is specified as participant C, processor 24 displays information for identifying participant C (e.g., name, account information, etc.) near message 36, as indicated by reference symbol 36a. For example, a list of participants participating in project α is displayed on message screen 34D, and participant D may specify the destination participant (e.g., participant C) from the list, or participant D may directly input information for identifying the destination participant.

Although not shown in Figure 7, information identifying the intended participants for messages 40, 42, and 44 is also displayed near each message.

Even if a participant to whom a message is addressed is specified, information for identifying the participant to whom the message is addressed (e.g., the character string indicated by reference numeral 36a) does not necessarily have to be associated with the message and displayed on the message screen.

Note that messages may be sent to each participant as individual messages, rather than being sent to project α. For example, message 36, which is associated with file 38, may be sent from participant D to participant C, rather than being sent to project α.

In the example shown in Figure 7, message 36, which is associated with file 38, corresponds to an example of the first message.

For example, processor 24 sets file access rights for file 38 according to the role "detailed design" assigned to participant D who posted message 36 (i.e., participant D who sent message 36 to the messaging service associated with project α). In other words, processor 24 associates role identification information for identifying the role "detailed design" with file 38. This allows participants assigned the role "detailed design" to access file 38. For example, participant D is allowed to access file 38.

Furthermore, file access rights to file 38 are granted to participants who are assigned the same role as participant D, who posted message 36. In other words, participants other than participant D who are assigned the role of "detailed design" are permitted to access file 38.

The processor 24 may analyze a character string included in the message 36 with which the file 38 is associated, and set file access rights to the file 38 according to the analysis results. For example, the processor 24 extracts a character string indicating a role, a character string indicating a phase, or a character string indicating an operation from the message 36, and sets file access rights corresponding to the extracted character string to the file 38. The message 36 includes the character string "detailed design," which is a character string indicating a role or a phase. In this case, the processor 24 associates role identification information for identifying the role "detailed design" with the file 38, and sets file access rights for the role "detailed design" to the file 38.

The processor 24 may set file access rights for the file 38 according to the role "system design" of participant C, who is the destination of the message 36. In other words, the processor 24 associates role identification information for identifying the role "system design" with the file 38. This allows participants assigned the role "system design" to access the file 38. For example, participant C is allowed to access the file 38.

Furthermore, file access rights to file 38 are granted to participants who are assigned the same role as participant C, who is the recipient of message 36. In other words, participants other than participant C who are assigned the role of "system design" are permitted to access file 38.

If the first message includes information about a deadline, the processor 24 may set file access rights corresponding to the deadline for the file associated with the first message. File access rights corresponding to the deadline are file access rights for which a deadline is set. For example, a file for which file access rights corresponding to a deadline are set is a file for which access is permitted until the deadline arrives or passes.

For example, if the message 36 associated with the file 38 contains information about a deadline, the processor 24 sets file access rights for the file 38 according to the deadline.

To give a specific example, message 36 is a message indicating that participant D is requesting participant C to review file 38. If message 36 contains a string related to a deadline, such as "by October 5th," processor 24 sets file access rights for file 38 according to the deadline. For example, processor 24 associates information indicating the deadline with file 38. In this case, access to file 38 is permitted until October 5th arrives or passes. For example, role identification information for identifying the role "system design" and information indicating the deadline are associated with file 38. Participants assigned the role "system design" are permitted to access file 38 until the deadline arrives or passes.

When the work on the file corresponding to the role of the second participant is completed, the processor 24 may revoke the file access rights granted to the role of the second participant. Revoked file access rights to the file means deleting the role identification information associated with the file, or, without deleting the role identification information associated with the file, associating information with the file indicating that participants assigned the role indicated by the role identification information are not permitted to access the file. When the file access rights granted to a role are revoked, participants assigned the role are not permitted to access files for which the revoked file access rights are set.

For example, processor 24 analyzes the strings included in a message posted by participant C, who is the second participant to whom message 36, to which file 38 is associated, is addressed, and determines whether the work corresponding to participant C's role has been completed. In the example shown in FIG. 7, message 42 posted by participant C contains the strings "review" and "complete." In this case, processor 24 extracts these strings from message 42, recognizes that participant C's review has been completed, and revokes the file access rights granted to participant C's role "system design" from file 38. As a result, a participant assigned the role "system design" (e.g., participant C) is not permitted to access file 38.

The processor 24 may grant file access rights to a file to a third participant who is assigned a role corresponding to the phase (e.g., work) following the phase (e.g., work) corresponding to the role of the first participant in the activity. For example, the processor 24 refers to the integrated management information described above to identify the order of each phase included in the activity, and grants file access rights to the file to the third participant who is assigned a role corresponding to the next phase. In this case, the processor 24 associates role identification information for identifying the role corresponding to the next phase with the file, thereby allowing the participant who is assigned the role to access the file.

In the example shown in FIG. 7, the first participant, participant D, is assigned the role of "detailed design." In this case, processor 24 associates role identification information for identifying the role "implementation" corresponding to the phase "implementation" that follows the phase "detailed design" corresponding to the role "detailed design" with file 38. This allows participants assigned the role "implementation" to access file 38.

When the task corresponding to the role of participant C, the second participant, is completed, processor 24 may grant file access rights to file 38 to a participant assigned a role corresponding to the phase subsequent to the phase corresponding to participant C's role. Explaining this process in more detail, processor 24 analyzes a string included in a message (e.g., messages 40 and 42) posted by participant C, who is the recipient of message 36 associated with file 38, and determines whether the task corresponding to participant C's role has been completed. If the task has been completed, processor 24 grants file access rights to the file to a participant assigned a role corresponding to the phase subsequent to the phase corresponding to participant C's role. In other words, processor 24 associates role identification information for identifying the role corresponding to the subsequent phase with file 38.

To give a specific example, message 42 posted by participant C, who is the recipient of message 36 with which file 38 is associated, contains the character strings "review" and "complete." In this case, processor 24 determines that the work corresponding to the role assigned to participant C has been completed, and associates with file 38 role identification information for identifying role "detailed design" corresponding to the phase "detailed design" that follows the phase "system design" corresponding to participant C's role "system design."

When the work corresponding to the role of participant C, the second participant, is completed, the processor 24 may grant file access rights to file 38 to a participant who is assigned a role corresponding to the phase next to the phase corresponding to the role of participant D, the first participant.

In the example shown in FIG. 7, when the work corresponding to the role "system design" of participant C, the second participant to whom message 36, which is associated with file 38, is addressed, is completed, processor 24 grants file access rights to file 38 to participants assigned the role "implementation," which corresponds to the phase "implementation" that follows the phase "detailed design" corresponding to the role "detailed design" of participant D, the first participant who posted message 36. In other words, processor 24 associates role identification information for identifying the role "implementation," which corresponds to the next phase "implementation," with file 38. As a result, participants assigned the role "implementation" are permitted to access file 38.

The example of file access right settings described with reference to FIG. 7 is one example. For example, file access rights for file 38 are granted to the role "detailed design" of participant D, who posted message 36 associated with file 38, and the role "system design" of participant C, the recipient of message 36. Furthermore, when the work corresponding to the role "system design" of participant C, the recipient of message 36, is completed, file access rights for file 38 are granted to the role "implementation," which corresponds to the phase following the phase "detailed design," which corresponds to the role "detailed design" of participant D, who posted message 36. As a result, participants assigned the role "detailed design," participants assigned the role "system design," and participants assigned the role "implementation" are permitted to access file 38. Furthermore, participants assigned roles for which file access rights have been revoked are not permitted to access file 38.

Figure 8 shows messages exchanged between participant D and participant F. Figure 8 also shows message screen 34D displayed on the display of participant D's terminal device 16D. Message screen 34D displays messages 48, 50, 52, 54, and 58. Messages 50 and 54 are messages sent by participant D to participant F. Messages 48, 52, and 58 are messages sent by participant F to participant D. A screen similar to message screen 34D is also displayed on the display of participant F's terminal device 16F, and messages 48, 50, 52, 54, and 58 are displayed on this screen. Message 54 is also associated with file 56, which indicates a link (e.g., an address such as a URL) to file 38. File 38 can be accessed by accessing this link.

Furthermore, as shown in FIG. 7, by exchanging messages between participant C and participant D, file access rights for file 38 are granted to the roles "detailed design," "system design," and "implementation." For example, participant D, who posted message 36 associated with file 38, exchanges messages with participant C (see FIG. 7), and then exchanges messages with participant F (see FIG. 8).

Processor 24 sets file access rights for file 38 posted by participant D for the role "test" of participant F, who is the recipient of the message posted by participant D. In other words, processor 24 associates role identification information for identifying role "test" with file 38. As a result, participants assigned the role "test" are permitted to access file 38.

Figure 9 shows another exchange of messages. Figure 9 shows message screen 34E. Message screen 34E is a screen displayed on the display of participant E's terminal device 16E. On message screen 34E, messages 60, 62, 64, and 66 are exchanged between participant E and other participants. File 68 is attached to message 60 posted by participant E.

For example, the processor 24 analyzes a string included in the message 60 to which the file 68 is associated, and sets file access rights for the file 68 according to the analysis results. The message 60 includes the string "implementation." In this case, the processor 24 associates role identification information for identifying the role "implementation" with the file 68, thereby setting file access rights for the file 68 for the role "implementation." As a result, participants assigned the role "implementation" are permitted to access the file 68.

Message 60 also contains the string "implementation" along with the string "completed." In this case, processor 24 recognizes that the work corresponding to role "implementation" has been completed, and may set file access rights for role "implementation" by associating role identification information for identifying role "implementation" with file 68.

The processor 24 may set the file access rights for the file 68 for the role "Implementation" of participant E, who posted the message 60 with which the file 68 is associated.

Figure 10 shows another exchange of messages. Figure 10 shows message screen 34F. Message screen 34F is a screen displayed on the display of participant F's terminal device 16F. On message screen 34F, messages 70, 72, 74, and 76 are exchanged between participant F and other participants. Message 70 posted by participant F has file 78 attached.

For example, the processor 24 analyzes a string included in the message 70 to which the file 78 is associated, and sets file access rights for the file 78 according to the analysis results. The message 70 includes the string "test." In this case, the processor 24 associates role identification information for identifying the role "test" with the file 78, thereby setting file access rights for the file 78 for the role "test." As a result, participants assigned the role "test" are permitted to access the file 78.

Message 70 also contains the string "create" along with the string "test." In this case, processor 24 recognizes that the work corresponding to role "test" has been completed, and may set file access rights for role "test" by associating role identification information for identifying role "test" with file 78.

The processor 24 may set file access rights for the file 78 for the role "test" of participant F, who posted the message 70 with which the file 78 is associated.

Another application example of the embodiment will be described below. The embodiment may be applied to an activity where work flows in one direction. For example, the embodiment may be applied to an activity that includes multiple tasks that must be performed in a predetermined order, and authority for each task is granted to the workers involved in each task.

For example, the embodiments are applied to activities that involve multiple tasks performed in a medical setting (e.g., medical procedures, diagnoses, etc.). Specifically, the embodiments may be applied to medical procedures and diagnoses that involve imaging using a CT scanner, MRI scanner, etc. In such situations, the following tasks are performed in this order: scanning by a radiologist or other photographer, image generation, image quality confirmation, and loading of diagnostic information onto the image, and display and printing of the image by a doctor, nurse, etc. In this case, because a doctor's authority is greater than other authorities, the doctor is granted authority for all tasks, and workers other than a doctor are granted authority according to the role of the worker.

As another example, the embodiment may be applied to work related to publishing or advertising. For example, tasks such as creating a manuscript, submitting the manuscript, typesetting, proofreading, color proofing, and printing are performed in this order. Each worker is granted authority according to the role and order of the worker involved in each task.

The functions of each of the above-mentioned file management server 10, messaging server 12, link server 14, and terminal device 16 are realized, for example, by a combination of hardware and software. For example, the processor of each device reads and executes a program stored in the memory of each device, thereby realizing the function of each device. The program is stored in memory via a recording medium such as a CD or DVD, or via a communication path such as a network.

In the above embodiments, the term "processor" refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.). Furthermore, the operations of the processor in the above embodiments may not only be performed by a single processor, but may also be performed by multiple processors located in physically separate locations working together. Furthermore, the order of each processor operation is not limited to the order described in the above embodiments, and may be changed as appropriate.

10A, 10B, ..., 10K file management servers, 12A, 12B, ..., 12L messaging servers, 14 collaboration servers, 16A, 16B, ..., 16M terminal devices, 24 processors.

Claims (6)

a processor;
The processor:
providing users with a service for exchanging messages among multiple users who are assigned roles in a specific activity;
When a first user sends a first message to a second user in the service, the first message has a file associated therewith. The second user's access rights are set to the file according to the role of the second user;
If the first message includes information about a deadline, an access right according to the deadline is set for the file.
Information processing device. The processor further comprises:
granting access rights to the file to a user assigned a role that is the same as the role of the second user;
2. The information processing apparatus according to claim 1, wherein: The processor further comprises:
When the work on the file according to the role of the second user is completed, the access right granted to the role of the second user is cancelled.
3. The information processing device according to claim 1 or 2 . The processor further comprises:
granting access rights to the file to a third user who has a role corresponding to a task subsequent to a task corresponding to a role of the first user in the activity;
4. The information processing device according to claim 1, wherein the information processing device is a computer . The processor further comprises:
setting an access right to the file according to a keyword included in the first message;
5. The information processing device according to claim 1, wherein the information processing device is a computer . The computer
providing users with a service for exchanging messages among multiple users who are assigned roles in a specific activity;
When a first user sends a first message to a second user in the service, the first message has a file associated therewith. The second user's access rights are set to the file according to the role of the second user;
If the first message includes information about a deadline, an access right according to the deadline is set for the file.
A program to make it work like this.