Information processing device and program

Abstract

To provide an information processing apparatus and program for presenting a message related to a certain file to a user.SOLUTION: An information processing system includes a plurality of file management servers, a plurality of messaging servers, a plurality of terminal devices, and a cooperation server. A terminal device 16, which is an information processing apparatus, includes a processor 32 configured to form a first display region where messages from the device or other terminals are displayed and a second display region where files are displayed on a display, and display a message related to an operated file so as to indicate the message in the first display region in accordance with the operation performed on the file displayed in the second display region.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information processing device and a program. [Background technology]

[0002] Patent Document 1 describes displaying comments on a timeline in different colors for each topic.

[0003] Patent Document 2 describes identifying a document file related to a keyword included in a message. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2018-60508 [Patent Document 2] Japanese Patent Application Publication No. 2019-185620 Summary of the Invention [Problem to be solved by the invention]

[0005] An object of the present invention is to present a user with messages related to a file. [Means for solving the problem]

[0006] First Reference Example is an information processing device having a processor that forms a first display area in which messages are displayed and a second display area in which files are displayed on a display, and that, in response to an operation on a file displayed in the second display area, displays, among messages displayed in the first display area, messages related to the operated file in a manner that makes them distinguishable from other messages.

[0007] Second Reference ExampleWhen an updated file is operated, the processor displays a message related to the updated file in the first display area. First Reference Example The information processing device is described in the above.

[0008] Third Reference Example messages related to updated files will be included, including messages with the original file attached. Second Reference Example The information processing device is described in the above.

[0009] Fourth Reference Example the processor does not display messages not related to the operated file in the first display area. First Reference Example from Third Reference Example 1 is an information processing device according to any one of the preceding claims.

[0010] Fifth Reference Example the first display area is a movable area, and a message is displayed or hidden in accordance with the movement of the first display area; the second display area is a movable area, and a file is displayed or hidden in accordance with the movement of the second display area; and the processor moves the first display area in accordance with an operation on a file displayed in the second display area so that a message related to the operated file is displayed. First Reference Example from Fourth Reference Example 1 is an information processing device according to any one of the preceding claims.

[0011] Sixth Reference Example the first display area and the second display area are display areas formed on a single screen, and the processor moves either the first display area or the second display area in accordance with the movement of the other display area. Fifth Reference Example The information processing device is described in the above.

[0012] Claim 1The invention relates to an information processing device having a processor that forms a first display area on a display where messages are displayed and a second display area where files are displayed, and that displays in the first display area a message related to the operated file in response to an operation on a file displayed in the second display area, wherein each activity set by a user for a specific purpose is associated with participants in the activity, and storage areas of file management services provided by multiple service providers to which at least one participant has access are linked to the activity, and a messaging service for exchanging at least messages to which at least one participant has access is linked to the activity, wherein the first display area is an area where messages sent to an linked messaging service to which the requesting participant has access in response to a request for access to the activity from each participant are displayed, and the second display area is an area where files stored in the linked storage area to which the requesting participant has access are displayed.

[0013] Seventh Reference Example is a program for operating a computer to form on a display a first display area in which messages are displayed and a second display area in which files are displayed, and in response to an operation on a file displayed in the second display area, display, among the messages displayed in the first display area, messages related to the operated file in a manner that makes them distinguishable from other messages. [Effects of the Invention]

[0014] Reference Examples 1 and 7 allows a message related to a file to be presented to the user.

[0015] Second and third reference examples According to the present invention, a message relating to the updated file can be presented to the user.

[0016] The fourth reference exampleThis makes it possible to prevent messages unrelated to the operated file from being presented to the user.

[0017] Fifth and Sixth Reference Examples According to the method, when a file is operated, even if a message related to the file is not displayed in the first display area, the message can be presented to the user.

[0018] Claim 1 According to the present invention, even if a file relating to an activity set for a specific purpose is managed by a file management service provided by a service provider and messages relating to the activity are managed by a messaging service, a message related to a certain file can be presented to a user. [Brief explanation of the drawings]

[0019] [Figure 1] FIG. 1 is a block diagram showing a configuration of an information processing system. [Figure 2] FIG. 2 is a block diagram showing the hardware configuration of a collaboration server. [Figure 3] FIG. 2 is a block diagram showing the hardware configuration of the terminal device. [Figure 4] FIG. 2 is a block diagram showing the configuration of a file management server. [Figure 5] FIG. 10 is a diagram illustrating a setting screen. [Figure 6] FIG. [Figure 7] FIG. [Figure 8] FIG. 10 is a diagram illustrating a setting screen. [Figure 9] FIG. 10 is a diagram illustrating a setting screen. [Figure 10] FIG. [Figure 11] FIG. [Figure 12] FIG. [Figure 13] FIG. [Figure 14] FIG. [Figure 15] FIG. [Figure 16] FIG. [Figure 17] FIG. [Figure 18] FIG. [Figure 19] FIG. [Figure 20] FIG. [Figure 21] FIG. [Figure 22] FIG. [Figure 23] FIG. [Figure 24] FIG. [Figure 25] FIG. [Figure 26] FIG. [Figure 27] FIG. [Figure 28] FIG. 2 is a diagram illustrating a display area. [Figure 29] FIG. 2 is a diagram illustrating a display area. DETAILED DESCRIPTION OF THE INVENTION

[0020] First Embodiment An information processing system according to the first embodiment will be described with reference to Fig. 1. Fig. 1 shows an example of the configuration of the information processing system according to the first embodiment.

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

[0022] 1, the information processing system according to the first 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 first embodiment.

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

[0024] The file management server 10, messaging server 12, link server 14, and each terminal device 16 have the function of communicating with other devices. This communication may be wired communication using a cable, or may be wireless communication. Wireless communication may be, for example, short-range wireless communication or Wi-Fi (registered trademark). Short-range wireless communication may be, for example, Bluetooth (registered trademark) or 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.

[0025] The file management server 10 provides a service for managing files (hereinafter referred to as a "file management service"). For example, as the 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 by, for example, a memory.

[0026] An access right (hereinafter referred to as a "first access right") that is the authority to access and use a repository is given to the user in advance. The user uses the terminal device 16 to access the repository to which the user has the first access right, and stores files in the repository or retrieves files from the repository.

[0027] 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 in the file management server 10. The first account information is, for example, a user ID, a password, or the user's biometric information. When logging in to the file management server 10, the user uses the terminal device 16 to send their own 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 in the file management server 10. If the first account information sent from the user's terminal device 16 is registered in 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 a first access right. If the first account information transmitted from the user's terminal device 16 is not registered in the file management server 10, the file management server 10 does not permit 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 a separate control, the file management server 10 may permit the user to create a new repository to which the user has access rights, even if the file management server 10 does not permit the user to log in to the file management server 10. Furthermore, the file management server 10 may permit the user to use or create a repository regardless of whether the user is logged in.

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

[0029] The file management server 10 may provide file management services to users who do not log in to the file management server 10 using the first account information (for example, guest users).

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

[0031] A first access right may be set for each individual repository, or multiple repositories may be collectively managed and a first access right may be set for each of the multiple repositories. A first access right for one 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 a first access right for one or multiple repositories may be set for the multiple different first account information (i.e., the single group). 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. Note that a repository without a first access right may be created, and all users may be permitted to access the repository. All users include 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).

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

[0033] 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 a combination of at least two of these. The file format is not particularly limited, 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.

[0034] For example, the file management server 10 is operated by a file management service provider. That is, 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.

[0035] The messaging server 12 provides a service (hereinafter referred to as a "messaging service") for exchanging at least messages among multiple users. A message includes characters, symbols or codes other than characters, images, videos, figures, sounds, or at least two of these. For example, the messaging service is a service for sending and receiving emails, a social networking service (SNS), groupware, voice calls such as telephones, a service for providing online conferences (for example, services using voice, images, videos, etc.), or a service for providing online games. An online conference is sometimes called a web conference, a remote conference, a video conference, etc.

[0036] An access right (hereinafter referred to as "second access right") that is the authority to use a messaging service is given to the user in advance. The user uses the terminal device 16 to participate in the messaging service to which the user has the second access right, and exchanges messages with other users who use the messaging service. For example, when the user sends a message to the messaging service using the 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 the terminal device 16 or output as sound from a speaker.

[0037] For example, user account information (hereinafter referred to as "second account information") for logging in to the messaging server 12 is determined for each user and registered in the messaging server 12. The second account information is, for example, a user ID, a password, or the user's 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 logging in to the messaging server 12. The messaging server 12 authenticates the user who requested logging in 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.

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

[0039] The messaging server 12 may provide a messaging service to users who do not log in to the file management server 10 using the second account information (for example, guest users).

[0040] Second account information is defined for each messaging server 12 or for 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 for logging in to messaging server 12A and the second account information for logging in to messaging server 12B may be the same or different. The same applies to second account information registered in other messaging servers 12. Note that the same second account information may be shared among multiple messaging servers 12 to authenticate users. Note that the same information as the first account information may be used as the second account information.

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

[0042] The second access right may be set for each individual channel, or multiple channels may be collectively managed 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 pieces of second account information may be grouped together, and the second access right for one or multiple channels may be set for the multiple different pieces of second account information (i.e., the single group). The second access right may be set or changed when the second account information is registered in the messaging server 12, or may be set or changed after the second account information is registered in the messaging server 12.

[0043] The user may use the messaging service by logging in to the messaging server 12 using the terminal device 16 without going through the link server 14, or may use the messaging service via the link server 14 as described below.

[0044] 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.

[0045] 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 each specific purpose. For example, 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.

[0046] 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 activities, physical activities such as sports, and hobby activities. An example of a work activity is a work project or task 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 goals (e.g., project or task goals), physical activities, and hobby goals.

[0047] A user who sets up an activity may be a participant of the activity or an administrator, and the administrator may also participate in the activity.

