WO2019096086A1 - Procédé d'accès à un espace partagé et procédé et appareil de gestion d'autorisation - Google Patents

Procédé d'accès à un espace partagé et procédé et appareil de gestion d'autorisation Download PDF

Info

Publication number
WO2019096086A1
WO2019096086A1 PCT/CN2018/115003 CN2018115003W WO2019096086A1 WO 2019096086 A1 WO2019096086 A1 WO 2019096086A1 CN 2018115003 W CN2018115003 W CN 2018115003W WO 2019096086 A1 WO2019096086 A1 WO 2019096086A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
shared
shared content
content
information
Prior art date
Application number
PCT/CN2018/115003
Other languages
English (en)
Chinese (zh)
Inventor
陈京昌
佘智勇
李智
林剑雄
Original Assignee
钉钉控股（开曼）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 钉钉控股（开曼）有限公司 filed Critical 钉钉控股（开曼）有限公司
Publication of WO2019096086A1 publication Critical patent/WO2019096086A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • One or more embodiments of the present disclosure relate to the field of communications technologies, and in particular, to a shared space access method, a rights management method, and an apparatus.
  • the mobile group office platform is more and more widely used in the business processes of various groups such as enterprises, educational institutions, government agencies, etc., which can not only improve communication efficiency between users, reduce communication costs, but also be effective. Improve user event processing efficiency and office efficiency.
  • one or more embodiments of the present specification provide an access method, a rights management method, and an apparatus for a shared space.
  • a method for accessing a shared space including:
  • a method for accessing a shared space including:
  • a method for sharing shared content including:
  • an access device for a shared space including:
  • An access request receiving unit that receives an access request of the user for a shared space associated with the community
  • the content determining unit determines, according to the rights information of the user in the organization structure of the community, the shared content in the shared space that matches the rights information, to provide to the user.
  • an access device for a shared space including:
  • the request sending unit in response to the detected user operation, sending an access request for the community-related shared space to the server, so that the server determines the content according to the user's authority information in the organization structure of the group a shared content in the shared space that matches the permission information;
  • a sharing device for sharing content including:
  • the instruction sending unit sends a sharing instruction for the shared content to the server, where the sharing instruction is used to instruct the server to share the shared content to the target user specified by the user.
  • a method for accessing a shared space including:
  • an access device for a shared space including:
  • the content determining unit determines, according to the rights information of the user in the community, the shared content that matches the rights information in the shared space to provide to the user.
  • a rights management method for a shared space including:
  • a rights management apparatus for a shared space including:
  • the authority obtaining unit obtains the authority information of the user in the group
  • the rights management unit manages the access rights of the user to the shared content in the shared space related to the community according to the rights information.
  • a method for accessing a shared space including:
  • an access device for a shared space including:
  • a permission obtaining unit acquiring the authority information of the user in an organization structure of the group
  • the content determining unit determines, according to the rights information of the user in the organization structure of the community, the shared content in the shared space that matches the rights information, to provide to the user.
  • FIG. 1 is a schematic structural diagram of a shared space access system according to an exemplary embodiment.
  • FIG. 2A is a flowchart of a method for accessing a shared space on a server side according to an exemplary embodiment.
  • FIG. 2B is a flowchart of a method for accessing a shared space on a client side according to an exemplary embodiment.
  • 2C is a flowchart of a method for sharing shared content provided by an exemplary embodiment.
  • FIG. 3 is a flowchart of a method for managing rights in a shared space according to an exemplary embodiment.
  • FIG. 4 is a schematic diagram of an organizational structure of an enterprise AA according to an exemplary embodiment.
  • 6-10 are schematic diagrams of an access interface of a shared space provided by an exemplary embodiment.
  • FIG. 11 is a schematic diagram of an entry display interface provided by an exemplary embodiment.
  • FIG. 12 is a schematic diagram of another shared space access interface provided by an exemplary embodiment.
  • FIG. 13 is a schematic diagram of a group session interface provided by an exemplary embodiment.
  • FIG. 14 is a schematic diagram of a task initiation interface of a job receiving function provided by an exemplary embodiment.
  • FIG. 15 is a schematic diagram of another population group session interface provided by an exemplary embodiment.
  • FIG. 16 is a schematic diagram of a communication session interface of a participant side of a job receiving task according to an exemplary embodiment.
  • FIG. 17 is a schematic diagram of uploading shared content provided by an exemplary embodiment.
  • FIG. 18 is a schematic diagram of another upload sharing content provided by an exemplary embodiment.
  • FIG. 19 is a schematic diagram of still another shared space access interface provided by an exemplary embodiment.
  • FIG. 20 is a schematic diagram of an automatic synchronization file provided by an exemplary embodiment.
  • FIG. 21 is a schematic diagram of an online editing file provided by an exemplary embodiment.
  • FIG. 22 is a schematic diagram of triggering a sharing operation on shared content according to an exemplary embodiment.
  • FIG. 23 is a schematic diagram of a sharing setting interface provided by an exemplary embodiment.
  • FIG. 24 is a schematic diagram of a communication session interface provided by an exemplary embodiment.
  • FIG. 25 is a schematic diagram of permission setting for shared content according to an exemplary embodiment.
  • FIG. 26 is a schematic structural diagram of an apparatus according to an exemplary embodiment.
  • FIG. 27 is a block diagram of a shared space access device according to an exemplary embodiment.
  • FIG. 28 is a block diagram of another shared space access device according to an exemplary embodiment.
  • FIG. 29 is a schematic structural diagram of another apparatus according to an exemplary embodiment.
  • FIG. 30 is a block diagram of a rights management apparatus for a shared space according to an exemplary embodiment.
  • FIG. 31 is a schematic structural diagram of still another apparatus according to an exemplary embodiment.
  • FIG. 32 is a block diagram of a shared content sharing apparatus according to an exemplary embodiment.
  • the steps of the corresponding method are not necessarily performed in the order shown and described in the specification in other embodiments. In some other embodiments, the method may include more or fewer steps than those described herein. In addition, the individual steps described in this specification may be decomposed into multiple steps for description in other embodiments; while the multiple steps described in this specification may be combined into a single step in other embodiments. description.
  • FIG. 1 is a schematic structural diagram of a shared space access system according to an exemplary embodiment.
  • the system may include a server 11, a network 12, and a number of electronic devices, such as a mobile phone 13, a PC 14, and the like.
  • the server 11 may be a physical server including a separate host, or the server 11 may be a virtual server hosted by the host cluster.
  • the server 11 can run a server-side program of an application to implement related business functions of the application. For example, when the server 11 runs the program of the mobile group office platform, the mobile group can be implemented. The server side of the platform.
  • the server 11 can carry the shared space and related functions, or the shared space can be carried by other devices, and the server 11 implements access control and management functions for the shared space.
  • the mobile group office platform can not only realize the communication function, but also can be used as an integrated function platform for many other functions, such as approval events (such as leave, office item application, financial and other approval events), attendance events.
  • approval events such as leave, office item application, financial and other approval events
  • attendance events such as attendance events.
  • the mobile group office platform can be carried in instant messaging applications in related technologies, such as enterprise instant messaging (EIM) applications, such as Skype For. Microsoft Wait.
  • EIM enterprise instant messaging
  • Skype For. Microsoft Wait a mobile group office platform
  • the instant messaging function is only one of the communication functions supported by the mobile group office platform, and the mobile group office platform can implement more functions such as the above, which will not be described here.
  • the mobile phone 13 and the PC 14 are only some types of electronic devices that the user can use. In fact, users obviously can also use electronic devices such as tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc. Various embodiments do not limit this.
  • the electronic device can run a client-side program of an application to implement related business functions of the application, for example, when the electronic device runs a program of the mobile group office platform, the mobile device can be implemented as the mobile device. The client of the group office platform.
  • the application of the client of the mobile group office platform can be pre-installed on the electronic device so that the client can be launched and run on the electronic device; of course, when adopting an online "customer such as HTML5 technology" At the end, the client can be obtained and run without installing the corresponding application on the electronic device.
  • the network 12 may include a Public Switched Telephone Network (PSTN) and the Internet.
  • PSTN Public Switched Telephone Network
  • FIG. 2A is a flowchart of a method for accessing a shared space on a server side according to an exemplary embodiment. As shown in FIG. 2A, the method is applied to a server device (such as the server 11 shown in FIG. 1), and may include the following steps:
  • Step 202A Receive an access request of the user for the shared space associated with the community.
  • the user may initiate an access request through the client side device, so that the server side device can receive a corresponding access request from the client side device.
  • the user may access the shared space associated with the community for the internal members of the community from the portal provided by the relevant functional interface of the community.
  • the user may not belong to the community, that is, the user is not an internal member of the community, but the user may access the shared space associated with the community through an portal provided by the community's public homepage or the like.
  • the community-related shared space may include at least one of the following: a shared space of the group, for example, the shared space may be a cloud disk rented, purchased, or built by the group; a shared subspace associated with a specific function in the shared space, for example, when the specific function is a financial management function, the corresponding shared subspace is used to store shared content such as financial related files; and the group belonging to the community corresponds to
  • the shared subspace for example, each department in the community respectively creates a corresponding group, and each group can divide the shared subspaces in the shared space for sharing between the group members in the same group. Sharing of content.
  • Step 204A Determine, according to the rights information of the user in the community, the shared content in the shared space that matches the rights information, to provide to the user.
  • the rights information of the user in the community may include the rights information of the user in the organization structure of the group; of course, the rights information of the user in the group is not necessarily related to the organizational structure, such as separately set. Permission information, temporarily set permission information, permission information with space or time conditions, etc., are not limited in this specification.
  • the rights information of the user in the community may be predetermined.
  • the user's rights information in the community may be obtained upon receiving the access request.
  • this specification does not limit the timing of acquisition of the rights information.
  • the organizational structure of the community is divided into a plurality of permission categories according to a specific dimension, for example, when the specific dimension is a department, the group members of the same department may be divided into the same permission category, wherein each permission category You can include group members from one or more departments to achieve privilege isolation between departments in different privilege categories.
  • determining, according to the specific permission category with the management authority indicated by the permission information of the user, and the permission category indicated by the permission information of the shared content in the shared space determining that the shared space belongs to the specific permission The shared content of the category as the shared content that matches the permission information.
  • the shared content belonging to the privilege category 1 in the shared space may be considered to match the privilege information of the above-mentioned user, but in the shared space
  • the shared content attributed to the privilege category 2 may be considered to not match the privilege information of the above-mentioned user (for example, the "sales department" is divided into the privilege category 2, then the user does not have access to the shared content belonging to the "sales department” ).
  • the above specific dimensions may have many other options besides the department, and the specification does not limit this; for example, the specific dimension may also include a job level, and the group members of the same job level may be divided into the same Permission categories, where each permission category can include group members of one or more job levels.
  • the shared content that matches the rights information in the shared space may include at least one of the following: the shared content uploaded by the user, and the shared by the group members belonging to the specific permission type in the community.
  • the content for example, when the user and the department to which the other user belongs belong to the permission category 1, the shared content uploaded by the other user matches the permission information of the user, that is, the shared content uploaded by the user for the another user has Access rights, and when the department to which another user belongs belongs to the rights category 2, the shared content uploaded by the other user does not match the rights information of the user, that is, the user does not have access to the shared content uploaded by the other user.
  • the management member of the group is set to be shared content belonging to the specific permission category, for example, although the department to which the other user belongs belongs to the permission category 2, the management user may actively upload the at least one user.
  • Part of the shared content is set to match the permission category 1 (the shared content can still be at the same time Arranged for permission category 2), so that the user uploads further rights information matches at least a portion shared content to the user, the at least a portion of the shared content that is uploaded to the said user has access to another user.
  • the permission category 1 the shared content can still be at the same time Arranged for permission category 2
  • the organizational structure of the group may be divided into a plurality of privilege levels according to a specific dimension.
  • a specific dimension is a job grading level
  • the privilege level can be associated with the job tier to achieve privilege isolation between group members at different privilege levels, ie, group members with higher rank levels have higher privilege levels, and group members with lower rank tiers have lower privilege levels. Permission level.
  • the specific permission level with the management authority indicated by the permission information of the user, and the permission level indicated by the permission information of the shared content in the shared space may be determined that the permission level in the shared space is not higher than
  • the shared content of a specific privilege level is used as the shared content that matches the privilege information.
  • the specific privilege level indicated by the privilege information of the user is 3, the shared content in the shared space whose privilege level is not higher than the level 3 (ie, 0-3) is considered to match the privilege information of the user.
  • the shared content whose privilege level is higher than level 3 (such as level 4, level 5 or higher) is considered to not match the privilege information of the above user.
  • each privilege category may include one or more group members of the position level, for example, all group members of the "General Manager” have a privilege level of 5, and all group members of the "finance room” have a privilege level of 4
  • the level of authority of all group members of the "Sales" department is level 3.
  • the shared content that matches the rights information in the shared space includes at least one of the following: the shared content uploaded by the user; and the group member whose privilege level is not higher than the specific privilege level in the community
  • the shared content for example, when the privilege level of the user is 3, the shared content uploaded by another user whose privilege level is 2, because the privilege level of the user is higher, it can be considered to match the privilege level of the user. That is, the user has access rights to the shared content uploaded by the other user, and the shared content uploaded by another user with the privilege level of 5 is considered to be unmatched by the user because the privilege level of the user is lower.
  • the permission level that is, the user does not have access to the shared content uploaded by the other user; the management member of the group is set to the shared content whose permission level is not higher than the specific permission level, such as although the above-mentioned another user The permission level is 5, but the management user can actively upload at least one of the other users.
  • the shared content is set to match the privilege level 3 and is not greater than the specific privilege level indicated by the user privilege information, so that the at least part of the shared content uploaded by the further user matches the privilege information of the user, that is, the user The at least one part of the shared content uploaded by another user has access rights.
  • the access rights in this specification may include rights to perform one or more operations such as reading, modifying, deleting, etc. for the shared content.
  • the rights information of the shared content in the shared space may be determined in various ways.
  • the rights information of the uploader may be used as the rights information of the shared content. For example, when the uploader belongs to the rights type 1, the rights information of the shared content uploaded by the uploader is set to the permission type 1, and then When the uploader's permission level is 3, the permission information of the shared content uploaded by the uploader is set to the permission level 3.
  • the rights information that is set by the uploader for the shared content, and the set rights information meets the rights information of the uploader; for example, when the uploader belongs to the rights type 1, the uploader The permission information of the uploaded shared content can be set to the permission type 1 and cannot be set to the permission type 2, and when the uploader belongs to both the permission type 1 and the permission type 2, the uploader can upload the shared content.
  • the permission information sets at least one of the permission type 1 and the permission type 2, and when the uploader's permission level is 3, the uploader can set the permission information of the uploaded shared content to the permission level 0-3.
  • the rights information may be set by the administrative user of the community for the shared content.
  • the administrative user of the group refers to a user who has administrative rights to the group, and the administrative user may be a group member of the group, such as a creator or administrator of the group, or the management member may be not Group members of the group, such as super administrators.
  • the storage path matching the permission information in the shared space may be determined according to the rights information of the user in the community, and then the shared content under the determined storage path is determined to be a match.
  • the shared content of the permission information may be stored in advance in the same storage path of the shared space (such as in the same folder) according to the rights information of the shared content, so that by determining the storage path that matches the rights information of the user, All shared content under the storage path is quickly determined as the shared content that matches the user's permission information.
  • the determined storage path may be provided to the client side device to display the determined storage path to the user by the client side device, because the shared content under the storage path is considered to match the user's Permission information, and thus the user can access the storage path to achieve access to the shared content in the shared space that matches the permission information.
  • the shared content under the determined storage path may be provided to the client side device to display the shared content under the determined storage path to the user by the client side device, where the storage path is The user is invisible, so that the user only needs to pay attention to the shared content that matches the own permission information, and does not need to pay attention to the storage path where the shared content is located, such as a folder corresponding to the storage path, so that the user can directly and quickly browse and match.
  • the shared content of its own permission information may be provided to the client side device to display the shared content under the determined storage path to the user by the client side device, where the storage path is The user is invisible, so that the user only needs to pay attention to the shared content that matches the own permission information, and does not need to pay attention to the storage path where the shared content is located, such as a folder corresponding to the storage path, so that the user can directly and quickly browse and match.
  • the shared content of its own permission information may be provided to the client side device to display the shared content under the determined storage path to the user by the client side device, where
  • the plurality of shared content selected by the user from the shared content that matches the rights information may be determined, and the record information in the specific information record format in the plurality of shared content is extracted to be combined and generated.
  • New shared content For example, when the shared content includes a weekly report submitted by each group member in the group, the record information of the weekly reports may be merged according to the above embodiment, so that only one shared content needs to be viewed, and it is not necessary to separately view multiple copies. Sharing content helps improve access to shared content.
  • the shared content uploaded by the group members of the community for the upload task may be stored.
  • the uploading task may be initiated by the user, or may be initiated by any group member in the community; in some cases, the initiator of the uploading task may be qualified, for example, only the administrative user of the group may initiate, and the ordinary community member Can't initiate.
  • the shared content that matches the rights information may include the shared content uploaded by the user for the upload task, and any of the The shared content uploaded by the group member for the uploading task, so that the user accesses the shared content uploaded by other community members, is helpful to implement management work; when the user's permission information is not greater than the member of the group
  • the shared content that is matched to the rights information may include the shared content uploaded by the user for the uploading task, and does not include the shared content uploaded by the any group member for the uploading task, so that Protect the privacy of members of the group.
  • the file to be synchronized and the file synchronization object selected by the management member of the community may be determined, the file synchronization object includes at least one group member in the community; and then, the file synchronization object is pushed to the file synchronization object
  • the synchronization file is described to update to the local storage space on the electronic device used by the file synchronization object.
  • the file to be synchronized may include any file such as a regulation system, a reimbursement process, a commodity quotation, and the like, and the server may actively push the file to be synchronized to the electronic device to be used for synchronization by selecting a file to be synchronized and a file synchronization object by the management member.
  • the local storage space of the device without the file synchronization object acquiring the file to be synchronized from the shared space or other storage space, can not only simplify the operation of searching, downloading, etc. of the file synchronization object for the file to be synchronized, but also can actively push the file to be synchronized. Automatic update to avoid problems associated with file synchronization objects using older versions of files.
  • an online editing interface of any of the files may be returned to the at least one community member according to an online editing request initiated by at least one group member of the group to any of the files; and then receiving the An online editing instruction issued by at least one group member for any of the files, and in response to the online editing instruction, performing a corresponding online editing process on any of the files.
  • the online editing request may be initiated by the group member for any file, such as the file in the shared space, the file sent by other community members to the group member, the shared file in the group where the group member is located, and the like. Make restrictions.
  • the group member can perform online editing processing for any of the files without having to download the file to the local storage space and then perform editing processing, thereby avoiding leaving too much in the local storage space.
  • Files of the versions (such as the original version, the first modified version, the second modified version, etc.) to prevent confusion in subsequent processing.
  • the online editing process of files is also applicable to collaborative editing scenarios between multiple group members, that is, multiple group members can perform online editing processing on any of the files, avoiding multiple
  • the local storage space of group members form different versions of files, preventing confusion between different versions of files.
  • the target editing content corresponding to the online editing instruction in the any file may be determined; when the target editing content matches the organization of the group initiating the online editing instruction in the group In the permission information, the corresponding online editing process is performed on any of the files according to the online editing instruction.
  • each group member can be controlled to edit the content of the target in any file, for example, the group member A can only edit the first page 1-3 of the file, Group member B can only edit the first chapter of any of the files, etc., thereby implementing less fine-grained rights management for online editing processing, and avoiding conflicts between online editing of different group members.
  • the sharing request of the user for the shared content may be received, and the shared content is shared to the target user specified by the user, so that the target user can view the shared content, even the sharing Content implementation editing and other operations.
  • the shared content may be directly sent to the target user; or the access link of the shared content may be sent to the target user, so that the target user can access the shared content through the access link.
  • the access link may be a storage path of the shared content.
  • the target user may include any user specified by the user, and this specification does not limit this.
  • the target user may belong to the group to which the user belongs, or may not be related to the group; for example, from the perspective of the authority, the target user may have the authority corresponding to the shared content, and You may not have permission for this shared content.
  • the sharing scheme can be made based on the above sharing scheme.
  • Target users can also view, edit, and other shared content to facilitate project collaboration such as cross-group.
  • the above-mentioned sharing scheme can realize the reminding function for the target user, and the target user is not required to actively search in the shared space, which helps to simplify the operation of the target user. .
  • permission settings may be made for the shared content to restrict sharing operations for the shared content. For example, it may be restricted that only the uploader of the shared content can implement the sharing operation, or the member of the specified one or more groups can be restricted from being able to perform the sharing operation, or the user above the specified authority level can be restricted from performing the sharing operation, etc. This is not a limitation.
  • the operation authority for the shared content set by the user for the target user may be received, so that the operation performed by the target user on the shared content is restricted according to the operation authority.
  • the user can set the operation permission to only allow reading, only allow reading and editing, allow reading and editing but do not allow sharing, etc., and this specification does not limit this.
  • the user who is the sharer can limit the type of operation of the shared content as the target user of the shared party, and avoid the problem of leakage of information of the shared content.
  • an operation time period for the shared content set by the user for the target user may be received; and then, the target user is given temporary operation authority for the shared content, the temporary Operation rights are only valid for the operating time period.
  • the user can set the temporary operation authority so that the temporary operation authority of the target user is set to allow only reading, only reading and editing, allowing reading and editing but not sharing. Etc., this specification does not limit this.
  • sharing restrictions can be performed on the shared content in the time dimension, so that in particular, if the target user itself does not have direct operation authority for the shared content, the risk that the shared content is leaked can be reduced.
  • FIG. 2B is a flowchart of a method for accessing a shared space on a client side according to an exemplary embodiment. As shown in FIG. 2B, the method is applied to a client side device (for example, the mobile phone 13, the PC 14, and the like shown in FIG. 1), and may include the following steps:
  • Step 202B in response to the detected user operation, sending an access request for the community-related shared space to the server, so that the server determines that the shared space matches according to the user's rights information in the community.
  • the shared content of the permission information in response to the detected user operation, sending an access request for the community-related shared space to the server, so that the server determines that the shared space matches according to the user's rights information in the community.
  • the user may initiate an access request through the client side device, so that the server side device can receive a corresponding access request from the client side device.
  • the user may access the shared space associated with the community for the internal members of the community from the portal provided by the relevant functional interface of the community.
  • the user may not belong to the community, that is, the user is not an internal member of the community, but the user may access the shared space associated with the community through an entry provided by the community's public home page or the like.
  • the community-related shared space may include at least one of the following: a shared space of the group, for example, the shared space may be a cloud disk rented, purchased, or built by the group; a shared subspace associated with a specific function in the shared space, for example, when the specific function is a financial management function, the corresponding shared subspace is used to store shared content such as financial related files; and the group belonging to the community corresponds to
  • the shared subspace for example, each department in the community respectively creates a corresponding group, and each group can divide the shared subspaces in the shared space for sharing between the group members in the same group. Sharing of content.
  • the rights information of the user in the community may include the rights information of the user in the organization structure of the group; of course, the rights information of the user in the group is not necessarily related to the organizational structure, such as separately set. Permission information, temporarily set permission information, permission information with space or time conditions, etc., are not limited in this specification.
  • the rights information of the user in the community may be predetermined.
  • the user's rights information in the community may be obtained upon receiving the access request.
  • this specification does not limit the timing of acquisition of the rights information.
  • the organizational structure of the community is divided into a plurality of permission categories according to a specific dimension, for example, when the specific dimension is a department, the group members of the same department may be divided into the same permission category, wherein each permission category You can include group members from one or more departments to achieve privilege isolation between departments in different privilege categories.
  • determining, according to the specific permission category with the management authority indicated by the permission information of the user, and the permission category indicated by the permission information of the shared content in the shared space determining that the shared space belongs to the specific permission The shared content of the category as the shared content that matches the permission information.
  • the shared content belonging to the privilege category 1 in the shared space may be considered to match the privilege information of the above-mentioned user, but in the shared space
  • the shared content attributed to the privilege category 2 may be considered to not match the privilege information of the above-mentioned user (for example, the "sales department" is divided into the privilege category 2, then the user does not have access to the shared content belonging to the "sales department” ).
  • the above specific dimensions may have many other options besides the department, and the specification does not limit this; for example, the specific dimension may also include a job level, and the group members of the same job level may be divided into the same Permission categories, where each permission category can include group members of one or more job levels.
  • the shared content that matches the rights information in the shared space may include at least one of the following: the shared content uploaded by the user, and the shared by the group members belonging to the specific permission type in the community.
  • the content for example, when the user and the department to which the other user belongs belong to the permission category 1, the shared content uploaded by the other user matches the permission information of the user, that is, the shared content uploaded by the user for the another user has Access rights, and when the department to which another user belongs belongs to the rights category 2, the shared content uploaded by the other user does not match the rights information of the user, that is, the user does not have access to the shared content uploaded by the other user.
  • the management member of the group is set to be shared content belonging to the specific permission category, for example, although the department to which the other user belongs belongs to the permission category 2, the management user may actively upload the at least one user.
  • Part of the shared content is set to match the permission category 1 (the shared content can still be at the same time Arranged for permission category 2), so that the user uploads further rights information matches at least a portion shared content to the user, the at least a portion of the shared content that is uploaded to the said user has access to another user.
  • the permission category 1 the shared content can still be at the same time Arranged for permission category 2
  • the organizational structure of the group may be divided into a plurality of privilege levels according to a specific dimension.
  • a specific dimension is a job grading level
  • the privilege level can be associated with the job tier to achieve privilege isolation between group members at different privilege levels, ie, group members with higher rank levels have higher privilege levels, and group members with lower rank tiers have lower privilege levels. Permission level.
  • the specific permission level with the management authority indicated by the permission information of the user, and the permission level indicated by the permission information of the shared content in the shared space may be determined that the permission level in the shared space is not higher than
  • the shared content of a specific privilege level is used as the shared content that matches the privilege information.
  • the specific privilege level indicated by the privilege information of the user is 3, the shared content in the shared space whose privilege level is not higher than the level 3 (ie, 0-3) is considered to match the privilege information of the user.
  • the shared content whose privilege level is higher than level 3 (such as level 4, level 5 or higher) is considered to not match the privilege information of the above user.
  • each privilege category may include one or more group members of the position level, for example, all group members of the "General Manager” have a privilege level of 5, and all group members of the "finance room” have a privilege level of 4
  • the level of authority of all group members of the "Sales" department is level 3.
  • the shared content that matches the rights information in the shared space includes at least one of the following: the shared content uploaded by the user; and the group member whose privilege level is not higher than the specific privilege level in the community
  • the shared content for example, when the privilege level of the user is 3, the shared content uploaded by another user whose privilege level is 2, because the privilege level of the user is higher, it can be considered to match the privilege level of the user. That is, the user has access rights to the shared content uploaded by the other user, and the shared content uploaded by another user with the privilege level of 5 is considered to be unmatched by the user because the privilege level of the user is lower.
  • the permission level that is, the user does not have access to the shared content uploaded by the other user; the management member of the group is set to the shared content whose permission level is not higher than the specific permission level, such as although the above-mentioned another user The permission level is 5, but the management user can actively upload at least one of the other users.
  • the shared content is set to match the privilege level 3 and is not greater than the specific privilege level indicated by the user privilege information, so that the at least part of the shared content uploaded by the further user matches the privilege information of the user, that is, the user The at least one part of the shared content uploaded by another user has access rights.
  • the access rights in this specification may include rights to perform one or more operations such as reading, modifying, deleting, etc. for the shared content.
  • the rights information of the shared content in the shared space may be determined in various ways.
  • the rights information of the uploader may be used as the rights information of the shared content. For example, when the uploader belongs to the rights type 1, the rights information of the shared content uploaded by the uploader is set to the permission type 1, and then When the uploader's permission level is 3, the permission information of the shared content uploaded by the uploader is set to the permission level 3.
  • the rights information that is set by the uploader for the shared content, and the set rights information meets the rights information of the uploader; for example, when the uploader belongs to the rights type 1, the uploader The permission information of the uploaded shared content can be set to the permission type 1 and cannot be set to the permission type 2, and when the uploader belongs to both the permission type 1 and the permission type 2, the uploader can upload the shared content.
  • the permission information sets at least one of the permission type 1 and the permission type 2, and when the uploader's permission level is 3, the uploader can set the permission information of the uploaded shared content to the permission level 0-3.
  • the rights information may be set by the administrative user of the community for the shared content.
  • the administrative user of the group refers to a user who has administrative rights to the group, and the administrative user may be a group member of the group, such as a creator or administrator of the group, or the management member may be not Group members of the group, such as super administrators.
  • the storage path matching the permission information in the shared space may be determined according to the rights information of the user in the community, and then the shared content under the determined storage path is determined to be a match.
  • the shared content of the permission information may be stored in advance in the same storage path of the shared space (such as in the same folder) according to the rights information of the shared content, so that by determining the storage path that matches the rights information of the user, All shared content under the storage path is quickly determined as the shared content that matches the user's permission information.
  • Step 204B Show, according to the data returned by the server, the shared content in the shared space that matches the permission information.
  • the determined storage path may be displayed to the user. Since the shared content under the storage path is considered to match the user's permission information, the user may access the storage path to achieve the shared space. An access operation of the shared content that matches the permission information.
  • the shared content under the determined storage path may be presented to the user, wherein the storage path is invisible to the user, such that the user only needs to focus on the shared content that matches the own permission information, without Pay attention to the storage path where the shared content is located, such as a folder corresponding to the storage path, etc., so that the user can directly and quickly browse the shared content that matches the own permission information.
  • the plurality of shared content selected by the user from the shared content matching the rights information may be determined, so that the record information of the plurality of shared content adopting the specific information record format may be extracted, to Merge to generate new shared content.
  • the shared content includes a weekly report submitted by each group member in the group
  • the record information of the weekly reports may be merged according to the above embodiment, so that only one shared content needs to be viewed, and it is not necessary to separately view multiple copies. Sharing content helps improve access to shared content.
  • the shared content uploaded by the group members of the community for the upload task may be stored.
  • the uploading task may be initiated by the user, or may be initiated by any group member in the community; in some cases, the initiator of the uploading task may be qualified, for example, only the administrative user of the group may initiate, and the ordinary community member Can't initiate.
  • the shared content that matches the rights information may include the shared content uploaded by the user for the upload task, and any of the The shared content uploaded by the group member for the uploading task, so that the user accesses the shared content uploaded by other community members, is helpful to implement management work; when the user's permission information is not greater than the member of the group
  • the shared content that is matched to the rights information may include the shared content uploaded by the user for the uploading task, and does not include the shared content uploaded by the any group member for the uploading task, so that Protect the privacy of members of the group.
  • the file to be synchronized and the file synchronization object selected by the user may be determined, and the file synchronization object includes at least one group member in the community; Initiating a file push request to the server, the file push request instructing the server to push the file to be synchronized to the file synchronization object, to update the file to be synchronized to an electronic device used by the file synchronization object a local storage space on the device; when the user does not belong to the management member of the community, the file that the server pushes according to the file push request initiated by the management member of the community may be received and stored in the local storage space.
  • the file to be synchronized may include any file such as a regulation system, a reimbursement process, a commodity quotation, and the like, and the server may actively push the file to be synchronized to the electronic device to be used for synchronization by selecting a file to be synchronized and a file synchronization object by the management member.
  • the local storage space of the device without the file synchronization object acquiring the file to be synchronized from the shared space or other storage space, can not only simplify the operation of searching, downloading, etc. of the file synchronization object for the file to be synchronized, but also can actively push the file to be synchronized. Automatic update to avoid problems associated with file synchronization objects using older versions of files.
  • the old version file corresponding to the received file in the local storage space may be automatically searched to update the old version file to the received file, which may prevent The user mistakes the old version file for the latest version of the file.
  • the file may be determined to be the same file according to the file name. For example, if the received file is "Enterprise AA Quoted Quote.xls", the file named "Enterprise AA Quote.xls" in the local storage space may be searched for automatic implementation. replace.
  • the default is that the received file is the latest version; in another case, the version number of the received file can be compared with the version number of the found file, such as when the received file is If the version number is 2.0 and the version number of the found file is 1.0, you can confirm that the received file is the latest version and the replacement operation of the implementation file.
  • the version number of the received file is 2.0
  • the version of the found file is When the number is 2.1, it can be determined that the received file is not the latest version, and the replacement of the file is canceled.
  • an online editing request for any file may be initiated to the server; an online editing interface of any of the files returned by the server is received and displayed, so that the user can view and implement subsequent User editing operation; then, according to the detected user editing operation, sending an online editing instruction for the file to the server, so that the server performs corresponding online editing processing on any of the files.
  • the online editing request may be initiated by the group member for any file, such as the file in the shared space, the file sent by other community members to the group member, the shared file in the group where the group member is located, and the like. Make restrictions.
  • the group member can perform online editing processing for any of the files without having to download the file to the local storage space and then perform editing processing, thereby avoiding leaving too much in the local storage space.
  • Files of the versions (such as the original version, the first modified version, the second modified version, etc.) to prevent confusion in subsequent processing.
  • the online editing process of files is also applicable to collaborative editing scenarios between multiple group members, that is, multiple group members can perform online editing processing on any of the files, avoiding multiple
  • the local storage space of group members form different versions of files, preventing confusion between different versions of files.
  • the online editing instruction corresponding to the target editing content in the any file matches the authority information of the user in the organization structure of the community.
  • each group member can be controlled to edit the content of the target in any file, for example, the group member A can only edit the first page 1-3 of the file, Group member B can only edit the first chapter of any of the files, etc., thereby implementing less fine-grained rights management for online editing processing, and avoiding conflicts between online editing of different group members.
  • a sharing instruction for the shared content may be sent to the server in response to the detected user operation, so that the server shares the shared content to the target user specified by the user. So that the target user can view the shared content, and even perform editing and the like on the shared content.
  • the server may send the shared content directly to the target user; or the server may send the access link of the shared content to the target user, so that the target user can share the share through the access link.
  • the content is accessed, for example, the access link may be a storage path of the shared content.
  • the target user may include any user specified by the user, and this specification does not limit this.
  • the target user may belong to the group to which the user belongs, or may not be related to the group; for example, from the perspective of the authority, the target user may have the authority corresponding to the shared content, and You may not have permission for this shared content.
  • the sharing scheme can be made based on the above sharing scheme.
  • Target users can also view, edit, and other shared content to facilitate project collaboration such as cross-group.
  • the above-mentioned sharing scheme can realize the reminding function for the target user, and the target user is not required to actively search in the shared space, which helps to simplify the operation of the target user. .
  • the permission setting may be performed on the shared content by sending a permission setting instruction to the server to restrict the sharing operation for the shared content. For example, it may be restricted that only the uploader of the shared content can implement the sharing operation, or the member of the specified one or more groups can be restricted from being able to perform the sharing operation, or the user above the specified authority level can be restricted from performing the sharing operation, etc. This is not a limitation.
  • the operation authority for the shared content set by the user for the target user may be indicated to the server, so that the server limits the target user to the sharing according to the operation authority.
  • the operation of the content implementation For example, the user can set the operation authority to only allow reading, only reading and editing, allowing reading and editing but not sharing, etc., and this specification does not limit this.
  • the user who is the sharer can limit the type of operation of the shared content as the target user of the shared party, and avoid the problem of leakage of information of the shared content.
  • an operation period for the shared content set by the user for the target user may be indicated to the server, so that the server gives the target user a temporary operation on the shared content.
  • the temporary operation authority is valid only during the operation period.
  • the user can set the temporary operation authority so that the temporary operation authority of the target user is set to allow only reading, only reading and editing, allowing reading and editing but not sharing. Etc., this specification does not limit this.
  • sharing restrictions can be performed on the shared content in the time dimension, so that in particular, if the target user itself does not have direct operation authority for the shared content, the risk that the shared content is leaked can be reduced.
  • FIG. 2C is a flowchart of a method for sharing shared content provided by an exemplary embodiment. As shown in FIG. 2C, the method is applied to a client side device (for example, the mobile phone 13, the PC 14, and the like shown in FIG. 1), and may include the following steps:
  • Step 202C Receive a sharing request initiated by a user, where the sharing request is related to the shared content in the shared space of the community.
  • the user may access the shared space associated with the community for the internal members of the community from the portal provided by the relevant functional interface of the community.
  • the user may not belong to the community, that is, the user is not an internal member of the community, but the user may access the shared space associated with the community through an portal provided by the community's public homepage or the like.
  • the community-related shared space may include at least one of the following: a shared space of the group, for example, the shared space may be a cloud disk rented, purchased, or built by the group; a shared subspace associated with a specific function in the shared space, for example, when the specific function is a financial management function, the corresponding shared subspace is used to store shared content such as financial related files; and the group belonging to the community corresponds to
  • the shared subspace for example, each department in the community respectively creates a corresponding group, and each group can divide the shared subspaces in the shared space for sharing between the group members in the same group. Sharing of content.
  • the user's rights information in the community matches the shared content, otherwise the user will not be able to view the shared content in the shared space of the community, and thus the sharing plan for the shared content cannot be implemented.
  • the rights information of the user in the community may include the rights information of the user in the organization structure of the group; of course, the rights information of the user in the group is not necessarily related to the organizational structure, such as separately set. Permission information, temporarily set permission information, permission information with space or time conditions, etc., are not limited in this specification.
  • the rights information of the user in the community may be predetermined.
  • the user's rights information in the community may be obtained upon receiving the access request.
  • this specification does not limit the timing of acquisition of the rights information.
  • the organizational structure of the community is divided into a plurality of permission categories according to a specific dimension, for example, when the specific dimension is a department, the group members of the same department may be divided into the same permission category, wherein each permission category You can include group members from one or more departments to achieve privilege isolation between departments in different privilege categories.
  • determining, according to the specific permission category with the management authority indicated by the permission information of the user, and the permission category indicated by the permission information of the shared content in the shared space determining that the shared space belongs to the specific permission The shared content of the category as the shared content that matches the permission information.
  • the shared content belonging to the privilege category 1 in the shared space may be considered to match the privilege information of the above-mentioned user, but in the shared space
  • the shared content attributed to the privilege category 2 may be considered to not match the privilege information of the above-mentioned user (for example, the "sales department" is divided into the privilege category 2, then the user does not have access to the shared content belonging to the "sales department” ).
  • the above specific dimensions may have many other options besides the department, and the specification does not limit this; for example, the specific dimension may also include a job level, and the group members of the same job level may be divided into the same Permission categories, where each permission category can include group members of one or more job levels.
  • the shared content that matches the rights information in the shared space may include at least one of the following: the shared content uploaded by the user, and the shared by the group members belonging to the specific permission type in the community.
  • the content for example, when the user and the department to which the other user belongs belong to the permission category 1, the shared content uploaded by the other user matches the permission information of the user, that is, the shared content uploaded by the user for the another user has Access rights, and when the department to which another user belongs belongs to the rights category 2, the shared content uploaded by the other user does not match the rights information of the user, that is, the user does not have access to the shared content uploaded by the other user.
  • Permission the management member of the group is set to be shared content belonging to the specific permission category, for example, although the department to which the other user belongs belongs to the permission category 2, the management user may actively upload the at least one user.
  • Part of the shared content is set to match the permission category 1 (the shared content can still be at the same time Arranged for permission category 2), so that the user uploads further rights information matches at least a portion shared content to the user, the at least a portion of the shared content that is uploaded to the said user has access to another user.
  • the permission category 1 the shared content can still be at the same time Arranged for permission category 2
  • the user uploads further rights information matches at least a portion shared content to the user, the at least a portion of the shared content that is uploaded to the said user has access to another user.
  • the organizational structure of the group may be divided into a plurality of privilege levels according to a specific dimension.
  • a specific dimension is a job grading level
  • the privilege level can be associated with the job tier to achieve privilege isolation between group members at different privilege levels, ie, group members with higher rank levels have higher privilege levels, and group members with lower rank tiers have lower privilege levels. Permission level.
  • the specific permission level with the management authority indicated by the permission information of the user, and the permission level indicated by the permission information of the shared content in the shared space may be determined that the permission level in the shared space is not higher than
  • the shared content of a specific privilege level is used as the shared content that matches the privilege information.
  • the specific privilege level indicated by the privilege information of the user is 3, the shared content in the shared space whose privilege level is not higher than the level 3 (ie, 0-3) is considered to match the privilege information of the user.
  • the shared content whose privilege level is higher than level 3 (such as level 4, level 5 or higher) is considered to not match the privilege information of the above user.
  • each privilege category may include one or more group members of the position level, for example, all group members of the "General Manager” have a privilege level of 5, and all group members of the "finance room” have a privilege level of 4
  • the level of authority of all group members of the "Sales" department is level 3.
  • the shared content that matches the rights information in the shared space includes at least one of the following: the shared content uploaded by the user; and the group member whose privilege level is not higher than the specific privilege level in the community
  • the shared content for example, when the privilege level of the user is 3, the shared content uploaded by another user whose privilege level is 2, because the privilege level of the user is higher, it can be considered to match the privilege level of the user. That is, the user has access rights to the shared content uploaded by the other user, and the shared content uploaded by another user with the privilege level of 5 is considered to be unmatched by the user because the privilege level of the user is lower.
  • the permission level that is, the user does not have access to the shared content uploaded by the other user; the management member of the group is set to the shared content whose permission level is not higher than the specific permission level, such as although the above-mentioned another user The permission level is 5, but the management user can actively upload at least one of the other users.
  • the shared content is set to match the privilege level 3 and is not greater than the specific privilege level indicated by the user privilege information, so that the at least part of the shared content uploaded by the further user matches the privilege information of the user, that is, the user
  • the at least one part of the shared content uploaded by another user has access rights.
  • the rights information of the shared content in the shared space may be determined in various ways.
  • the rights information of the uploader may be used as the rights information of the shared content. For example, when the uploader belongs to the rights type 1, the rights information of the shared content uploaded by the uploader is set to the permission type 1, and then When the uploader's permission level is 3, the permission information of the shared content uploaded by the uploader is set to the permission level 3.
  • the rights information that is set by the uploader for the shared content, and the set rights information meets the rights information of the uploader; for example, when the uploader belongs to the rights type 1, the uploader The permission information of the uploaded shared content can be set to the permission type 1 and cannot be set to the permission type 2, and when the uploader belongs to both the permission type 1 and the permission type 2, the uploader can upload the shared content.
  • the permission information sets at least one of the permission type 1 and the permission type 2, and when the uploader's permission level is 3, the uploader can set the permission information of the uploaded shared content to the permission level 0-3.
  • the rights information may be set by the administrative user of the community for the shared content.
  • the administrative user of the group refers to a user who has administrative rights to the group, and the administrative user may be a group member of the group, such as a creator or administrator of the group, or the management member may be not Group members of the group, such as super administrators.
  • the storage path matching the permission information in the shared space may be determined according to the rights information of the user in the community, and then the shared content under the determined storage path is determined to be a match.
  • the shared content of the permission information may be stored in advance in the same storage path of the shared space (such as in the same folder) according to the rights information of the shared content, so that by determining the storage path that matches the rights information of the user, All shared content under the storage path is quickly determined as the shared content that matches the user's permission information.
  • Step 204C Send a sharing instruction for the shared content to the server, where the sharing instruction is used to instruct the server to share the shared content to the target user specified by the user.
  • a sharing instruction for the shared content may be sent to the server in response to the detected user operation, so that the server shares the shared content to the target user specified by the user. So that the target user can view the shared content, and even perform editing and the like on the shared content.
  • the server may send the shared content directly to the target user; or the server may send the access link of the shared content to the target user, so that the target user can share the share through the access link.
  • the content is accessed, for example, the access link may be a storage path of the shared content.
  • the target user may include any user specified by the user, and this specification does not limit this.
  • the target user may belong to the group to which the user belongs, or may not be related to the group; for example, from the perspective of the authority, the target user may have the authority corresponding to the shared content, and You may not have permission for this shared content.
  • the sharing scheme can be made based on the above sharing scheme.
  • Target users can also view, edit, and other shared content to facilitate project collaboration such as cross-group.
  • the above-mentioned sharing scheme can realize the reminding function for the target user, and the target user is not required to actively search in the shared space, which helps to simplify the operation of the target user. .
  • the permission setting may be performed on the shared content by sending a permission setting instruction to the server to restrict the sharing operation for the shared content. For example, it may be restricted that only the uploader of the shared content can implement the sharing operation, or the member of the specified one or more groups can be restricted from being able to perform the sharing operation, or the user above the specified authority level can be restricted from performing the sharing operation, etc. This is not a limitation.
  • the operation authority for the shared content set by the user for the target user may be indicated to the server, so that the server limits the target user to the sharing according to the operation authority.
  • the operation of the content implementation For example, the user can set the operation permission to only allow reading, only allow reading and editing, allow reading and editing but do not allow sharing, etc., and this specification does not limit this.
  • the user who is the sharer can limit the type of operation of the shared content as the target user of the shared party, and avoid the problem of leakage of information of the shared content.
  • an operation period for the shared content set by the user for the target user may be indicated to the server, so that the server gives the target user a temporary operation on the shared content.
  • the temporary operation authority is valid only during the operation period.
  • the user can set the temporary operation authority so that the temporary operation authority of the target user is set to allow only reading, only reading and editing, allowing reading and editing but not sharing. Etc., this specification does not limit this.
  • sharing restrictions can be performed on the shared content in the time dimension, so that in particular, if the target user itself does not have direct operation authority for the shared content, the risk that the shared content is leaked can be reduced.
  • FIG. 3 is a flowchart of a method for managing rights in a shared space according to an exemplary embodiment. As shown in FIG. 3, the method is applied to a server device (such as the server 11 shown in FIG. 1), and may include the following steps:
  • Step 302 Obtain permission information of the user in the community.
  • the rights information of the user in the community may include the rights information of the user in the organization structure of the group; of course, the rights information of the user in the group is not necessarily related to the organizational structure, such as separately set. Permission information, temporarily set permission information, permission information with space or time conditions, etc., are not limited in this specification.
  • the organizational structure of the community is divided into a plurality of permission categories according to a specific dimension, for example, when the specific dimension is a department, the group members of the same department may be divided into the same permission category, wherein each permission category You can include group members from one or more departments to achieve privilege isolation between departments in different privilege categories.
  • determining, according to the specific permission category with the management authority indicated by the permission information of the user, and the permission category indicated by the permission information of the shared content in the shared space determining that the shared space belongs to the specific permission The shared content of the category as the shared content that matches the permission information.
  • the shared content belonging to the privilege category 1 in the shared space may be considered to match the privilege information of the above-mentioned user, but in the shared space
  • the shared content attributed to the privilege category 2 may be considered to not match the privilege information of the above-mentioned user (for example, the "sales department" is divided into the privilege category 2, then the user does not have access to the shared content belonging to the "sales department” ).
  • the above specific dimensions may have many other options besides the department, and the specification does not limit this; for example, the specific dimension may also include a job level, and the group members of the same job level may be divided into the same Permission categories, where each permission category can include group members of one or more job levels.
  • the shared content that matches the rights information in the shared space may include at least one of the following: the shared content uploaded by the user, and the shared by the group members belonging to the specific permission type in the community.
  • the content for example, when the user and the department to which the other user belongs belong to the permission category 1, the shared content uploaded by the other user matches the permission information of the user, that is, the shared content uploaded by the user for the another user has Access rights, and when the department to which another user belongs belongs to the rights category 2, the shared content uploaded by the other user does not match the rights information of the user, that is, the user does not have access to the shared content uploaded by the other user.
  • Permission the management member of the group is set to be shared content belonging to the specific permission category, for example, although the department to which the other user belongs belongs to the permission category 2, the management user may actively upload the at least one user.
  • Part of the shared content is set to match the permission category 1 (the shared content can still be at the same time Arranged for permission category 2), so that the user uploads further rights information matches at least a portion shared content to the user, the at least a portion of the shared content that is uploaded to the said user has access to another user.
  • the permission category 1 the shared content can still be at the same time Arranged for permission category 2
  • the user uploads further rights information matches at least a portion shared content to the user, the at least a portion of the shared content that is uploaded to the said user has access to another user.
  • the organizational structure of the group may be divided into a plurality of privilege levels according to a specific dimension.
  • a specific dimension is a job grading level
  • the privilege level can be associated with the job tier to achieve privilege isolation between group members at different privilege levels, ie, group members with higher rank levels have higher privilege levels, and group members with lower rank tiers have lower privilege levels. Permission level.
  • the specific permission level with the management authority indicated by the permission information of the user, and the permission level indicated by the permission information of the shared content in the shared space may be determined that the permission level in the shared space is not higher than
  • the shared content of a specific privilege level is used as the shared content that matches the privilege information.
  • the specific privilege level indicated by the privilege information of the user is 3, the shared content in the shared space whose privilege level is not higher than the level 3 (ie, 0-3) is considered to match the privilege information of the user.
  • the shared content whose privilege level is higher than level 3 (such as level 4, level 5 or higher) is considered to not match the privilege information of the above user.
  • each privilege category may include one or more group members of the position level, for example, all group members of the "General Manager” have a privilege level of 5, and all group members of the "finance room” have a privilege level of 4
  • the level of authority of all group members of the "Sales" department is level 3.
  • the shared content that matches the rights information in the shared space includes at least one of the following: the shared content uploaded by the user; and the group member whose privilege level is not higher than the specific privilege level in the community
  • the shared content for example, when the privilege level of the user is 3, the shared content uploaded by another user whose privilege level is 2, because the privilege level of the user is higher, it can be considered to match the privilege level of the user. That is, the user has access rights to the shared content uploaded by the other user, and the shared content uploaded by another user with the privilege level of 5 is considered to be unmatched by the user because the privilege level of the user is lower.
  • the permission level that is, the user does not have access to the shared content uploaded by the other user; the management member of the group is set to the shared content whose permission level is not higher than the specific permission level, such as although the above-mentioned another user The permission level is 5, but the management user can actively upload at least one of the other users.
  • the shared content is set to match the privilege level 3 and is not greater than the specific privilege level indicated by the user privilege information, so that the at least part of the shared content uploaded by the further user matches the privilege information of the user, that is, the user The at least one part of the shared content uploaded by another user has access rights.
  • the access rights in this specification may include rights to perform one or more operations such as reading, modifying, deleting, etc. for the shared content.
  • the rights information of the shared content in the shared space may be determined in various ways.
  • the rights information of the uploader may be used as the rights information of the shared content. For example, when the uploader belongs to the rights type 1, the rights information of the shared content uploaded by the uploader is set to the permission type 1, and then When the uploader's permission level is 3, the permission information of the shared content uploaded by the uploader is set to the permission level 3.
  • the rights information that is set by the uploader for the shared content, and the set rights information meets the rights information of the uploader; for example, when the uploader belongs to the rights type 1, the uploader The permission information of the uploaded shared content can be set to the permission type 1 and cannot be set to the permission type 2, and when the uploader belongs to both the permission type 1 and the permission type 2, the uploader can upload the shared content.
  • the permission information sets at least one of the permission type 1 and the permission type 2, and when the uploader's permission level is 3, the uploader can set the permission information of the uploaded shared content to the permission level 0-3.
  • the rights information may be set by the administrative user of the community for the shared content.
  • the administrative user of the group refers to a user who has administrative rights to the group, and the administrative user may be a group member of the group, such as a creator or administrator of the group, or the management member may be not Group members of the group, such as super administrators.
  • Step 304 Manage, according to the rights information, the access rights of the user to the shared content in the shared space related to the community.
  • the community-related shared space may include at least one of the following: a shared space of the group, for example, the shared space may be a cloud disk rented, purchased, or built by the group; a shared subspace associated with a specific function in the shared space, for example, when the specific function is a financial management function, the corresponding shared subspace is used to store shared content such as financial related files; and the group belonging to the community corresponds to
  • the shared subspace for example, each department in the community respectively creates a corresponding group, and each group can divide the shared subspaces in the shared space for sharing between the group members in the same group. Sharing of content.
  • the user's access rights to the shared content may be consistent with the rights information, thereby applying the rights information in the community to the rights management in the process of accessing the shared content.
  • the update data of the rights information may be obtained, and the access rights of the user are updated correspondingly according to the update data.
  • the user's access rights to the shared content can also be automatically updated, eliminating the need for separate rights maintenance management.
  • the “permission information of a user in a group” is the authority information of the user in the organizational structure of the group
  • the user may be automatically determined based on the entry, departure, position transfer, department transfer, etc. appearing in the organization structure of the group.
  • the update data of the permission information, and based on the update data an automatic update of the access rights is implemented.
  • FIG. 4 to FIG. 5 are schematic diagrams of an organizational structure of an enterprise AA provided by an exemplary embodiment; as shown in FIG. 4, it is assumed that the enterprise AA includes a department 1, a department 2, a department 8, and the like. In some departments, the enterprise members of the enterprise AA have different job levels, taking the department 2 and the department 3 shown in Figure 5 as examples.
  • the enterprise members of the department 2 include the user A-user D
  • the enterprise members of the department 3 include the user E- User H, where User A and User E have a higher L4 rating, while User B-User D, User F-User H have a lower L3 rating.
  • the corresponding authority information can be set for the enterprise members of the enterprise AA, so that when the enterprise members access the "Enterprise WeChat" corresponding to the shared space of the enterprise AA, based on The own permission information implements a reasonable access operation to the shared content in the shared space.
  • the authority information of the enterprise members of the enterprise AA can be set in various ways to achieve different rights management effects. This specification does not limit the dimensions adopted; for ease of understanding, the following departments and positions are used. The two dimensions of the level are taken as an example to describe the access scheme of the shared space of this specification.
  • FIG. 6 is a schematic diagram of an access interface of a shared space provided by an exemplary embodiment; as shown in FIG. 6, it is assumed that the user A starts the enterprise WeChat client running on the electronic device, and triggers the enterprise WeChat client to provide
  • the "cloud disk” function option 602 can open the access interface 600 of the shared space of the enterprise AA on the "Enterprise WeChat".
  • each department can be divided into independent permission categories, such that department 1 corresponds to authority category 1, department 2 corresponds to permission category 2, and so on, and the authority information of enterprise members of each department is corresponding to the department.
  • the authority information of the user A is the permission category 2
  • the authority information of the other enterprise members such as the user B-user D of the department 2 is also the permission category 2.
  • the organizational structure of the enterprise AA can be divided into several permission categories, thereby implementing privilege isolation among enterprise members of different privilege categories. For example, as shown in FIG. 6 , when the rights information of the user A belongs to the rights category 2, the user A can only view the shared content belonging to the rights category 2 on the access interface 600, such as the “personal weekly report” uploaded by the user A itself.
  • content sharing can also be achieved between different permission categories.
  • the permission information of the shared content uploaded to the shared space defaults to the uploader's permission information.
  • the user H of the department 3 uploads the shared content "work skill.doc", because the permission information of the user H is the permission category. 3. Therefore, the permission information of the shared content "work skill.doc” defaults to the permission category 3, so that the user A cannot view the shared content "work skill.doc" in the access interface 600 shown in FIG.
  • the user H or the administrator of the enterprise AA can edit the permission information of the shared content "work skill.doc", for example, the permission information of the shared content "work skill.doc” can be edited as "permission category 3 and authority" If the category 2" or "all (ie, matches all permission categories)", then the permission information of the shared content "work skill.doc” can be considered to match the permission information of the user A, so that the user A can pass as shown in FIG.
  • the access interface 700 views the shared content "Work Tips.doc".
  • the dimension adopted is the position level
  • the position level of the enterprise members in the organizational structure in the enterprise AA it can be divided into different permission levels, and the authority information of each enterprise member is the permission level.
  • the corresponding authority information may be the authority level 4
  • the position level of the user B-user D and the user F-user H is the L3 level
  • the corresponding permission information may be the permission level 3; wherein the higher permission level may cover the lower permission level, so that a larger amount of shared content in the shared space can be accessed.
  • the organizational structure of the enterprise AA can be divided into several permission levels, thereby realizing the permission isolation based on the permission level. For example, as shown in FIG. 8, when the rights information of the user C belongs to the privilege level 3, the user C can only view the shared content that is not higher than the privilege level 3 on the access interface 800, such as the "personality” uploaded by the user C itself. Weekly newspaper-C.xls” and other documents, such as "personal weekly report-B.xls” uploaded by user B, "personal weekly report-D.xls” and “project interim report.doc” uploaded by user D, "user H uploaded” Work Skills .doc", etc., while shared content uploaded by User A, User E, etc.
  • privilege level 4 cannot be presented in the access interface 800 browsed by User C because User C is determined to have a high privilege level.
  • Shared content at level 3 does not have access.
  • the permission information of the shared content uploaded to the shared space is the permission information of the uploader by default.
  • the user E of the department 3 uploads the shared content "department quarterly plan.doc", because the permission information of the user E is the permission. Level 4, and thus the permission information of the shared content "Department Quarterly Plan.doc” defaults to the permission level 4, so that the user C cannot view the shared content "Department Quarterly Plan.doc” in the access interface 800 shown in FIG.
  • the user E who is the uploader or the administrator of the enterprise AA can edit the permission information of the shared content "department quarterly plan.doc", for example, the permission information of the shared content "department quarterly plan.doc” can be edited as the authority. Level 3, then the rights information of the shared content "Department Quarterly Plan.doc” can be considered to match the rights information of the user C, so that the user C can view the shared content "Department Quarter” through the access interface 1000 as shown in FIG. Planning .doc".
  • the rights information in the organization structure can be applied to the rights management of the shared content, so that the enterprise WeChat server does not need to implement additional rights control, and the enterprise members can base themselves on accessing the shared space.
  • the permission information directly browses the matched shared content, and does not need to resort to additional permission verification means, so that the enterprise members can quickly access the shared content.
  • FIG. 11 is a schematic diagram of an entry display interface provided by an exemplary embodiment. Taking user A as an example, it is assumed that the enterprise WeChat client corresponding to the user A can provide the portal display interface 1100 as shown in FIG. 11 , and the portal display interface 1100 can provide the “weekly report”, “sales report”, and “development verification”.
  • the shared subspace entry of functions such as "meeting record” enables user A to quickly enter the shared subspace entry of the corresponding function by triggering the shared subspace entry.
  • the "new" option in the portal display interface 1100 can create a shared subspace of more functions, and form a corresponding shared subspace entry in the portal presentation interface 1100, while the "edit” option in the portal display interface 1100 is displayed through the portal.
  • the enterprise WeChat client can switch to the access interface 1200 as shown in FIG. 12, which can display the function belonging to the "weekly” function.
  • Shared content For example, when the department dimension rights management scheme is adopted, user A can see the shared content attributed to the rights category 2, such as the shared content "personal weekly report-A.xls" and "personal” uploaded by user A-user D in FIG.
  • the shared subspace in addition to the "shared space” and the "shared subspace", the shared subspace can be further partitioned to achieve multi-level partitioning of the "shared space".
  • the access interface 1200 can include a spatial path 1202 as shown in FIG. 12, so that the user A can implement fast jumps between different levels in the shared space.
  • the portal display interface 1100 shown in FIG. 11 can be quickly returned; when the number of levels is more, the cross-level interface jump can also be implemented, thereby
  • the convenience of the spatial path 1202 is further embodied.
  • enterprise members can share the shared content in a variety of ways.
  • the user A can upload the shared content that is desired to be shared to the shared subspace corresponding to the “Weekly” function by triggering the upload option 1204 in the interface 1200; and the user A can trigger the content.
  • the editing option 1206 in the interface 1200 is accessed to delete, modify, and the like the shared content that has been uploaded.
  • corporate members are usually only able to edit the shared content uploaded by themselves, and cannot edit the shared content uploaded by other users. Of course, users with higher management rights, such as administrators, may also have shared shares uploaded by other users. The right to edit content.
  • the user A can upload the shared content that is desired to be shared to the shared space of the enterprise AA by triggering the upload option 604 in the access interface 600; and the user A can trigger the access interface.
  • the editing option 606 in 600 deletes, modifies, and the like the shared content that has been uploaded.
  • the enterprise WeChat can provide a group function, so that the enterprise members can share the shared content through the related interface of the group function.
  • FIG. 13 is a schematic diagram of a group session interface provided by an exemplary embodiment; enterprise WeChat can provide a group for enterprise AA, and enterprise members of the enterprise AA can be added as group members of the group. And the group member can implement functions such as communication through the group session interface 1300 shown in FIG.
  • the enterprise WeChat client may exhibit a selection window 1304 including a number of function entries, such as the selection window 1304 shown in FIG. Includes entry options that correspond to features such as Add Member, Conference Call, Send Mail, and Receive Job.
  • FIG. 14 is a schematic diagram of a task initiation interface of a job receiving function provided by an exemplary embodiment.
  • the enterprise WeChat client may present the task initiation interface 1400 as shown in FIG. 14 to the user A to initiate the interface based on the task by the user A.
  • the 1400 initiates a homework task.
  • the task initiation interface 1400 can include a custom description area 1402 for the user A to enter descriptive information for the receiving job task to describe its requirements for the job submitted by the participant of the home task.
  • the task initiation interface 1400 can include a template addition option 1404, based on the detected triggering operation for adding the option 1404 to the template, for the user A to add a job template for the receiving task, and the participation of the receiving task
  • the user can download the job template, complete the job content based on the job template, and ensure that all participants' content can be constrained by the format of the job template, so that the content is consistent in content format, which is convenient for browsing and subsequent operations. Merge operation.
  • the storage path shown in FIG. 14 is “Enterprise AA/Weekly Report”, and the storage path belongs to a shared subspace corresponding to the “Weekly” function in the shared space corresponding to the enterprise AA, and the storage path is used for storing and receiving. Jobs submitted by participants of the job task, which will be shared content in the shared space (ie, shared subspace); wherein the task initiation interface 1400 can include a path edit option 1406 for the user A to trigger the path
  • the above storage path is edited by editing option 1406.
  • the enterprise WeChat client can issue a corresponding receiving task to the enterprise member of the enterprise AA through the group session interface 1300, for example, the receiving task can be performed.
  • the group communication message 1500 shown in FIG. 15 the specification is of course not limited to the form adopted herein.
  • FIG. 16 is a schematic diagram of a communication session interface of a participant side of a job receiving task according to an exemplary embodiment. It is assumed that the user C can present the communication session interface 1600 as shown in FIG. 16 through the enterprise WeChat client running on the used electronic device; the following takes the user C's perspective as an example to perform related operations on the participants of the receiving task. description.
  • the communication session interface 1600 can show the group communication message 1602 corresponding to the receiving job task issued by the user A, and the user C can participate in the corresponding receiving task by triggering the group communication message 1602.
  • FIG. 17 is a schematic diagram of uploading shared content provided by an exemplary embodiment.
  • the group communication message 1602 may include an access link for the task processing interface 1700 as shown in FIG. 17, and after detecting that the user C triggers the group communication message 1602, the enterprise WeChat client may open the task. Processing interface 1700.
  • the task processing interface 1700 can include a description information display area 1702 for displaying the description information input by the user A in the custom description area 1402 as shown in FIG. 14 to facilitate the user C to know that he is present. The operations that need to be completed in the job task.
  • the task processing interface 1700 can include an attachment viewing area 1704, which can be used by the user C to view attachments carried by the receiving task, such as the "Weekly Report Template.xls" shown in FIG.
  • the task processing interface 1700 can include a job upload area 1706 for the user C to upload a job that he or she wishes to submit for the received job task.
  • the enterprise WeChat client can provide any form of job uploading, and this manual does not limit this.
  • a possible job uploading method is “drag and drop uploading”, and user C can drag and drop the job that is desired to be uploaded to the job uploading area 1706, and the enterprise WeChat client can detect the dragging operation and complete the subsequent uploading operation. .
  • the enterprise WeChat client can directly complete the job submission, and store the job in the corresponding storage path in the shared space, which is equivalent to realizing the pair.
  • the content of the job is shared.
  • the enterprise WeChat client can store the job to the share after detecting that the user C drags the job to the job upload area 1706 (for example, "personal weekly report - C.xls" shown in FIG. 17).
  • FIG. 18 is a schematic diagram of another upload sharing content provided by an exemplary embodiment.
  • the user C does not need to actively trigger the group communication message 1602 shown in FIG. 16 , and can directly drag the job to be uploaded to the group communication interface 1600 .
  • the user C can drag and drop the file "personal weekly report - C.xls" to the group communication interface 1600, and the enterprise WeChat client can detect the dragged file "personal weekly report - C.xls", and if the enterprise The WeChat client also detects that the group communication interface 1600 receives the receiving job task that has not been processed by the user C.
  • the enterprise WeChat client can actively display the job uploading area 1802 and the message sending area 1804 as shown in FIG.
  • the enterprise WeChat client can determine that the user C needs to send the file "personal weekly report - C.xls” as the chat content to the group "enterprise AA", and To the file "Personal weekly -C.xls” transmission operation.
  • the user A-user D belongs to the department 2 as shown in FIG. 4 to FIG. 5, and the position level of the user A is the L4 level, and the user B-user D
  • the job level is the L3 level, so it can be determined that the user A-user D belongs to the group category 2 corresponding to the department 2, and the user A has a permission level of 4, and the user B-user D has a permission level of 3.
  • the qualified user A-user D can only access the shared content of the group category 2 corresponding to the department 2 to which he belongs, and for the position level dimension, the limited user A-user D can only be lower than the own authority.
  • the shared content of the level is accessed, then: when the user A accesses the storage path corresponding to the receiving task, the user A-user D uploads the job in the access interface 1200 shown in FIG. 12; When the user C accesses the storage path corresponding to the above-mentioned receiving task, only the job uploaded by the user C is displayed in the access interface 1900 shown in FIG. 19, and the user member of the department 2 or other departments cannot be viewed. operation.
  • FIG. 20 is a schematic diagram of an automatic synchronization file provided by an exemplary embodiment. As shown in FIG. 20, it is assumed that the file "Department Conference Projection.ppt" is included in the access interface 2000, and User A expects both User B and User C to acquire and view the file "Department Conference Projection.ppt". Although the file "Department Conference Projection.ppt” can be accessed and obtained according to the rights information of User B and User C in Enterprise AA, User B and User C may still not acquire the file in time due to various reasons such as forgetting. “Departmental Conference Projection.ppt” has affected the related work that User A originally intended to carry out.
  • the user A can trigger the file “department conference projection.ppt” in the access interface 2000 to evoke the synchronization configuration interface 2001 as shown in FIG. 20, so that the user A can implement the synchronization configuration interface 2001.
  • the file "Department Conference Projection.ppt” is automatically synchronized.
  • the synchronization configuration interface 2001 can include the option “synchronize to their own computer” and the option “synchronize to the employee's computer”
  • the option “synchronize to their own computer” can synchronize the file "department conference projection.ppt” to the On the electronic device used by User A
  • the option "Sync to Employee's Computer” can synchronize the file "Department Conference Projection.ppt” to the electronic device used by other users.
  • the employee selection window 2002 as shown in FIG. 20 can be evoked for the user A to select the target synchronization object of the file "department conference projection.ppt", such as the above user. B and user C, etc.
  • the enterprise WeChat server can automatically push the file “department conference projection.ppt” to the electronic device used by the user B and the user C (for example, the user B uses
  • the electronic device may include an electronic device that is logged in with the user account of the user B, or an electronic device that has logged in the user account of the user B, etc., so that the user B and the user C can separately store from the local device of the electronic device used by the user.
  • the space reads the file "Department Conference Projection.ppt" without the user B and User C manually downloading.
  • an electronic device used by the user B is taken as an example.
  • the electronic device runs an enterprise WeChat client. After receiving the file “department conference projection.ppt” pushed by the enterprise WeChat server, the enterprise WeChat client can find out whether there is an old version of the file in the local storage space. Project .ppt", if it exists, replace the old version of the file with the file pushed by the enterprise WeChat server, so as to achieve automatic update of the file version.
  • FIG. 21 is a schematic diagram of an online editing file provided by an exemplary embodiment.
  • Enterprise WeChat supports users to edit files online.
  • the file may include files in the above shared space, files transmitted by users through enterprise WeChat, etc., and this specification does not limit this.
  • the file “Department Conference Projection.ppt” is uploaded to the shared space by the user A, and can be located in the file storage server maintained by the enterprise WeChat server shown in FIG.
  • an online editing operation for the file "department conference projection.ppt” may be triggered, so that the file editing server maintained by the enterprise WeChat server responds to the online The editing operation realizes online editing processing of the file "department conference projection.ppt”.
  • the enterprise WeChat server can send the online editing interface for the file "participation conference projection.ppt" to the enterprise WeChat client of user A, user B and user C respectively, to be respectively user A, user B and user C Browsing and issuing an online editing instruction for the file "Department Conference Projection.ppt” based on the online editing interface, and then implementing the online "Department Conference Projection.ppt” file by the file editing server based on the received online editing instruction Edit operation.
  • By implementing the online editing operation on the file "Department Conference Projection.ppt” User A, User B and User C do not need to download and edit the file "Department Conference Projection.ppt" to avoid creating multiple files and easily cause version confusion. To help reduce the probability of error.
  • User A, User B, and User C may have the same editing rights for the file "Department Conference Projection.ppt"; in another embodiment, User A, User B, and User C for the file " The department meeting projection .ppt" can have different editing rights, and according to the file "department conference projection.ppt", respectively, the user A, user B and user C are respectively divided into the allowed editing contents, so that user A, user B And the user C can only perform an online editing operation on the corresponding editable content corresponding to the user C, thereby avoiding the formation of an erroneous operation.
  • FIG. 22 is a schematic diagram of triggering a sharing operation on shared content according to an exemplary embodiment.
  • FIG. 22 shows the access interface 2200 when the user C accesses the shared space of the enterprise AA, and the shared content matching the right of the user C is shown in the access interface 2200.
  • User C wishes to share the shared document "Department Quarterly Plan.doc”.
  • a corresponding operation option window 2201 may be displayed, and the operation option window 2201 includes operation options such as "share” and “permission setting” to Used to implement the corresponding action for the shared document "Department Quarterly Plan.doc".
  • FIG. 23 is a schematic diagram of a sharing setting interface provided by an exemplary embodiment.
  • the sharing setting interface 2300 as shown in FIG. 23 can be illustrated, so that the user C can set the related document "department quarter plan.doc". .
  • the user C can select the shared object of the shared document “Department Quarterly Plan.doc” by triggering the “+Add Shared Object” option in the sharing setting interface 2300, thereby the shared document “Department Quarterly Planning” .doc” is shared to the shared object.
  • the selected shared objects in FIG. 23 include “user M”, “user N”, and “group-item X", etc., of course, user C can also select fewer or more. Shared object.
  • User C can delete the selected shared object. For example, the left side of "User M", “User N", and “Group-Item X" shown in Figure 23 are displayed with the corresponding "Delete” option, which can be used for deleting. The corresponding shared object.
  • the shared object of the shared document "Department Quarterly Plan.doc” may be an individual, such as “User M”, “User N”, etc. as shown in FIG. 23; sharing of the shared document "Department Quarterly Plan.doc”
  • the object may also be a group, such as "Group-Item X" shown in FIG. 23; in fact, the present specification does not limit the type of the shared object.
  • the shared object may be an internal member of the enterprise AA, such as "user M” and the like shown in FIG. 23; the shared object may not be an internal member of the enterprise AA, for example, "user N" shown in FIG. 23 belongs to Enterprise BB does not belong to enterprise AA.
  • the shared object may be an internal group of the enterprise AA (ie, the group members are internal members of the enterprise AA); or, may be a cooperative group between the enterprise AA and other enterprises (ie, the group members are The internal members of the enterprise AA and other group members are not internal members of the enterprise AA, such as the "group-item X" shown in FIG.
  • the user C can set the operation authority of each shared object for the shared document "department quarter plan.doc", for example, the operation permission corresponding to the shared object "user M” shown in FIG. 23 is “editable”.
  • the operation permission corresponding to the shared object "user N” is "can be viewed", and the operation permission corresponding to the shared object “group-item X” is “editable”.
  • the user C can adjust the operation authority of each shared object according to actual needs; for example, for the shared object "user M", all the alternative operations can be called up by triggering the ⁇ identifier on the right side of the "can be edited”. Permissions for users C to view and select.
  • the validity period of the operation authority may also be set, so that the operation authority of the shared object for the shared document "department quarterly plan.doc" is the temporary operation authority, and is valid only in the operation time period corresponding to the validity period.
  • User C can set the validity period of the shared document "Department Quarterly Plan.doc” so that the validity period is applied to all shared objects; or, user C can separately set each shared object separately.
  • the user C may select at least a part of the group members, so that the shared document "department quarterly plan.
  • the doc is shared to the at least part of the group members and is not shared to the unselected group members. For example, the member selection situation corresponding to the shared object "group-item X" in FIG.
  • FIG. 24 is a schematic diagram of a communication session interface provided by an exemplary embodiment.
  • the user C shares the shared document "Department Quarterly Plan.doc" to the user M as an example.
  • the communication session between the user C and the user M can be performed.
  • the communication session message 2401 for the shared document "Department Quarterly Plan.doc” can be seen, and the user M can trigger the communication session message 2401.
  • To directly open the shared document "Department Quarterly Plan.doc” or the shared document "Department Quarterly Plan.doc” in the shared space corresponding to the access interface (similar to the access interface 2200 shown in Figure 22).
  • the shared document “Department Quarterly Plan.doc” can be directly sent to the shared object such as the user M, that is, after the user M receives the communication session message 2401.
  • the shared document "Department Quarterly Plan.doc” can be directly stored to the electronic device used by the user M or the cloud storage space corresponding to the user M.
  • the access link of the shared document "Department Quarterly Plan.doc” can be sent to the user M, so that the user M can trigger the shared document "Department Quarterly Plan.doc” in the shared space by triggering the communication session message 2401. Remote access; of course, user M can also download or dump the shared document "Department Quarterly Plan.doc” from the shared space, or may also be allowed to perform operations such as downloading or dumping based on permission restrictions.
  • FIG. 25 is a schematic diagram of permission setting for shared content provided by an exemplary embodiment; still taking the shared document “Department Quarterly Plan.doc” as an example, and assumes that user C has the department quarterly plan for the shared document.
  • .doc performs the operation authority of the rights setting, then in response to the user C's selection operation of the "rights setting” option in the operation option window 2201, the rights setting interface 2500 as shown in FIG. 25 can be displayed, so that the user C can Share the document "Department Quarterly Plan.doc" for permission settings.
  • the configurable permissions options for the shared document "Department Quarterly Plan.doc” may include “Anyone can view”, “Anyone can view/edit/share", "A designated member can view/edit/share", “Close the link” and so on.
  • any user who has permission to match the shared document "Department Quarterly Plan.doc” can view the shared document "Department Quarterly Plan.doc”.
  • Edit or share an action For example, when set to "designate members can view/edit/share", user C can set some users, group members, etc. to view, edit, or share the shared document "department quarter plan.doc”. For example, when set to "close link”, sharing operations for the shared document "Department Quarterly Plan.doc" are not allowed.
  • the mobile group office platform can be unified to achieve unified management of rights and improve management efficiency.
  • FIG. 26 is a schematic structural diagram of an apparatus provided by an exemplary embodiment.
  • the device includes a processor 2602, an internal bus 2604, a network interface 2606, a memory 2608, and a non-volatile memory 2610, and may of course include hardware required for other services.
  • the processor 2602 reads the corresponding computer program from the non-volatile memory 2610 into the memory 2608 and then operates to form a shared space access device at a logical level.
  • one or more embodiments of the present specification do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each.
  • a logical unit which can also be a hardware or logic device.
  • the access device of the shared space may include:
  • the access request receiving unit 2701 receives an access request of the user for the shared space associated with the community
  • the content determining unit 2702 determines, according to the rights information of the user in the community, the shared content that matches the rights information in the shared space to provide to the user.
  • the rights information includes rights information of the user in an organization structure of the community.
  • the method further includes: a rights obtaining unit 2703, which acquires rights information of the user in the community.
  • the community-related shared space includes at least one of the following:
  • a shared space of the community a shared subspace related to a specific function in the shared space of the community, and a shared subspace corresponding to a group belonging to the community.
  • the organization structure of the community is divided into a plurality of permission categories according to a specific dimension; the content determining unit 2702 is specifically configured to:
  • the shared content in the shared space that matches the permission information includes at least one of the following:
  • the shared content uploaded by the user, the shared content uploaded by a group member belonging to the specific permission type in the community, and the management member of the community are set as shared content belonging to the specific permission category.
  • the organization structure of the community is divided into a plurality of permission levels according to a specific dimension; the content determining unit 2702 is specifically configured to:
  • the shared content in the shared space that matches the permission information includes at least one of the following:
  • the shared content uploaded by the user, the shared content uploaded by the group member whose permission level is not higher than the specific permission level, and the management member of the group are set to be not higher than the specific permission level. Share content.
  • the specific dimension includes at least one of the following: a department, a job level.
  • the permission information of the shared content in the shared space is from:
  • the content determining unit 2702 is specifically configured to:
  • the shared content under the determined storage path is determined to be the shared content that matches the permission information.
  • the method further includes: a path display unit 2704 or a content display unit 2705;
  • the path display unit 2704 is configured to display the determined storage path to the user, so that the user accesses the shared content that matches the permission information through the storage path;
  • the content presentation unit 2705 is configured to display the shared content under the determined storage path to the user, wherein the storage path is invisible to the user.
  • it also includes:
  • the content selection unit 2706 determines a plurality of shared content selected by the user from the shared content matching the permission information
  • the information extracting unit 2707 extracts the recording information of the plurality of shared contents in a specific information recording format to merge and generate new shared content.
  • the method further includes: a storage unit 2708, configured to store the shared content uploaded by the group member of the community for the upload task;
  • the content determining unit 2702 is specifically configured to:
  • the rights information of the user is greater than the rights information of any group member, determining that the shared content that matches the rights information includes the shared content uploaded by the user for the uploading task, and the The shared content uploaded by the uploading task;
  • the rights information of the user is not greater than the rights information of the any group member, determining that the shared content that matches the rights information includes the shared content uploaded by the user for the upload task.
  • it also includes:
  • the determining unit 2709 is configured to determine a file to be synchronized and a file synchronization object selected by the management member of the community, where the file synchronization object includes at least one group member in the community;
  • the file pushing unit 2710 pushes the file to be synchronized to the file synchronization object to update to a local storage space on the electronic device used by the file synchronization object.
  • it also includes:
  • the interface returning unit 2711 returns an online editing interface of any of the files to the at least one community member according to an online editing request initiated by at least one group member of the group to any of the files;
  • the instruction receiving unit 2712 receives an online editing instruction issued by the at least one group member for the any file
  • the online editing unit 2713 in response to the online editing instruction, performs a corresponding online editing process on any of the files.
  • the online editing unit 2713 is specifically configured to:
  • it also includes:
  • a sharing request receiving unit 2714 receiving a sharing request of the user for the shared content
  • the content sharing unit 2715 shares the shared content to the target user specified by the user.
  • the content sharing unit 2715 is specifically configured to:
  • the target user belongs to the community; or the target user is not related to the community.
  • it also includes:
  • the permission setting unit 2716 receives an operation authority for the shared content set by the user for the target user;
  • the operation restriction unit 2717 limits an operation performed by the target user on the shared content according to the operation authority.
  • it also includes:
  • a time period setting unit 2718 receiving an operation time period set by the user for the target user for the shared content
  • the authority giving unit 2719 assigns the target user temporary operation authority to the shared content, and the temporary operation authority is valid only during the operation period.
  • the access device of the shared space may include:
  • the request sending unit 2801 in response to the detected user operation, sending an access request for the community-related shared space to the server, so that the server determines the location according to the user's authority information in the organization structure of the community. Sharing the shared content in the shared space that matches the permission information;
  • the content display unit 2802 displays, according to the data returned by the server, the shared content in the shared space that matches the permission information.
  • it also includes:
  • a file pushing unit 2803 when the user belongs to a management member of the community, determining a file to be synchronized and a file synchronization object selected by the user, where the file synchronization object includes at least one group member in the group;
  • the server initiates a file push request, and the file push request instructs the server to push the file to be synchronized to the file synchronization object to update the file to be synchronized to an electronic device used by the file synchronization object.
  • Local storage space
  • the file update unit 2804 when the user does not belong to the management member of the community, receives the file pushed by the server according to the file push request initiated by the management member of the community, and stores the file to the local storage space.
  • it also includes:
  • the file lookup unit 2805 searches for an old version file corresponding to the received file in the local storage space to update the old version file to the received file by the file update unit.
  • it also includes:
  • An editing request unit 2806 initiating an online editing request for any file to the server
  • the interface receiving unit 2807 receives and displays an online editing interface of the any file returned by the server.
  • the instruction sending unit 2808 sends an online editing instruction for the any file to the server according to the detected user editing operation, so that the server performs corresponding online editing processing on any of the files.
  • the corresponding edit content of the online editing instruction in the any file matches the authority information of the user in the organization structure of the community.
  • it also includes:
  • the content sharing unit 2809 in response to the detected user operation, send a sharing request for the shared content to the server, so that the server shares the shared content to the target user specified by the user.
  • FIG. 29 is a schematic structural diagram of another apparatus provided by an exemplary embodiment.
  • the device includes a processor 2902, an internal bus 2904, a network interface 2906, a memory 2908, and a non-volatile memory 2910, and of course may also include hardware required for other services.
  • the processor 2902 reads the corresponding computer program from the non-volatile memory 2910 into the memory 2908 and then operates to form a rights management device for the shared space on the logical level.
  • one or more embodiments of the present specification do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each.
  • a logical unit which can also be a hardware or logic device.
  • the rights management apparatus of the shared space may include:
  • the authority obtaining unit 3001 acquires the authority information of the user in the community;
  • the authority management unit 3002 manages the access authority of the user to the shared content in the shared space related to the group according to the authority information.
  • it also includes:
  • the data obtaining unit 3003 acquires update data of the authority information
  • the authority updating unit 3004 updates the access authority of the user according to the update data.
  • FIG. 31 is a schematic structural diagram of still another apparatus provided by an exemplary embodiment.
  • the device includes a processor 3102, an internal bus 3104, a network interface 3106, a memory 3108, and a non-volatile memory 3110.
  • the processor 3102 reads the corresponding computer program from the non-volatile memory 3110 into the memory 3108 and then operates to form a sharing device that shares the content on a logical level.
  • one or more embodiments of the present specification do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each.
  • a logical unit which can also be a hardware or logic device.
  • the sharing device of the shared content may include:
  • the request receiving unit 3201 receives a sharing request initiated by the user, and the sharing request is related to the shared content in the shared space of the group;
  • the instruction sending unit 3202 sends a sharing instruction for the shared content to the server, where the sharing instruction is used to instruct the server to share the shared content to the target user specified by the user.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control.
  • a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • flash memory or other memory technology
  • compact disk read only memory CD-ROM
  • DVD digital versatile disk
  • Magnetic cassette tape disk storage
  • quantum memory graphene-based storage media or other magnetic storage devices or any other non-transporting media
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may be used to describe various information in one or more embodiments of the specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • the first information may also be referred to as the second information without departing from the scope of one or more embodiments of the present disclosure.
  • the second information may also be referred to as the first information.
  • the word "if” as used herein may be interpreted as "when” or "when” or "in response to a determination.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Storage Device Security (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Un ou plusieurs modes de réalisation de la présente invention concernent un procédé d'accès à un espace partagé, ainsi qu'un procédé et un appareil de gestion d'autorisation, ledit procédé d'accès consistant : à recevoir une demande d'accès provenant d'un utilisateur à un espace partagé associé à un groupe ; et à déterminer, en fonction d'informations d'autorisation de l'utilisateur dans le cadre organisationnel du groupe, le contenu partagé correspondant aux informations d'autorisation dans l'espace partagé, de façon à fournir ce dernier à l'utilisateur.
PCT/CN2018/115003 2017-11-14 2018-11-12 Procédé d'accès à un espace partagé et procédé et appareil de gestion d'autorisation WO2019096086A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
CN201711124479.X 2017-11-14
CN201711124479 2017-11-14
CN201810182697.7 2018-03-06
CN201810182697.7A CN109787946B (zh) 2017-11-14 2018-03-06 共享空间的访问方法、权限管理方法及装置
CN201811073161.8A CN109787948B (zh) 2017-11-14 2018-09-14 共享空间的访问方法、权限管理方法及装置
CN201811073161.8 2018-09-14

Publications (1)

Publication Number Publication Date
WO2019096086A1 true WO2019096086A1 (fr) 2019-05-23

Family

ID=66495705

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/115003 WO2019096086A1 (fr) 2017-11-14 2018-11-12 Procédé d'accès à un espace partagé et procédé et appareil de gestion d'autorisation

Country Status (3)

Country Link
CN (2) CN109787946B (fr)
TW (2) TW201919366A (fr)
WO (1) WO2019096086A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111935214A (zh) * 2020-06-29 2020-11-13 中铁第一勘察设计院集团有限公司 基于野外移动设备的数据传输方法
CN112163398A (zh) * 2020-09-30 2021-01-01 金蝶软件（中国）有限公司 一种图表分享方法及其相关设备
CN113395203A (zh) * 2021-06-11 2021-09-14 网易（杭州）网络有限公司 信息处理方法、装置、服务器、用户终端和存储介质
US20220270523A1 (en) * 2021-01-05 2022-08-25 Contentful GmbH Templates for content spaces in a content management system
US11783293B1 (en) * 2022-05-11 2023-10-10 Contentful GmbH Templates for content spaces in a content management system
US11783294B1 (en) * 2022-05-11 2023-10-10 Contentful GmbH Templates for content spaces in a content management system

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109787946B (zh) * 2017-11-14 2022-02-25 阿里巴巴集团控股有限公司 共享空间的访问方法、权限管理方法及装置
CN110334068B (zh) * 2019-07-10 2021-01-12 浪潮卓数大数据产业发展有限公司 一种组织协作实现方法、装置及系统
JP7398248B2 (ja) * 2019-11-14 2023-12-14 シャープ株式会社 ネットワークシステム、サーバ、および情報処理方法
CN111163473B (zh) * 2020-01-02 2020-11-13 广州爱浦路网络技术有限公司 一种基于nrf权限等级的5g核心网数据防护方法
CN111327589B (zh) * 2020-01-19 2021-09-10 腾讯科技（深圳）有限公司 资源共享方法、装置、计算机可读存储介质和计算机设备
TWI769531B (zh) * 2020-09-23 2022-07-01 東海大學 文件機密等級管理系統及方法
CN112597514A (zh) * 2020-12-22 2021-04-02 北京时代民芯科技有限公司 一种易于私有化定制部署的文档协同系统及方法
TWI806125B (zh) * 2021-08-10 2023-06-21 李揚 一種資料共享管理系統及其方法
CN114493382B (zh) * 2022-04-14 2022-07-01 未来地图(深圳)智能科技有限公司 基于企业风险关联图谱的企业风险数据处理方法和系统
CN115242503B (zh) * 2022-07-21 2024-05-07 北京字跳网络技术有限公司 内容空间的分享方法、装置、电子设备及存储介质
CN118555087A (zh) * 2023-02-27 2024-08-27 华为技术有限公司 访问控制方法和装置
CN117333140B (zh) * 2023-11-24 2024-02-20 贵州航天云网科技有限公司 一种企业信息服务管理系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101425903A (zh) * 2008-07-16 2009-05-06 冯振周 一种基于身份的可信网络架构
US20150067354A1 (en) * 2013-08-27 2015-03-05 Power-All Networks Limited Storage management device and storage management method
CN104426938A (zh) * 2013-08-27 2015-03-18 宇宙互联有限公司 存储管理系统及方法
WO2016197680A1 (fr) * 2015-06-12 2016-12-15 深圳大学 Système de contrôle d'accès pour une plateforme de service de stockage en nuage et procédé de contrôle d'accès associé
CN106682523A (zh) * 2016-11-17 2017-05-17 安徽华博胜讯信息科技股份有限公司 一种基于DSpace的数字资源管理方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008033552A2 (fr) * 2006-09-12 2008-03-20 Iwatchnow Inc. Système et procédé de répartition et acheminement distribués de média
KR20130006883A (ko) * 2011-06-24 2013-01-18 주식회사 케이티 가상 그룹을 이용한 컨텐츠 공유 시스템 및 방법
CN102546664A (zh) * 2012-02-27 2012-07-04 中国科学院计算技术研究所 用于分布式文件系统的用户与权限管理方法及系统
CN103731501A (zh) * 2014-01-13 2014-04-16 北京发现角科技有限公司 基于移动终端的多人协同管理待办事项的方法和系统
CN103813204B (zh) * 2014-02-26 2017-01-11 深圳市佳创视讯技术股份有限公司 一种基于机顶盒的跨屏互播方法及系统
CN104219326A (zh) * 2014-09-23 2014-12-17 深圳市爱洁家环保科技有限公司 保洁服务信息管理系统中的资源共享装置和方法
CN105528553A (zh) * 2014-09-30 2016-04-27 中国移动通信集团公司 一种数据安全共享的方法、装置和终端
CN105099876A (zh) * 2015-06-26 2015-11-25 阿里巴巴集团控股有限公司 团体用户的资料管理及即时通讯群组的维护方法、装置
CN109787946B (zh) * 2017-11-14 2022-02-25 阿里巴巴集团控股有限公司 共享空间的访问方法、权限管理方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101425903A (zh) * 2008-07-16 2009-05-06 冯振周 一种基于身份的可信网络架构
US20150067354A1 (en) * 2013-08-27 2015-03-05 Power-All Networks Limited Storage management device and storage management method
CN104424407A (zh) * 2013-08-27 2015-03-18 宇宙互联有限公司 存储管理系统及方法
CN104426938A (zh) * 2013-08-27 2015-03-18 宇宙互联有限公司 存储管理系统及方法
WO2016197680A1 (fr) * 2015-06-12 2016-12-15 深圳大学 Système de contrôle d'accès pour une plateforme de service de stockage en nuage et procédé de contrôle d'accès associé
CN106682523A (zh) * 2016-11-17 2017-05-17 安徽华博胜讯信息科技股份有限公司 一种基于DSpace的数字资源管理方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111935214A (zh) * 2020-06-29 2020-11-13 中铁第一勘察设计院集团有限公司 基于野外移动设备的数据传输方法
CN112163398A (zh) * 2020-09-30 2021-01-01 金蝶软件（中国）有限公司 一种图表分享方法及其相关设备
US20220270523A1 (en) * 2021-01-05 2022-08-25 Contentful GmbH Templates for content spaces in a content management system
US11782822B2 (en) * 2021-01-05 2023-10-10 Contentful GmbH Templates for content spaces in a content management system
CN113395203A (zh) * 2021-06-11 2021-09-14 网易（杭州）网络有限公司 信息处理方法、装置、服务器、用户终端和存储介质
US11783293B1 (en) * 2022-05-11 2023-10-10 Contentful GmbH Templates for content spaces in a content management system
US11783294B1 (en) * 2022-05-11 2023-10-10 Contentful GmbH Templates for content spaces in a content management system

Also Published As

Publication number Publication date
CN109787948B (zh) 2022-05-17
CN109787946B (zh) 2022-02-25
TW201931229A (zh) 2019-08-01
CN109787946A (zh) 2019-05-21
CN109787948A (zh) 2019-05-21
TW201919366A (zh) 2019-05-16

Similar Documents

Publication Publication Date Title
WO2019096086A1 (fr) Procédé d'accès à un espace partagé et procédé et appareil de gestion d'autorisation
US11025718B2 (en) Synchronization of permissioned content in cloud-based environments
US10567484B2 (en) Identifying content items for inclusion in a shared collection
WO2020135142A1 (fr) Procédé de création de groupe de projet, et procédé et dispositif de gestion de projet
US9866508B2 (en) Aggregating and presenting recent activities for synchronized online content management systems
US10579715B2 (en) Animating edits to documents
US20240031316A1 (en) Managing message attachments
US9992278B2 (en) Automatic account selection
US11182348B2 (en) Sharing collections with external teams
US11240188B2 (en) Large data management in communication applications through multiple mailboxes
US20220141227A1 (en) Managing Metadata for External Content within a Computing Environment
US11080243B2 (en) Synchronizing virtualized file systems
US11165726B2 (en) Contextual sharing for screen share
US9466056B2 (en) Content item delivery for payment
WO2023147425A1 (fr) Création de canevas automatique associée à un canal de communication à base de groupe
US20190102369A1 (en) Maintaining multiple versions of a collection of content items
WO2019019929A1 (fr) Procédé de génération de signature, et procédé et dispositif de partage de modèle de signature
WO2023020550A1 (fr) Procédé et appareil de traitement de service basés sur un document en ligne, et terminal et support de stockage
US10635641B1 (en) System and method to provide document management on a public document system
US9961132B2 (en) Placing a user account in escrow
US11494412B2 (en) Hub and spoke architecture for cloud-based synchronization

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18878151

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18878151

Country of ref document: EP

Kind code of ref document: A1