[0048] For example, user account information for logging in to link server 14 (hereinafter referred to as "third account information") is defined for each user and registered in link server 14. The third account information is, for example, a user ID, a password, or the user's biometric information. When logging in to link server 14, the user uses terminal device 16 to transmit their own third account information to link server 14 and requests logging in to link server 14. Link server 14 authenticates the user who requested logging in by comparing the third account information transmitted from the user's terminal device 16 with third account information pre-registered in link server 14. If the third account information transmitted from the user's terminal device 16 is registered in link server 14, link server 14 permits the user to log in to link server 14. If the account information transmitted from the user's terminal device 16 is not registered in link server 14, link server 14 does not permit the user to log in to link server 14.

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

[0050] Account information common to the file management server 10, the messaging server 12, and the linking server 14 may be used, and one piece of account information may be used to permit login to each of the file management server 10, the messaging server 12, and the linking server 14. Common account information may be used by at least two of the file management server 10, the messaging server 12, and the linking server 14.

[0051] The link server 14 may provide a file management service and a messaging service to users. That is, the link server 14 may create a repository in its own device and allow users to use the repository. The link server 14 may also allow multiple users who are logged in to the link server 14 to exchange messages with each other. When the link server 14 provides a file management service, it is not necessary to link the file management service provided by the file management server 10 with an activity set for a specific purpose. Of course, the link server 14 may provide the file management service and link the file management provided by the file management server 10 with an activity set for a specific purpose. When the link server 14 provides a messaging service, it is not necessary to link the messaging service provided by the messaging server 12 with an activity set for a specific purpose. Of course, the link server 14 may provide the messaging service and link the messaging service provided by the messaging server 12 with an activity set for a specific purpose.

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

[0053] The hardware configuration of link server 14 will be described below with reference to Fig. 2. Fig. 2 shows an example of the hardware configuration of link server 14.

[0054] The link server 14 includes, for example, a communication device 18, a UI 20, a memory 22, and a processor 24.

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

[0056] The UI 20 is a user interface and includes at least one of a display and an operation device. The display is a liquid crystal display, an EL display, or the like. The operation device is a keyboard, a mouse, input keys, an operation panel, or the like. The UI 20 may be a UI such as a touch panel that combines a display and an operation device. The UI 20 may also include a microphone and a speaker.

[0057] The memory 22 is a device that configures one or more storage areas for storing data. The 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 linking server 14.

[0058] The processor 24 is configured to control the operation of each unit of the link server 14. The processor 24 may include a memory.

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

[0060] Processor 24 also associates each activity with one or more services, including one or more file management services and one or more messaging services.

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

[0062] In response to a request from a participant for access to an activity, processor 24 causes a file stored in a linked repository to which the requesting participant has first access rights to be displayed on the display of terminal device 16 of the requesting participant. Note that this file is an example of a first file.

[0063] If the repository to which the requesting participant has first access rights includes repositories of multiple file management services (i.e., if the requesting participant has first access rights to the repositories of the multiple file management services), the processor 24 causes a list of multiple first files stored in the repositories of the multiple file management services to be displayed on the display of the terminal device 16 of the requesting participant.

[0064] For example, the processor 24 interprets the first access right of the requesting participant that is set for the linked repository in the file management server 10. The processor 24 displays the first file on the display of the terminal device 16 of the requesting participant in a display format that corresponds to the first access right of the requesting participant that is set for the linked repository. Various methods can be used to interpret the first access right. For example, if the third account information of the requesting participant and the first account information of the requesting participant are linked and managed by the file management server 10, the processor 24 recognizes the content of the first access right of the requesting participant by inquiring of the file management server 10 about the content of the first access right of the requesting participant who logged in to the linked server 14 using the third account information. In addition, if the activity and the participants are managed by linking first account information or common account information to activity identification information for identifying the activity to which the participant has requested access, the processor 24 may recognize the content of the first access right of the requesting participant by sending the first account information or the common account information to the file management server 10 and inquiring of the file management server 10 about the content of the first access right of the requesting participant.

[0065] The processor 24 may change the first access right of each participant to the repository. In response to the change, the first access right of each participant in the file management server 10 may be changed. When the first access right is changed, the processor 24 may transmit information indicating that the first access right of the participant will be changed to the terminal device 16 of the participant or administrator whose first access right is to be changed. If the participant or administrator allows the change, the processor 24 may change the first access right of the participant, but if the participant or administrator does not allow the change, the processor 24 may not change the first access right of the participant. The first access right in the file management server 10 may not be changed, and only the first access right when using the repository via the link server 14 may be changed.

[0066] The processor 24 may also associate a messaging service to which at least one participant has a second access right with the activity. For example, the processor 24 associates a channel to which at least one participant has a second access right with the activity. The processor 24 associates, for each activity, an activity with a channel of the messaging service associated with the activity and manages the 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 the activity, and stores and manages this information in the memory 22.

[0067] The processor 24 may cause a file sent to a linked messaging service to which the requesting participant has the second access right to be displayed in a list together with the first file on the display of the terminal device 16 of the requesting participant. The file is an example of a second file. For example, the processor 24 causes a list of the second file sent to the linked channel to be displayed together with the first file on the display.

[0068] The processor 24 may list the second file in the same display area as the first file on the display so that the second file can be identified as a file sent to the linked messaging service.

[0069] The processor 24 may also list messages sent to an integrated messaging service to which the requesting participant has second access rights, along with the above-mentioned first file, on the display of the requesting participant's terminal device 16.

[0070] For example, the processor 24 accesses the messaging server 12 that provides a channel of the linked messaging service and interprets the second access right of the requesting participant that is set for the channel of the messaging service. The processor 24 displays the second file on the display of the terminal device 16 of the requesting participant in a display format that corresponds to the second access right of the requesting participant that is set for the channel of the linked messaging service. There are various methods for interpreting the second access right. For example, if the third account information of the requesting participant and the second account information of the requesting participant are linked and managed by the messaging server 12, the processor 24 recognizes the content of the second access right of the requesting participant by inquiring of the messaging server 12 about the content of the second access right of the requesting participant who logged in to the link server 14 using the third account information. In addition, when the activity and the participants are managed by linking second account information or common account information to activity identification information for identifying the activity to which the participant has requested access, the processor 24 may recognize the content of the second access right of the requesting participant by sending the second account information or the common account information to the file management server 10 and inquiring the messaging server 12 about the content of the second access right of the requesting participant.

[0071] The processor 24 may change the second access right of each participant to the channel of the messaging service. In response to the change, the second access right of each participant on the messaging server 12 may be changed. When the second access right is changed, the processor 24 may transmit information indicating that the second access right of the participant will be changed to the terminal device 16 of the participant or administrator who has the second access right to be changed. If the participant or administrator permits the change, the processor 24 may change the second access right of the participant, but if the participant or administrator does not permit the change, the processor 24 may not change the second access right of the participant. The second access right on the messaging server 12 may remain unchanged, and only the second access right when using the message service via the link server 14 may be changed.

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

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

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

[0075] The UI 28 is a user interface and includes at least one of a display and an operation device. The display is a liquid crystal display, an EL display, or the like. The operation device is a keyboard, a mouse, input keys, an operation panel, or the like. The UI 28 may be a UI such as a touch panel that combines a display and an operation device. The UI 28 may also include a microphone and a speaker.

[0076] The memory 30 is a device that configures one or more storage areas for storing data. The 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 the terminal device 16.

[0077] The processor 32 is configured to control the operation of each part of the terminal device 16. The processor 32 may include a memory.

[0078] The repositories included in the file management server 10 will be described below with reference to Fig. 4. Fig. 4 shows the repositories included in each of the file management servers 10A, 10B, ..., 10K. Although not shown in Fig. 4, each file management server 10 includes, for example, a communication device, a UI, a memory, and a processor, and the file management service is provided by the processor.

[0079] The file management server 10A includes repositories 34Aa, 34Ab, . . . , 34Ak. Each repository included in the file management server 10A is realized by a memory included in the file management server 10A.

[0080] The file management server 10B includes repositories 34Ba, 34Bb, . . . , 34Bm. Each repository included in the file management server 10B is realized by a memory included in the file management server 10B.

[0081] The file management server 10K includes repositories 34Ka, 34Kb, . . . , 34Kn. Each repository included in the file management server 10K is realized by a memory included in the file management server 10K.

[0082] As described above, a first access right is set for each repository, and a user having the first access right is permitted to access the repository corresponding to the first access right and use the repository. Note that repositories to which no first access right is set and to which all users are permitted access, and repositories to which a first access right is set and to which all users are permitted access may be formed in the file management server 10.

[0083] The first embodiment will be described in detail below. As an example, the first embodiment will be described below assuming a situation in which a work project is launched as an activity and the project is carried out. For example, an administrator who manages the project and participants who join the project and perform tasks, operations, etc. are involved in the project. 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. Furthermore, the administrator and participants 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.

[0084] The settings at the time of launching a project will be described with reference to Fig. 5. Fig. 5 shows a project settings screen 36. On the settings screen 36, the participants of the project, the messaging service that will be linked to the project, and the file management service that will be linked to the project are set. For example, when project AAA is launched, the participants of project AAA and the services that will be linked to project AAA (i.e., the file management service and the messaging service) are set on the settings screen 36.

[0085] For example, an administrator of project AAA logs in to link server 14 using his / her own terminal device 16 and requests link server 14 to register project AAA. Upon receiving the request, processor 24 of link server 14 displays setting screen 36 on the display of the administrator's terminal device 16. The administrator performs various settings on setting screen 36.

[0086] The administrator inputs information for identifying each participant in project AAA on the setting screen 36, and registers each participant in project AAA. For example, the administrator inputs third account information for each participant on the setting screen 36. The processor 24 of the link server 14 accepts the input third account information for each participant and links the third account information of each participant to activity identification information for identifying project AAA. In this way, each participant is registered in project AAA. In the example shown in FIG. 5, the third account information of each of participants A, B, C, etc. is input, and participants A, B, C, etc. are registered in project AAA. In this way, multiple participants are associated with project AAA, which is an example of an activity.

[0087] Furthermore, the administrator sets, on the setting screen 36, each channel of the messaging service to be linked to Project AAA and a link to each channel. For example, the administrator inputs an address (e.g., a URL) for accessing the channel of the messaging service to be linked to Project AAA. The processor 24 of the link server 14 accepts the input address and associates the input address with the activity identification information of Project AAA. This links the messaging service to Project AAA. More specifically, the channels of the messaging service are linked to Project AAA. In the example shown in FIG. 5 , the address (e.g., a URL) of Channel ML, which is an email mailing list, the address (e.g., a URL) for accessing Channel α1 (e.g., a group chat) provided by Messaging Service α, and the address (e.g., a URL) for accessing Channel β1 (e.g., a group chat) provided by Messaging Service β are input into the setting screen 36. The address of Channel ML, the address of Channel α1, and the address of Channel β1 are associated with Project AAA. This links Channel ML, Channel α1, and Channel β1 to Project AAA.

[0088] Each of the email, messaging service α, and messaging service β is provided by one of messaging servers 12A, 12B, . . . , 12L. One or more of the email, messaging service α, and messaging service β may be provided by the same messaging server 12, or each service may be provided by a different messaging server 12.

[0089] Furthermore, the administrator sets each repository of the file management service to be linked to project AAA and a link to each repository on the setting screen 36. For example, the administrator inputs an address (e.g., a URL) for accessing the repository of the file management service to be linked to project AAA. The processor 24 of the linking server 14 accepts the input address and associates the input address with the activity identification information of project AAA. This causes the file management service to be linked to project AAA. More specifically, the repository of the file management service is linked to project AAA. In the example shown in FIG. 5, an address (e.g., a URL) for accessing repository γ1 provided by file management service γ, an address (e.g., a URL) for accessing repository δ1 provided by file management service δ, and an address (e.g., a URL) for accessing repository ε1 provided by file management service ε are input on the setting screen 36. The addresses of repository γ1, repository δ1, and repository ε1 are associated with project AAA. This allows repositories γ1, δ1, and ε1 to be linked to project AAA.

[0090] Each of the file management services γ, δ, and ε is provided by one of the file management servers 10A, 10B, . . . , 10K. One or more of the file management services γ, δ, and ε may be provided by the same file management server 10, or each service may be provided by a different file management server 10.

[0091] Instead of the administrator of Project AAA setting the links, a person with authority to set the first access rights for each repository on the file management server 10 may set links to each repository, and a person with authority to set the first access rights for each channel on the messaging server 12 may set links to each channel.

[0092] Each participant (e.g., participants A, B, C, etc.) registered on the setting screen 36 may or may not have access rights to each repository linked to Project AAA and each channel linked to Project AAA.

[0093] For example, participant A may have the second access right to channel α1, but participant B may not have the second access right to channel α1. It is conceivable that participant A is registered with the messaging server 12 that provides the messaging service α as a user with the second access right to channel α1, but participant B is not registered with the messaging server 12 that provides the messaging service α as a user with the second access right to channel α1.

[0094] Furthermore, participant A may have the first access right to repository γ1, but participant B may not have the first access right to repository γ1. It is conceivable that participant A is registered in the file management server 10 that provides the file management service γ as a user with the first access right to repository γ1, but participant B is not registered in the file management server 10 that provides the file management service γ as a user with the first access right to repository γ1.

[0095] As described above, each participant is registered in project AAA, and each repository and each channel is linked to project AAA. The processor 24 associates the activity identification information of project AAA, information for identifying each participant in project AAA (e.g., third account information), the address of each repository linked to project AAA, and the address of each channel linked to project AAA, and stores and manages this information in memory 22. The same applies when a project other than project AAA is launched. In this way, the processor 24 associates and manages, for each project, the project, each participant in the project, each repository linked to the project, and each channel linked to the project.

[0096] In the example shown in FIG. 5, multiple channels and multiple repositories are linked to Project AAA, but this is merely an example. The number of channels linked to Project AAA may be one, and the number of repositories linked to Project AAA may be one. Also, one or more repositories may be linked to Project AAA, and no channels may be linked to Project AAA. Similarly, one or more channels may be linked to Project AAA, and no repositories may be linked to Project AAA.

[0097] The following describes the process when a participant requests access to an activity. As an example, assume that participant A of project AAA requests access to project AAA using his / her own terminal device 16A.

[0098] For example, participant A uses his / her terminal device 16A to send his / her third account information to the link server 14, requesting login to the link server 14 and access to Project AAA. Because participant A's third account information is registered in the link server 14, the processor 24 of the link server 14 permits participant A to log in to the link server 14. Furthermore, as described above, because participant A is linked to Project AAA, the processor 24 permits participant A to access Project AAA. In this case, the processor 24 displays, on the display of participant A's terminal device 16A, a first file stored in a repository to which the requesting participant A has first access rights and which is linked to Project AAA. Furthermore, the processor 24 displays, on the display of participant A's terminal device 16A, a message sent to a channel of a messaging service to which participant A has second access rights and which is linked to Project AAA, together with the first file.

[0099] An example of these displays is shown in Figure 6. Figure 6 shows a screen 38. Screen 38 is a screen displayed on the display of participant A's terminal device 16A. Screen 38 includes display areas 40 and 42. Processor 24 forms display areas 40 and 42 on the display.

[0100] The display area 40 is an area where files are displayed. For example, the processor 24 displays a list of files stored in a repository to which participant A has first access right and which is linked to project AAA in the display area 40. For example, each file is displayed according to a timeline notation. That is, each file is displayed in chronological order according to the date and time when the file was created, the date and time when the file was stored in the repository, or the date and time when the file was updated. For example, each file is displayed in order from top to bottom, bottom to top, left to right, or right to left according to the date and time. Of course, each file may be displayed in a non-chronological order. For example, the file may be displayed in a position specified by the participant or according to the file name.

[0101] 6, a plurality of files stored in different repositories are displayed together in the display area 40. A filter function may be used to display only files stored in a specific repository, or files may be displayed for each first access right, or files may be displayed for each repository.

[0102] The processor 24 may display files that do not fit in the display area 40 by moving the display area 40 vertically or horizontally (for example, by scrolling).

[0103] The display area 42 is an area where messages are displayed. For example, the processor 24 displays a list of messages sent to a channel to which participant A has second access rights and which is linked to project AAA in the display area 42. For example, each message is displayed according to a timeline notation. That is, each message is displayed in order according to the date and time when the message was sent to the channel. Even if each message was sent to a different channel, each message is displayed in order according to the date and time when the message was sent to the channel. For example, each message is displayed in order from top to bottom or bottom to top according to the date and time. Note that information for identifying the participant who sent the message (for example, a name, a nickname, an ID, an image such as an icon, etc.) is associated with the message and displayed in the display area 42. For example, the information is displayed near the message.

[0104] 6, multiple messages sent to different channels are displayed mixed together in the display area 42. Only messages sent to a specific channel may be displayed using a filter function, or messages may be displayed for each second access right, or messages may be displayed for each channel. Note that when a voice call such as a telephone call is used as a messaging service and voice is exchanged between participants, the voice may be converted into a character string, and the character string may be displayed as a message in the display area 42.

[0105] In addition, when a participant operates on a file in display area 40 (for example, when a file is edited or moved), or when an operation is performed to upload a file to display area 40, processor 24 may display a message in display area 42 indicating that the operation has been performed.

[0106] The processor 24 may display a message that does not fit in the display area 42 within the display area 42 by moving the display area 42 up and down or left and right (for example, by scrolling).

[0107] When a participant other than participant A (e.g., participant B, C, etc.) accesses project AAA, a screen similar to screen 38 is displayed on the display of the terminal device 16 of the other participant. For example, the display of terminal device 16B of participant B displays files stored in a repository to which participant B has first access rights and which is linked to project AAA, and messages sent to a channel to which participant B has second access rights and which is linked to project AAA. The same is true for participant C.

[0108] Alternatively, the linked server 14 itself may provide a messaging service. In this case, an input field 44 for sending a message to the messaging service is displayed on the screen 38. When a message is entered in the input field 44 and an instruction to send is given, the processor 24 displays the entered message in the display area 42. The processor 24 also sends the entered message to other participants accessing Project AAA. Note that when a message is replied to a message sent to a channel linked to Project AAA using the messaging service provided by the linked server 14 itself, the replied message may be reflected in the channel to which the reply was sent.

[0109] Each file and each message shown in FIG. 6 will be explained in detail.

[0110] Files F1 and F2 are files stored in repository γ1 of file management service γ that is linked to project AAA. Files F3 and F4 are files stored in repository δ1 of file management service δ that is linked to project AAA. File F5 is a file stored in repository ε1 of file management service ε that is linked to project AAA. File F6 is a file attached to message M5.

[0111] Participant A has first access rights to repositories γ1 and δ1, but does not have first access rights to repository ε1. In other words, participant A has first access rights to files F1 to F4, but does not have first access rights to file F5. In this case, processor 24 displays files F1 to F4 in a list in display area 40, but does not display file F5. For convenience of explanation, file F5 is shown in FIG. 6, but file F5 is not displayed on screen 38. Furthermore, file F6 is a file attached to message M5, and is displayed in display area 40. For example, images (e.g., icons) representing each of files F1 to F4 and F6 are displayed. Attaching files will be described in detail later.

[0112] The processor 24 may change the display mode of a file depending on the repository in which the file is stored. For example, the processor 24 changes the display color, size, shape, pattern, etc. of the file depending on the repository in which the file is stored. In the example shown in Figure 6, files F1 and F2 are displayed in a color (e.g., light blue) corresponding to file management service γ, files F3 and F4 are displayed in a color (e.g., green) corresponding to file management service δ, and file F6 is displayed in a color (e.g., orange) corresponding to a message attachment.

[0113] Message M1 is a message sent to a user registered in a channel ML (i.e., a mailing list ML) linked to Project AAA. Messages M2 and M6 are messages sent to channel α1 of messaging service α linked to Project AAA. Messages M3, M4, and M5 are messages sent to channel β1 of messaging service β linked to Project AAA. Message M5 has file F6 attached.

[0114] Participant A has second access rights to channel ML, which is a mailing list, and channel β1 of messaging service β, but does not have second access rights to channel α1 of messaging service α. That is, participant A has second access rights to messages M1, M3, M4, and M5, but does not have second access rights to messages M2 and M6. In this case, processor 24 displays messages M1, M3, M4, and M5 in a list in display area 42, but does not display messages M2 and M6. For convenience of explanation, messages M2 and M6 are shown in FIG. 6, but messages M2 and M6 are not displayed on screen 38.

[0115] Processor 24 may change the display mode of a message depending on the channel through which the message was sent. For example, processor 24 changes the display color, size, shape, and pattern of the entire message and its frame, as well as the display color, size, font type, etc. of each character included in the message depending on the channel through which the message was sent. In the example shown in Fig. 6, the frame and characters of message M1 are displayed in a color (e.g., purple) corresponding to mailing list M, and the frames and characters of mailing lists M3, M4, and M5 are displayed in a color (e.g., red) corresponding to messaging service β.

[0116] 6, in response to a request from participant A for access to project AAA, processor 24 displays a list of files (e.g., files F1 to F4) stored in a repository (e.g., repositories γ1 and δ1) to which participant A has first access right in display area 40. For example, processor 24 displays files F1 to F4 together in display area 40. Note that files F1 to F4 are examples of first files.

[0117] When participant A has first access rights to the repositories of multiple file management services, processor 24 displays a list of multiple files stored in the repositories of the multiple file management services in display area 40. In the example shown in Fig. 6, participant A has first access rights to repository γ1 of file management service γ and repository δ1 of file management service δ, and processor 24 displays a list of files (e.g., files F1 to F4) stored in repositories γ1 and δ1, respectively, in display area 40.

[0118] The processor 24 may list files sent to a messaging service to which participant A has second access rights, together with the first file (i.e., a file stored in the repository of the file management service) in the display area 40. In the example shown in FIG. 6, a message M5 to which file F6 is attached is sent to a channel β1 to which participant A has second access rights. In this case, the processor 24 displays the message M5 in the display area 42 and also displays the file F6 together with the first file in the display area 40. The file F6 is an example of a second file.

[0119] Processor 24 displays file F6 attached to message M5 in display area 40 so that it can be identified as a file sent to a messaging service. As described above, for example, file F6 is displayed in a color (e.g., orange) that corresponds to the message attachment. This color may also correspond to the messaging service.

[0120] When a file F6 is specified by participant A, the processor 24 may display the message M5 to which the specified file F6 was attached in a manner that indicates the message. For example, the processor 24 may display the message M5 in a conspicuous manner so that it can be distinguished from other messages. Specifically, the processor 24 may decorate the message M5, may enlarge the message M5, or may display the message M5 in a specific color.

[0121] If no messaging services are linked to Project AAA, messages exchanged via each messaging service will not be displayed on screen 38. Similarly, if no file management services are linked to Project AAA, files stored in the repositories of each file management service will not be displayed on screen 38.

[0122] If a file stored in a repository linked to Project AAA is deleted, the deleted file will no longer be displayed in the display area 40. Furthermore, if the first access right for a file is changed in the file management service, the file will be displayed in the display area 40 or will no longer be displayed in the display area 40 in accordance with the changed first access right. Furthermore, if a file stored in a repository linked to Project AAA is copied and transmitted to and stored in linked server 14, even if the file stored in the repository is deleted, the copied file will be displayed in the display area 40 as long as it is stored in linked server 14. Whether or not to copy a file is set in advance by an administrator, etc.

[0123] Similarly, if a message sent to a channel linked to Project AAA is deleted, the deleted message will no longer be displayed in display area 42. Furthermore, if the second access right for a channel is changed in the messaging service, the message will be displayed in display area 42 or will no longer be displayed in display area 42 in accordance with the changed second access right. Furthermore, if a message sent to a channel linked to Project AAA is copied, sent to linkage server 14, and stored therein, even if the message is deleted from the channel, the message will be displayed in display area 42 as long as the copied message is stored in linkage server 14. Whether or not to copy a message is set in advance by an administrator, etc.

[0124] The process when a participant requests access to an activity is described in more detail below.

[0125] For example, participant A has first access rights to repositories γ1, δ1, and ε1, and second access rights to channels ML, α1, and β1. Therefore, participant A is permitted to access all repositories and all channels linked to project AAA. An example of participant A is a participant with a certain level of authority, such as a project AAA supervisor, person in charge, leader, or manager.

[0126] Furthermore, participant B has a first access right to repositories δ1 and ε1, and a second access right to channels ML and α1. Participant B does not have a first access right to repository γ1, and does not have a second access right to channel β1. Therefore, participant B is permitted to access repositories δ1 and ε1 and channels ML and α1, but is not permitted to access repository γ1 and channel β1. For example, a participant other than the participants with a certain level of authority described above (for example, a general participant who does not have such authority) is an example of participant B.

[0127] For example, repository γ1 is a repository exclusively for participants with a certain level of authority (e.g., participant A), and channel β1 is a channel exclusively for participants with a certain level of authority. Repositories δ1 and ε1 are repositories to which all participants in project AAA are permitted to access, and channel ML and α1 are channels to which all participants in project AAA are permitted to access. In other words, all participants, including participants with a certain level of authority (e.g., participant A) and participants without a certain level of authority (e.g., participant B), are permitted to access repositories δ1 and ε1 and channels ML and α1.

[0128] 7 shows a screen 38A that is displayed when participant A requests access to project AAA. Screen 38A includes display areas 40A, 42A, and 46A.

[0129] The processor 24 displays a list of files stored in the repository linked to the project AAA in the display area 40A. The files displayed in the display area 40A are the same as the files displayed in the display area 40 shown in FIG.

[0130] Processor 24 displays a list of messages sent to channels linked to Project AAA in display area 42A. The messages displayed in display area 42A are the same as the messages displayed in display area 42 shown in FIG.

[0131] The processor 24 displays in the display area 46A a list of files stored in a repository to which participant A has access rights, but which are stored in a repository different from the repository linked to project AAA. The files displayed in the display area 46A are an example of third files. For example, the display area 46A displays files stored in participant A's personal repository. As shown in FIG. 7, the processor 24 distinguishes between files stored in a repository linked to project AAA (i.e., first files) and files stored in a repository to which participant A has access rights, but which is different from the repository linked to project AAA (i.e., third files), and displays these files in a list on the display.

[0132] For example, the address of the repository in which the file displayed in the display area 46A is stored is set by participant A. FIG. 8 shows a screen 48 for this setting. The screen 48 is displayed on the display of participant A's terminal device 16A. In the example shown in FIG. 8, the addresses of the local PC, drive ζ, and share η are input by participant A. Note that the local PC, drive ζ, and share η are examples of repositories. The local PC is the terminal device 16A used by participant A, and the address of a storage area (e.g., a folder, etc.) formed in the memory 22 of the terminal device 16 is input as the address of the local PC. Drives ζ and η are repositories to which participant A has first access rights.

[0133] The files stored in each repository set on the screen 48 are displayed in the display area 46A. In the example shown in Fig. 7, files F10, F11, F12, F13, ... are displayed in the display area 46A. For example, files F10 and F11 are files stored in the local PC (i.e., terminal device 16A), and files F12 and F13 are files stored in drive ζ. The files stored in drive η cannot be displayed in the display area 46A, and the files stored in drive η can be displayed in the display area 46A by scrolling the display area 46A vertically or horizontally.

[0134] The processor 24 may switch between displaying and hiding the display area 46A in accordance with an instruction from participant A to switch the display.

[0135] The processor 24 may associate information for identifying the file management service in which the file is stored with the file and display the information. The information for identifying the file management service may be, for example, a character string, an image, or a graphic indicating the file management service. For example, files F1 and F2 stored in repository γ1 are displayed with a badge indicating file management service γ (for example, an image indicating γ). Files F3 and F4 stored in repository δ1 are displayed with a badge indicating file management service δ (for example, an image indicating δ). File F5 stored in repository ε1 is displayed with a badge indicating file management service ε (for example, an image indicating ε). In this way, information indicating which file management service the file originates from is displayed.

[0136] 7, when a plurality of files stored in different repositories are displayed together in the display area 40A, the processor 24 displays each file with information such as a badge indicating which file management service the file originates from. Also, when the participant A instructs the display of information such as a badge, the processor 24 may display the information such as a badge.

[0137] The processor 24 may associate information indicating that the files F1 and F2 are files that are permitted to be accessed only by participants with a certain level of authority or higher with the files F1 and F2 and display the information. The information may be, for example, a character string, an image, or a graphic. In the example shown in FIG. 7, a badge "Mgr" (for example, an image representing "Mgr") is an image indicating that only participants with a certain level of authority or higher are permitted to access the files, and the badge "Mgr" is displayed attached to the files F1 and F2.

[0138] The processor 24 may associate information for identifying the messaging service of the channel to which the message was sent with the message and display it. The information for identifying the messaging service is, for example, a character string, an image, or a graphic indicating the messaging service. For example, a message M1 sent to channel ML is displayed with a badge indicating a mailing list (e.g., an image representing M). Messages M2 and M6 sent to channel α1 are displayed with a badge indicating messaging service α (e.g., an image representing α). Messages M3, M4, and M5 sent to channel β1 are displayed with a badge indicating messaging service β (e.g., an image representing β). In this way, information indicating which messaging service the message originates from is displayed.

[0139] For example, as shown in Fig. 7, when a plurality of messages sent to different channels are displayed in the display area 42A, the processor 24 displays each message with information such as a badge indicating which messaging service the message originates from. Also, when the participant A instructs to display information such as a badge, the processor 24 may display the information such as a badge.

[0140] The processor 24 may associate information indicating that messages M3, M4, and M5 are messages that are permitted to be accessed only by participants with a certain level of authority with the messages M3, M4, and M5, and display the information. The information may be, for example, a character string, an image, or a graphic. In the example shown in FIG. 7, the badge "Mgr" is an image indicating that only participants with a certain level of authority are permitted to access the messages, and the badge "Mgr" is displayed attached to the messages M3, M4, and M5.

[0141] (Switch display) The following describes how to switch the display of files and messages: For example, files and messages are switched by a filter function based on the authority of the participants.

[0142] FIG. 9 shows a screen 50 for setting a file filter function. When participant A issues an instruction to display screen 50 using terminal device 16A, processor 24 displays screen 50 on the display of terminal device 16A. Types of filter functions include "All," "Mgr only," and "General only." The "All" filter function displays all files stored in repositories linked to Project AAA. The "Mgr only" filter function displays files stored in repositories linked to Project AAA that are accessible only to participants with a certain level of authority. The "General only" filter function displays files stored in repositories linked to Project AAA that are accessible only to participants who do not have a certain level of authority. When participant A sets a filter function on screen 50, processor 24 displays files according to the settings.

[0143] 10 shows a screen 38A after the file filter function has been executed. Here, as an example, the filter function "Mgr only" is set. In this case, the processor 24 displays in the display area 40A only files (e.g., files F1 and F2) stored in a repository (e.g., repository γ1) that is linked to project AAA and to which only participants with a certain level of authority are permitted to access. Note that when the filter function is executed, information such as a badge indicating the file management service γ may or may not be displayed attached to the files F1 and F2.

[0144] The processor 24 may store a file attached to a message (e.g., file F5 attached to message M5) in a specific repository. The specific repository may be designated by, for example, a participant or may be predetermined. When the file attached to the message is stored in the specific repository, the processor 24 may switch the display of the file according to a first access right set for the specific repository.

[0145] As with files, the display of messages may be switched using a filter function. For example, a filter function for messages is set on a screen similar to screen 50. FIG. 11 shows screen 38A after the filter function for messages has been executed. Here, as an example, the filter function "Mgr only" is set. In this case, processor 24 displays, in display area 42A, only messages (e.g., messages M2 and M6) sent to a channel (e.g., channel α1) that is linked to project AAA and to which only participants with a certain level of authority are permitted to access. Note that when the filter function is executed, information such as a badge indicating messaging service α may or may not be displayed attached to messages M2 and M6.

[0146] The filter function may be executed only on files, only on messages, or on both files and messages. In the example shown in FIG. 11, the filter function is also executed on files, but the filter function does not have to be executed on files. Different filter functions may be executed for files and messages. For example, the filter function "Mgr only" may be executed on files, and the filter function "All" may be executed on messages.

[0147] The processor 24 may associate information for identifying the participant who sent the message (for example, an image such as an icon, or a character string such as a name, nickname, or ID) with information such as a badge indicating the authority of the participant, and display the information such as the badge in the display area 42. For example, the processor 24 may display information such as a badge indicating the authority of the participant near an image such as an icon representing the participant. As another example, the processor 24 may display a list of participants in a specific area (for example, an upper or lower area) in the display area 42, or may display an image such as a button for transitioning to a screen displaying the list of participants in a specific area. The processor 24 may display information such as a badge indicating the authority of each participant in the list of participants.

[0148] The display of files and messages may be switched by tabs, as shown in Figure 12.

[0149] 12, the tab for file management service δ is selected, and only files F3 and F4 stored in repository δ1 are displayed in display area 40A. When the tab for file management service γ is selected, only files F1 and F2 stored in repository γ1 are displayed in display area 40A. When the tab for file management service ε is selected, only file F5 stored in repository ε1 is displayed in display area 40A.

[0150] 12, the messaging service α tab is selected, and only messages M2 and M6 sent to channel α1 are displayed in the display area 42A. When the mailing list ML tab is selected, only message M1 sent to channel ML is displayed in the display area 42A. When the messaging service β tab is selected, only messages M3, M4, and M5 sent to channel β1 are displayed in the display area 42A.

[0151] 13 shows a screen 38B that is displayed when participant B requests access to project AAA. Screen 38B includes display areas 40B, 42B, and 46B.

[0152] The processor 24 displays a list of files stored in a repository linked to project AAA in the display area 40A. Unlike participant A, participant B is not a participant with a certain level of authority, but a general participant. Therefore, the processor 24 displays a list of files (e.g., files F3, F4, and F5) stored in a repository linked to project AAA that is accessible only to participants who do not have a certain level of authority in the display area 40B. The processor 24 does not display files (e.g., files F1 and F2) stored in a repository linked to project AAA that is accessible only to participants who have a certain level of authority in the display area 40B. For convenience of explanation, files F1 and F2 are shown in dashed lines in FIG. 13, but files F1 and F2 are not displayed in the display area 40B. Files F1 and F2 are an example of a fourth file.

[0153] File F6 is a file attached to a message, and therefore may be displayed in display area 40B. Note that, as will be described later, message M5 is a message that only participants with a certain level of authority are permitted to access, and therefore file F6 attached to message M5 may also be a file that only participants with a certain level of authority are permitted to access. In this case, file F6 is not displayed in display area 40B.

[0154] Processor 24 may display information suggesting the existence of a fourth file (eg, files F1 and F2) in display area 40B.

[0155] For example, when the files are displayed side by side in display area 40B according to the timeline notation, processor 24 does not display files F1 and F2 themselves in display area 40B, but instead reserves space where files F1 and F2 should be displayed according to the display conditions, and does not display other files in that space. In the example shown in Figure 13, other files are not displayed where files F1 and F2 should be displayed.

[0156] As another example, the processor 24 may display files F1 and F2 but not accept participant B's operations on files F1 and F2. For example, even if participant B performs an operation to open files F1 and F2, such as clicking on them, or to delete files F1 and F2, or to move files F1 and F2, the processor 24 does not accept the operation and does not open, delete, or move files F1 and F2. When displaying files F1 and F2, the processor 24 may display files F1 and F2 in a way that distinguishes them from other files. For example, the processor 24 may display images representing files F1 and F2 smaller than the other files, display images representing files F1 and F2 in a different color than the images representing the other files, or display images representing files F1 and F2 in a lighter color. The processor 24 may display files F1 and F2 so that they are less noticeable than the other files.

[0157] In response to a request from participant B, processor 24 may grant participant B access rights to a fourth file (e.g., files F1 and F2), or may request a person with authority to grant access rights, such as an administrator of project AAA, to grant the access rights to participant B. If the person with authority to grant access rights permits granting the access rights to participant B, processor 24 grants the access rights to participant B. If the person with authority to grant access rights does not permit granting the access rights to participant B, processor 24 does not grant the access rights to participant B. When the access rights are granted to participant B, processor 24 displays files F1 and F2 in display area 40B, accepts participant B's operations on files F1 and F2, and performs processing according to the operations (e.g., file opening, deletion, movement, etc.).

[0158] The processor 24 displays a list of messages sent to channels linked to Project AAA in the display area 42B. Because participant B is a general participant, the processor 24 displays a list of messages (e.g., M1, M2, and M6) sent to channels linked to Project AAA that are accessible only to participants who do not have a certain level of authority in the display area 42B. The processor 24 does not display messages (e.g., messages M3, M4, and M5) sent to channels linked to Project AAA that are accessible only to participants who have a certain level of authority in the display area 42B. In the example shown in FIG. 13, the contents of messages M3, M4, and M5 are not displayed, and only frames displaying messages M3, M4, and M5 are displayed, or messages M3, M4, and M5 are displayed in a solid state. Messages M3, M4, and M5 may not be displayed at all.

[0159] In response to a request from participant B, the processor 24 may grant participant B access rights to messages M3, M4, and M5, or may request a person with authority to grant access rights, such as an administrator of project AAA, to grant the access rights to participant B. If the person with authority to grant access rights authorizes granting the access rights to participant B, the processor 24 grants the access rights to participant B. If the person with authority to grant access rights does not authorize granting the access rights to participant B, the processor 24 does not grant the access rights to participant B. Once the access rights are granted to participant B, the processor 24 displays the contents of messages M3, M4, and M5 in the display area 42B.

[0160] Processor 24 displays in display area 46B a list of files stored in a repository to which participant B has access rights, which are different from the repository linked to project AAA. The files displayed in display area 46B are an example of third files. For example, display area 46B displays files stored in participant B's personal repository. As described with reference to FIG. 8, the repository in which the files displayed in display area 46B are stored is set by participant B, and the files are displayed in display area 46B according to that setting.

[0161] The first access right may be set for each file, and the second access right may be set for each message.

[0162] For example, the first access right to file F1 is not granted to participant B, but is granted to participant A. In this case, participant A is permitted to access file F1, and file F1 is displayed in display area 40A of participant A's screen 38A. Participant B is not permitted to access file F1, and file F1 is not displayed in display area 40B of participant B's screen 38B. The same applies to other files. In this way, the first access right may be set individually for each file.

[0163] For example, the second access right for message M1 is not granted to participant B but is granted to participant A. In this case, participant A is permitted to access message M1, and message M1 is displayed in display area 42A of participant A's screen 38A. Participant B is not permitted to access message M1, and message M1 is not displayed in display area 42B of participant B's screen 38B. The same applies to other messages. In this way, the second access right may be set individually for each message.

[0164] Furthermore, a message sent to a mailing list whose destinations include only participants with a certain level of authority or more may be displayed only on the displays of the terminal devices 16 of participants with the certain level of authority or more. For example, such a message may be displayed in the display area 42 on the screen 38A of participant A, but not in the display area 42 on the screen 38B of participant B.

[0165] (Granting access rights to files) When a message displayed in a display area (e.g., display area 42A, 42B) displaying a message sent to a messaging service linked to Project AAA is associated with a file (i.e., a third file) stored in a repository to which a participant (e.g., participant A, B) has access rights, but which is different from the repository linked to Project AAA, the processor 24 may grant access rights to the associated third file to other participants who have second access rights to the message associated with the third file. In this case, the processor 24 displays the associated third file on the display of the terminal device 16 of the other participant who has been granted access rights to the third file. For example, the processor 24 displays the third file in the display area 40 where files are displayed.

[0166] The process of granting access rights to the third file to other participants will be described below with reference to Fig. 14. Fig. 14 shows a screen 38A displayed on the display of the terminal device 16A of participant A. Here, as an example, participant A associates the third file with a message.

[0167] As described above, files (i.e., third files) stored in a repository to which participant A has access rights and which are different from the repository linked to project AAA are displayed in display area 46A. In the example shown in Fig. 14, files F10 to F13, which are examples of third files, are displayed in display area 46A.

[0168] For example, when participant A drags file F10 displayed in display area 46A to message M2 displayed in display area 42A and drops it on message M2, as indicated by reference numeral 52, processor 24 associates file F10 with message M2. Processor 24 grants access rights to the associated file F10 to other participants who have second access rights to message M2 with which file F10 is associated. For example, if participant B has second access rights to message M2, processor 24 displays file F10 in display area 40B of participant B's screen 38B. In this way, file F10 is displayed to other participants (e.g., participant B) who have second access rights to message M2, and file F10 is shared between participant A and the other participants. Processor 24 also displays file F10 in display area 40A of screen 38A of participant A, who associated file F10 with message M2.

[0169] Another process for granting access rights to the third file to other participants will be described below with reference to Fig. 15. Fig. 15 shows a screen 38A. Here, as an example, access rights to the third file designated by participant A are granted to other participants.

[0170] For example, when participant A designates file F10 displayed in display area 46A and gives an instruction to display a menu of permissions (for example, by right-clicking), processor 24 displays menu 54 on screen 38A. Menu 54 displays a list of permissions of other participants to whom access rights to file F10 are granted. When participant A selects a permission from menu 54, processor 24 grants access rights to file F10 to other participants who have the selected permission, and displays file F10 to the other participants.

[0171] For example, if the authority "All" is selected by participant A, the processor 24 grants access rights to file F10 to all participants in project AAA and displays file F10 to all participants. For example, file F10 is displayed in display area 40B of participant B's screen 38B. The same applies to participants other than participant B. Furthermore, as indicated by reference numeral 56, file F10 is also displayed in display area 40A of participant A's screen 38A.

[0172] When the authority "Mgr" is selected by participant A, processor 24 grants access to file F10 only to participants with a certain level of authority or higher, and displays file F10 only to participants with the certain level of authority or higher. For example, participant B is not a participant with a certain level of authority or higher, and therefore file F10 is not displayed in display area 40B of screen 38B.

[0173] Furthermore, when access rights to file F10 are granted to other participants in accordance with instructions from participant A, processor 24 may display a message indicating this in a display area (e.g., display areas 42A, 42B) in which messages sent to channels linked to project AAA are displayed. In the example shown in FIG. 15, message 58 stating "Participant A has uploaded a file" is displayed in display area 42A. Message 58 is also displayed in display areas 42 of other participants. Message 58 may be displayed to other participants who have been granted access rights to file F10, but may not be displayed to participants who have not been granted access rights to file F10.

[0174] Hereinafter, another process for granting access rights to the third file to other participants will be described with reference to Fig. 16. Fig. 16 shows a screen 38A. Here, as an example, access rights to the third file designated by participant A are granted to other participants.

[0175] For example, when participant A instructs display area 40A to execute a filter function based on the authority, processor 24 displays a file in display area 40A in accordance with the authority set by the filter function. In this state, when participant A drags and drops a file displayed in display area 46A into display area 40A, processor 24 grants access rights to the file to other participants who have the authority set by the filter function.

[0176] For example, if participant A selects the authority "Mgr" in the filter function, the processor 24 displays in the display area 40A only files that are accessible only to participants with that authority. At this time, the display area 40A is in a state where only files that are accessible only to participants with the authority "Mgr" are displayed. When participant A drags and drops file F10 into the display area 40A in this state, as indicated by the reference numeral 60, the processor 24 grants access rights to file F10 to other participants with the authority "Mgr." In other words, the processor 24 displays file F10 in the display area 40 of the screen 38 of the other participant.

[0177] As yet another example, if participant A posts a file displayed in display area 46A to a channel of a messaging service linked to Project AAA or sends the file as an attachment to an email, processor 24 may grant access to the file to other participants who have a second access right to the channel.

[0178] Second Embodiment The second embodiment will be described below. The information processing system according to the second embodiment has the same configuration as the information processing system according to the first embodiment, and the file management server 10, messaging server 12, linking server 14, and terminal device 16 according to the second embodiment each have the same configuration as the file management server 10, messaging server 12, linking server 14, and terminal device 16 according to the first embodiment.

[0179] In the second embodiment, when a participant operates on a message displayed in the display area 42, the processor 24 displays a file (hereinafter referred to as an "associated file") related to the operated message in the display area 40 in accordance with the operation, so as to indicate the file.

[0180] Conversely, when a participant operates on a file displayed in display area 40, processor 24 displays a message related to the operated file (hereinafter referred to as a "related message") in display area 42 in response to the operation.

[0181] In the second embodiment, the display area 40 is an example of a second display area, and the display area 42 is an example of a first display area.

[0182] (Process to display related files) The process of displaying related files in response to an operation on a message will be described in detail below.

[0183] Related files include, for example, a file attached to the operated message, a file to be operated on indicated by the operated message, a file attached to a specific message related to the operated message, or a file to be operated on indicated by a specific message.

[0184] The specific message may be, for example, a message to which the manipulated message is replied, a message from which the manipulated message is replied, or a message on the same topic as the manipulated message. For example, multiple messages containing a common specific word or a common hashtag may be determined to be messages on the same topic, multiple messages exchanged using the same messaging service may be determined to be messages on the same topic, or multiple messages exchanged using the same channel may be determined to be messages on the same topic. Furthermore, messages on the same topic as the manipulated message may be identified using publicly known technology such as that described in Japanese Patent Application Laid-Open No. 2018-60508.

[0185] A specific example will be described with reference to Fig. 17. Fig. 17 shows a screen 38. Similar to the screen 38 according to the first embodiment described above (see Fig. 6), the screen 38 includes a display area 40 in which files stored in a repository linked to the activity are displayed, and a display area 42 in which messages sent to a channel linked to the activity are displayed. In the second embodiment, as in the first embodiment, the activity is, for example, Project AAA.

[0186] For example, if a participant selects message M3 displayed in display area 42 by clicking, tapping, speaking, etc., processor 24 displays related files in display area 40 to show the related files of the selected message M3.

[0187] For example, files F2, F5, and F6 are examples of related files. The processor 24 displays files F2, F5, and F6 in the display area 40 so that files F2, F5, and F6 are identified as related files of message M3. For example, the processor 24 displays files F2, F5, and F6 in the display area 40 so that they stand out and can be distinguished from other files other than files F2, F5, and F6. Specifically, the processor 24 may highlight files F2, F5, and F6, decorate files F2, F5, and F6, enlarge and display files F2, F5, and F6, or display files F2, F5, and F6 in a specific color.

[0188] The display area 40 is an area that can be moved, such as by scrolling, and a file may be displayed in the display area 40 or may no longer be displayed in the display area 40 depending on the scrolling of the display area 40.

[0189] Similarly, the display area 42 is an area that can be moved, such as by scrolling, and a message may be displayed in the display area 42 or may no longer be displayed in the display area 42 depending on the scrolling of the display area 42.

[0190] For example, as shown in FIG. 18 , a scroll bar 70 is displayed in the display area 40, and a scroll bar 72 is displayed in the display area 42. The scroll bar 70 has a function of scrolling the display area 40 vertically. The scroll bar 72 has a function of scrolling the display area 42 vertically. A participant operates the scroll bar 70 to scroll the display area 40 vertically, thereby displaying a file outside the display area 40 within the display area 40, or moving a file within the display area 40 out of the display area 40 so that it is no longer displayed within the display area 40. Similarly, a participant operates the scroll bar 72 to scroll the display area 42 vertically, thereby displaying a message outside the display area 42 within the display area 40, or moving a message within the display area 42 out of the display area 42 so that it is no longer displayed within the display area 42. Note that the display areas 40 and 42 may be scrolled both vertically and horizontally, or may be scrolled only horizontally.

[0191] In the example shown in FIG. 18, files F30 to F36 are displayed within the display area 40, and files F2, F5, and F6, which are related files of message M3, are not displayed within the display area 40. In other words, files F2, F5, and F6 cannot fit within the display area 40 and are arranged outside the display area 40. In this state, when a participant selects message M3 displayed within the display area 42, the processor 24 scrolls the display area 40 so that files F2, F5, and F6, which are related files of message M3, are displayed within the display area 40. In other words, the processor 24 scrolls the display area 40 so that files F2, F5, and F6, which are outside the display area 40, are displayed within the display area 40.

[0192] 19 shows the display area 40 after scrolling. Files F2, F5, and F6, which are related files of message M3, are displayed in the display area 40 after scrolling. By scrolling the display area 40 in this manner, files F2, F5, and F6, which are related files of the selected message M3, are displayed in the display area 40. As described with reference to FIG. 17, the processor 24 displays files F2, F5, and F6 in the display area 40 so that they stand out and can be distinguished from other files other than files F2, F5, and F6.

[0193] Note that if files F2, F5, and F6, which are related files, cannot fit together within display area 40 even when display area 40 is scrolled (i.e., if files F2, F5, and F6 are not displayed together within display area 40), processor 24 may change the positions of files F2, F5, and F6 within display area 40, thereby displaying files F2, F5, and F6 together within display area 40. If selection of message M3 is deselected, processor 24 may return the positions of files F2, F5, and F6 to their original positions.

[0194] As another example, when message M3 is selected by a participant in the state shown in FIG. 18, processor 24 may change the position of files F2, F5, and F6, which are related files of message M3, within display area 40 without scrolling display area 40, and display files F2, F5, and F6 together within display area 40.

[0195] Processor 24 may display at least certain of the associated files of the selected message in display area 40 .

[0196] A specific related file is, for example, the file most related to the selected message, the oldest or newest file among the related files when files are displayed in a timeline, or the file located chronologically at the same position as the selected message when files and messages are displayed in a timeline. A most related file is, for example, a file attached to the selected message, or a file that contains a character string specifying a file when the selected message contains that character string. For example, if the number of related files for the selected message is equal to or greater than a threshold, processor 24 displays at least a specific related file among the related files in display area 40.

[0197] Processor 24 may change the brightness of the highlighting of the associated file, the decoration of the associated file, the size of the associated file, or the color of the associated file depending on the relevance between the selected message and the file. For example, the relevance of the file attached to the selected message is highest, the relevance of the file to be operated indicated by the selected message is second highest, the relevance of the file attached to a specific message related to the selected message is third highest, and the relevance of the file to be operated indicated by the specific message is fourth highest. Of course, these relevance levels are merely examples, and the relevance levels may be set by an administrator or the like.

[0198] As shown in Fig. 20, processor 24 may display image 74, which represents a reduced version of the entire area in which the files are located, within display area 40. Display area 40 is a portion of that entire area. When a participant specifies a position within the entire area represented by image 74, processor 24 scrolls display area 40 to the specified position. Note that image 74 may be displayed when a participant issues a display instruction, or may be displayed regardless of whether a participant issues a display instruction.

[0199] Furthermore, if a related file does not fit within the display area 40 and is placed outside the display area 40, and a participant gives an instruction to display the next related file (for example, if the participant presses the "→" button or the "←" button, etc.), the processor 24 may display the next related file of the selected related file within the display area 40 in accordance with the instruction.

[0200] The processor 24 may not display files other than the related files in the display area 40. For example, when a message M3 is selected by a participant, as shown in Fig. 21, the processor 24 displays files F2, F5, and F6, which are related files of the message M3, in the display area 40, and does not display files other than files F2, F5, and F6 in the display area 40. When the number of related files is equal to or greater than a threshold, the processor 24 may not display files other than the related files in the display area 40 (see Fig. 21), and when the number of related files is less than the threshold, the processor 24 may display files other than the related files in the display area 40 (see Figs. 17 and 19).

[0201] In a case where files other than related files are not displayed in display area 40, if a participant gives an instruction to display files other than related files, processor 24 displays the files other than related files in display area 40. For example, if a button for giving an instruction to display files other than related files is displayed on screen 38 and a participant presses the button, processor 24 displays the files other than related files in display area 40.

[0202] (Processing to display related messages) The process of displaying related messages in response to file operations will be described in detail below.

[0203] Related messages include, for example, a message to which the manipulated file was attached, a context message related to the manipulated file, a message before or after the message to which the manipulated file was attached (e.g., a message sent before or a message sent after), a message before or after the context message to which the manipulated file was attached (e.g., a message sent before or a message sent after), a message to which a specific file related to the selected file was attached, or a context message related to a specific file related to the selected file.

[0204] The specific file is, for example, an updated version of the operated file or a file grouped by a participant. If a participant groups multiple files including the operated file, the grouped file is the specific file. For example, if a participant can change the position of a file in the display area 40 and the participant groups files, the grouped file is the specific file.

[0205] A context message related to a file is a message that indicates the status of the file, the details of an operation performed on the file, etc. Message 58 shown in FIG. 15 is an example of a context message related to a file. That is, when a participant instructs a file stored in the participant's personal repository to be dragged and dropped into display area 40, and access rights to the file are granted to other participants, message 58 is displayed in display area 42. Message 58 indicates the details of an operation performed on the file, i.e., uploading, and can be considered a context message related to the file. For example, when a participant selects the file displayed in display area 40, the context message is displayed in display area 42 as a related message.

[0206] The processor 24 may record the operation history of each participant and store information indicating the history (hereinafter referred to as "history information") in a memory such as the memory 22. The history information is information indicating, for example, who performed what, when, and what action was taken. For example, the processor 24 associates information for identifying the participant who performed the operation, information for identifying the target of the operation (e.g., a file, a message, etc.), information indicating the date and time the operation was performed, and information indicating the content of the operation, and stores and manages this information in a memory such as the memory 22. Files and messages may be searched for using the history information. For example, when a user such as a participant specifies information included in the history information and issues an instruction to search for files or messages, the processor 24 searches for files and messages that match the specified conditions and outputs the search results. For example, the search results are displayed on the display of the terminal device 16.

[0207] A specific example will be described with reference to Fig. 22. Fig. 22 shows a screen 38. Similar to the screen 38 according to the first embodiment described above (see Fig. 6), the screen 38 includes a display area 40 in which files stored in a repository linked to the activity are displayed, and a display area 42 in which messages sent to a channel linked to the activity are displayed. As an example, the activity is Project AAA.

[0208] For example, if a participant selects file F5 displayed in display area 40 by clicking, tapping, speaking, etc., processor 24 displays related messages in display area 42 to show related messages for the selected file F5.

[0209] For example, messages M3, M4, and M5 are examples of related messages. The processor 24 displays messages M3, M4, and M5 in the display area 42 so that messages M3, M4, and M5 are identified as messages related to file F5. For example, the processor 24 displays messages M3, M4, and M5 in the display area 42 so that they stand out and can be distinguished from other messages other than messages M3, M4, and M5. Specifically, the processor 24 may highlight messages M3, M4, and M5, decorate messages M3, M4, and M5, enlarge messages M3, M4, and M5, or display messages M3, M4, and M5 in a specific color.

[0210] 18, the display areas 40 and 42 may be scrolled. For example, as shown in FIG. 23, a scroll bar 70 is displayed in the display area 40, and a scroll bar 72 is displayed in the display area 42.

[0211] 23, messages M10 to M15 are displayed in the display area 42, and messages M3, M4, and M5, which are related messages of file F5, are not displayed in the display area 42. In other words, messages M3, M4, and M5 cannot fit within the display area 42 and are arranged outside the display area 42. In this state, when a participant selects file F5 displayed in the display area 40, the processor 24 scrolls the display area 42 so that messages M3, M4, and M5, which are related messages of file F5, are displayed within the display area 42. In other words, the processor 24 scrolls the display area 42 so that messages M3, M4, and M5, which are outside the display area 42, are displayed within the display area 42.

[0212] 24 shows the display area 42 after scrolling. Messages M3, M4, and M5, which are messages related to file F5, are displayed in the display area 42 after scrolling. By scrolling the display area 42 in this manner, messages M3, M4, and M5, which are messages related to the selected file F5, are displayed in the display area 42. As described with reference to FIG. 22, the processor 24 displays messages M3, M4, and M5 in the display area 42 so that they stand out and can be distinguished from other messages other than messages M3, M4, and M5.

[0213] Note that if messages M3, M4, and M5, which are related messages, cannot fit together within display area 42 even when display area 42 is scrolled (i.e., if messages M3, M4, and M5 are not displayed together within display area 42), processor 24 may display messages M3, M4, and M5 together within display area 42 by changing the positions of messages M3, M4, and M5 within display area 42. If selection of file F5 is deselected, processor 24 may return the positions of messages M3, M4, and M5 to their original positions.

[0214] As another example, when file F5 is selected by a participant in the state shown in FIG. 23, processor 24 may change the position of messages M3, M4, and M5, which are related messages of file F5, within display area 42 without scrolling display area 42, and display messages M3, M4, and M5 together in display area 42.

[0215] Processor 24 may display at least certain of the associated messages of the selected file in display area 42 .

[0216] The specific related message may be, for example, the message most related to the selected file, the oldest or newest related message, or a message at the same chronological position as the selected file. The most related message may be, for example, a message to which the selected file is attached. For example, if the number of related messages for the selected file is equal to or greater than a threshold, processor 24 displays at least the specific related message among the related messages in display area 42.

[0217] The processor 24 may change the brightness of the highlight display of the related message, the decoration of the related message, the size of the related message, or the color of the related message depending on the degree of relevance between the selected file and the message.

[0218] The processor 24 may not display messages other than related messages in the display area 42. For example, in the examples shown in Figures 17 and 18, when file F5 is selected by a participant, the processor 24 displays messages M3, M4, and M5, which are related messages of file F5, in the display area 42, and does not display messages other than messages M3, M4, and M5 in the display area 42. When the number of related messages is equal to or greater than a threshold, the processor 24 may not display messages other than related messages in the display area 42, and when the number of related messages is less than the threshold, may display messages other than related messages in the display area 42.

[0219] In a case where messages other than related messages are not displayed in display area 42, if a participant gives an instruction to display messages other than related messages, processor 24 displays messages other than related messages in display area 42. For example, if a button giving an instruction to display messages other than related messages is displayed on screen 38 and a participant presses the button, processor 24 displays messages other than related messages in display area 42.

[0220] The display of files and messages may be switched using tabs. An example of this switching is shown in Figures 25 and 26. Figures 25 and 26 show a screen 38.

[0221] In the examples shown in Figures 25 and 26, when a participant selects the message display tab, the processor 24 forms only the message display area 42 of the display areas 40, 42 on the screen 38, as shown in Figure 25, and when a participant selects the file display tab, the processor 24 forms only the file display area 40 of the display areas 40, 42 on the screen 38, as shown in Figure 26.

[0222] In other words, when the message display tab is selected by a participant, as shown in FIG. 25, the processor 24 forms only the display area 42 of the display areas 40 and 42 on the screen 38 and displays the message in the display area 42, thereby displaying only the message out of the files and messages on the screen 38.

[0223] When the file display tab is selected by a participant, as shown in FIG. 26, the processor 24 displays only the files out of the files and messages on the screen 38 by forming only the display area 40 of the display areas 40 and 42 on the screen 38.

[0224] 25, when a participant selects message M3 and then selects the file display tab, processor 24 switches the display area from display area 42 to display area 40, and displays files F2, F5, and F6, which are related files of message M3, in display area 40. In a case where files F2, F5, and F6 are located outside display area 40, when a participant selects message M3 and then selects the file display tab, processor 24 switches the display area from display area 42 to display area 40, scrolls display area 40 to the positions of files F2, F5, and F6, and displays files F2, F5, and F6 in display area 40.

[0225] 26, when a participant selects file F5 and then selects the message display tab, the processor 24 switches the display area from display area 40 to display area 42 and displays messages M3, M4, and M5, which are messages related to file F5, in the display area 42. In a case where messages M3, M4, and M5 are located outside the display area 42, when a participant selects file F5 and then selects the message display tab, the processor 24 switches the display area from display area 40 to display area 42, scrolls the display area 42 to the positions of messages M3, M4, and M5, and displays messages M3, M4, and M5 in the display area 42.

[0226] The display areas 40 and 42 may be displayed as separate screens (for example, separate windows) on the display of the terminal device 16. In this case, the processor 24 also displays the related files or related messages by using scrolling or the like, similar to tabs.

[0227] 18 and other figures, when display areas 40 and 42 are areas that can be moved by scrolling or the like, processor 24 may follow the movement of either display area 40 or display area 42, causing the other display area to scroll. For example, when one of display areas 40 and display area 42 is scrolled by a participant, processor 24 scrolls the other display area to follow the scrolling.

[0228] For example, if the display area 40 is scrolled by a participant and the file displayed in the display area 40 changes to another file, the processor 24 scrolls the display area 42 so that a message related to the file displayed in the scrolled display area 40 is displayed in the display area 42.

[0229] Similarly, when the display area 42 is scrolled by a participant and the message displayed in the display area 42 is changed to another message, the processor 24 scrolls the display area 40 so that the related file of the message displayed in the scrolled display area 42 is displayed in the display area 40.

[0230] (Processing when an updated file is selected) When a file displayed in display area 40 is updated and the updated file is selected, processor 24 may display a message associated with the updated file in display area 42. In this case, the associated message may include a message that was attached to the file before it was updated.

[0231] The process when an updated file is selected will be described in detail with reference to Figure 27. Figure 27 shows a schematic representation of the file.

[0232] For example, file F1 is attached to message M1, file F2 is attached to message M2, and file F3 is attached to message M3; messages M1, M2, and M3 are sent to a channel linked to project AAA, and processor 24 displays messages M1, M2, and M3 in a list in display area 42. Processor 24 also displays files attached to each message in a list in display area 40. As a result, files F1, F2, and F3 are displayed in a list in display area 40.

[0233] Furthermore, file F2 is an updated version of file F1. That is, file F2 is created by performing an operation such as editing on file F1. Furthermore, file F3 is an updated version of file F2. That is, file F3 is created by performing an operation such as editing on file F2. The operation such as editing may be performed on screen 38 via link server 14, or may be performed without the link server 14.

[0234] The specific processing when each file is selected will be described below.

[0235] (1. When file F1 is selected) For example, when a participant selects file F1 displayed in display area 40, processor 24 displays message M1, to which file F1 is attached, in display area 42, distinguishing it from other messages (e.g., messages M2 and M3). For example, processor 24 may display only message M1 among messages M1, M2, and M3 in display area 42, or may display messages M1, M2, and M3 in a list in display area 42 while message M1 stands out.

[0236] As another example, when a file F1 is selected by a participant, the processor 24 displays a message M1 to which the file F1 was attached and a message M2 to which an updated version of the file F2 was attached, distinguishing them from other messages, in the display area 42. For example, the processor 24 may display only the messages M1 and M2 out of the messages M1, M2, and M3 in the display area 42, or may display the messages M1 and M2 prominently while displaying a list of the messages M1, M2, and M3 in the display area 42.

[0237] As yet another example, if file F1 is selected by a participant, processor 24 displays in display area 42 message M1 to which file F1 was attached, and messages (e.g., messages M2 and M3) to which each of all files created by deriving file F1 (e.g., files F2 and F3, which are updated files) was attached.

[0238] As yet another example, when file F1 is selected by a participant, processor 24 may display message M1 to which file F1 was attached and messages before and after message M1 in display area 42, distinguishing them from other messages.

[0239] (2. When file F2 is selected) For example, when a participant selects file F2 displayed in display area 40, processor 24 displays message M2, to which file F2 is attached, in display area 42, distinguishing it from other messages (e.g., messages M1 and M3). For example, processor 24 may display only message M2 among messages M1, M2, and M3 in display area 42, or may display messages M1, M2, and M3 in a list in display area 42 while message M2 stands out.

[0240] As another example, when file F2 is selected by a participant, processor 24 displays message M2 to which file F2 was attached and message M1 to which file F1, which was the basis for creating file F2, was attached (i.e., message M1 to which file F1 before it was updated was attached) in display area 42, distinguishing them from other messages. For example, processor 24 may display only messages M1 and M2 out of messages M1, M2, and M3 in display area 42, or may display messages M1 and M2 prominently while displaying messages M1, M2, and M3 in a list in display area 42.

[0241] As yet another example, if file F2 is selected by a participant, processor 24 displays in display area 42 message M2 to which file F2 was attached, message M1 to which file F1, which was the basis for creating file F2, was attached, and message M3 to which file F3, which was created as a derivative of file F1, was attached.

[0242] (3. File F3 is selected) For example, when a participant selects file F3 displayed in display area 40, processor 24 displays message M3, to which file F3 is attached, in display area 42, distinguishing it from other messages (e.g., messages M1 and M2). For example, processor 24 may display only message M3 among messages M1, M2, and M3 in display area 42, or may display messages M1, M2, and M3 in a list in display area 42, with message M3 prominently displayed.

[0243] As another example, when file F3 is selected by a participant, processor 24 displays message M2 to which file F3 was attached and message M2 to which file F2, which was the basis for creating file F3, in display area 42, distinguishing them from other messages. For example, processor 24 may display only messages M2 and M3 among messages M1, M2, and M3 in display area 42, or may display messages M1, M2, and M3 in a list in display area 42 while messages M2 and M3 stand out.

[0244] As yet another example, if file F3 is selected by a participant, processor 24 displays in display area 42 message M3 to which file F3 was attached, and messages (e.g., messages M1 and M2) to which each of the files (e.g., files F1 and F2) that were the basis for creating file F3 were attached.

[0245] (Processing to hide files other than related files) 28 and 29, an example of processing for not displaying files other than related files in the display area 40 will be described. An example of the display area 40 is shown in FIGS. 28 and 29. As shown in FIG. 29, files F1 to F9 are displayed in the display area 40. Here, as an example, each file is not displayed in a timeline format (i.e., not in chronological order), but in an arbitrary position designated by the participant, in a position in name order, or the like.

[0246] For example, the processor 24 divides the display area 40 into a plurality of individual areas as shown by the dashed lines in Fig. 28. In the example shown in Fig. 28, the display area 40 is divided into a plurality of individual areas vertically.

[0247] For example, files F1, F4, and F7 are related files of a message selected by a participant. When the message is selected by a participant, processor 24 displays only files F1, F4, and F7 among files F1 to F9 in display area 40, and does not display files other than files F1, F4, and F7 in display area 40. At this time, processor 24 deletes the individual areas in display area 40 in which files other than files F1, F4, and F7 were displayed, and connects the individual areas in which related files F1, F4, and F7 are displayed. More specifically, files F5 and F6 are not displayed because they are not related files. The individual areas in which files F5 and F6 were displayed are deleted, and the individual area in which file F4 is displayed and the individual area in which file F7 is displayed are connected. As a result, related files F1, F4, and F7 are displayed closer to each other.

[0248] The functions of each unit of the link server 14 and the terminal device 16 are realized, for example, by the cooperation 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 the memory via a recording medium such as a CD or DVD, or via a communication path such as a network.

[0249] 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 the operations of the processor is not limited to the order described in the above embodiments, and may be changed as appropriate. [Explanation of symbols]

[0250] 10 file management server, 12 messaging server, 14 collaboration server, 16 terminal device.

Claims

[Claim 1] a processor; The processor: forming a first display area in which a message is displayed and a second display area in which a file is displayed on the display; In response to an operation on a file displayed in the second display area, a message related to the operated file is displayed in the first display area. An information processing device, For each activity set by a user for a specific purpose, participants of the activity are associated; Storage areas of file management services provided by a plurality of service providers, to which at least one participant has access rights, are linked to the activity; a messaging service to which at least one participant has access, for exchanging at least messages, is associated with the activity; the first display area is an area for displaying a message sent to a linked messaging service to which the requesting participant has access in response to a request from each participant for access to the activity; the second display area is an area where a file stored in a linked storage area to which the requesting participant has access is displayed; Information processing device.

Images