Service information sharing method and system and storage medium

Abstract

The embodiment of the invention provides a service information sharing method and system and a storage medium, and is used for improving the sharing efficiency of service information, and the method comprises the steps: setting identity information for an account in a sharing organization; setting a service information query permission for the account based on the identity information of the account; and when a service information query request of an account is received, generating a query result based on the service information query permission of the account.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, system and storage medium for sharing business information. Background Art

[0002] With the development of information technology, business information can be shared through online transmission so that business-related personnel in different locations can obtain the business information. In the prior art, multiple types of specific business information are usually shared one by one with different business-related personnel or groups so that business-related personnel can obtain specific business information and reduce the risk of business information leakage. However, the efficiency of sharing business information in the prior art is low. Therefore, how to improve the efficiency of sharing business information has become a technical problem that needs to be solved at present. Summary of the invention

[0003] In view of the above problems, the purpose of the present invention is to provide a method, system and storage medium for sharing business information to improve the efficiency of sharing business information. The specific scheme is as follows:

[0004] In a first aspect, an embodiment of the present application provides a service information sharing method, the method comprising:

[0005] Set up identity information for accounts in a shared organization;

[0006] Setting business information query permissions for the account based on the account's identity information;

[0007] When a business information query request of an account is received, a query result is generated based on the business information query authority of the account.

[0008] Optionally, when receiving a business information query request of an account, generating a query result based on the business information query authority of the account includes:

[0009] Receiving a business information query request of a first account; the information query request is used to indicate the business information of a second account to be queried by the first account;

[0010] If the business information query authority of the first account includes the authority to query the business information of the second account, the business information of the second account is provided to the first account; the first account and the second account are accounts in the shared organization.

[0011] Optionally, the method further includes:

[0012] Based on the identity information of the first account, setting business management permissions for the first account;

[0013] When a service management request for the second account from the first account is received, management options are provided for the first account based on the service management authority of the first account.

[0014] Optionally, the method further includes:

[0015] After the management authority of the shared organization is transferred from the original administrator account to the new administrator account, a management authority change message is pushed to the new administrator account.

[0016] Optionally, the method further includes:

[0017] Generate an invitation link based on the invitation request of the invitation initiating account;

[0018] After the account to be added logs in to the account based on the invitation link, verify the validity of the invitation link and the invitation authority of the invitation-initiating account;

[0019] If the invitation link is valid and the invitation initiating account has invitation authority, the account to be added is added to the sharing organization.

[0020] Optionally, the method further includes:

[0021] An invitation request is sent to the account to be added; when the account to be added accepts the invitation, the account to be added is added to the sharing organization.

[0022] Optionally, setting identity information for an account in a shared organization includes:

[0023] Set the identity information text of the account;

[0024] Performing sensitive word detection on the identity information text;

[0025] When the identity information text passes the sensitive word detection, it is determined that the identity information text is the identity information of the account.

[0026] Optionally, the method further includes:

[0027] When the removal information for the account to be logged out or the logout request of the account to be logged out is received, the information of the account to be logged out is deleted from the organization member table of the sharing organization.

[0028] In a second aspect, an embodiment of the present application provides a system for sharing business information, the system comprising:

[0029] The account identity setting module is used to set identity information for accounts in a shared organization;

[0030] A permission setting module, used to set business information query permissions for an account based on the account's identity information;

[0031] The query module is used to generate a query result based on the business information query authority of the account when receiving a business information query request of the account.

[0032] In a third aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements any of the above-mentioned information sharing methods when executed by a processor.

[0033] Compared with the prior art, this application has the following beneficial effects:

[0034] By setting identity information for the account in the sharing organization, setting business information query permissions for the account based on the account's identity information, and generating query results based on the account's business information query permissions when receiving a business information query request from the account, the system can automatically set business information query permissions for the account based on the account's identity, and feedback business information corresponding to the query permissions to the account. This eliminates the need for business information sharing personnel to share multiple types of specific business information one by one with business personnel with different reading permissions when sharing business information, simplifying the business information sharing process and improving the efficiency of business information sharing. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0036] Figure 1 It is a flowchart of a method for sharing business information provided by an embodiment of the present invention;

[0037] Figure 2 is a schematic diagram of a process for setting identity information or remarks provided by an embodiment of the present invention;

[0038] Figure 3 is a schematic diagram of a front-end page provided by an embodiment of the present invention;

[0039] Figure 4 It is a schematic diagram of the process of transferring a shared organization administrator provided by an embodiment of the present invention;

[0040] Figure 5 It is a schematic diagram of a process of removing a member from a sharing organization provided by an embodiment of the present invention;

[0041] Figure 6 is a schematic diagram of a process of exiting a sharing organization provided by an embodiment of the present invention;

[0042] Figure 7 is a schematic diagram of a process of dissolving a sharing organization provided by an embodiment of the present invention;

[0043] Figure 8 is a schematic diagram of a process for obtaining an entry configuration provided by an embodiment of the present invention;

[0044] Fig. 9 It is a schematic diagram of a process for setting business information query permissions provided by an embodiment of the present invention;

[0045] Fig.10 It is a structural diagram of a system for sharing business information provided by an embodiment of the present invention;

[0046] Fig.11 This is a schematic diagram of a process for a to-be-joined account to join a shared organization provided by an embodiment of the present invention;

[0047] Fig.12 is a schematic diagram of the structure of another system for sharing business information provided by an embodiment of the present invention;

[0048] Fig.13 It is a structural diagram of another system for sharing business information provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0049] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0050] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0051] An analysis of the prior art shows that, because different business-related personnel have different reading permissions for the same business information, the prior art needs to share multiple types of specific business information one by one with business personnel with different reading permissions. There are too many sharing steps and the process is cumbersome, resulting in low efficiency in sharing business information. To solve the above problems, this application provides a method, system and storage medium for sharing business information, and the specific solution is as follows.

[0052] like Figure 1 As shown, an embodiment of the present application provides a business information sharing method, the method comprising:

[0053] S101: Setting identity information for an account in a shared organization.

[0054] The shared organization includes business-related personnel. Taking orders in a freight scenario as an example, the shared organization may include the accounts of order-related personnel such as the orderer, order administrator, finance, and driver.

[0055] The administrator sets identity information for the account in the shared organization through the administrator terminal. The identity information may be the position of the business-related personnel in the enterprise or the identity, role, etc. of the business. It should be noted that the embodiment of the present application may also set notes for the account in the administrator terminal.

[0056] In an optional embodiment, setting identity information for an account in a shared organization specifically includes:

[0057] Set the account's identity information text;

[0058] Detect sensitive words in identity information text;

[0059] When the identity information text passes the sensitive word detection, it is determined that the identity information text is the identity information of the account.

[0060] Specifically, Figure 2 As shown, when setting identity information for an account in a shared organization, the administrator initiates the process of setting identity information to the user space (User-space API, uapi) through the administrator terminal, and the user space sets the identity information text based on user behavior. The risk control system performs a sensitive word check on the identity information text, and when sensitive words exist in the identity information text, it provides sensitive word reminders to the user. When there are no sensitive words in the identity information text, the sensitive word check passes, and the identity information of the account is updated. It should be noted that the members in the embodiments of the present application correspond one-to-one to the accounts.

[0061] Further, such as Figure 3As shown, the manager or creator of a shared organization can enter the organization creation page through the front-end page of the mobile terminal. The organization creation page contains a brief description of the order sharing capabilities and an entry for creating and inviting members. The identity, business information query permissions, and business management permissions of each member can also be edited and adjusted through the organization member management interface. This page can also be used to remove members, invite members, change administrators, disband the organization, and other adjustment operations.

[0062] Specifically, when the administrator performs the operation of changing the administrator through the front-end page of the mobile terminal, the method further includes:

[0063] After transferring the management rights of a shared organization from the original administrator account to the new administrator account, push the management rights change message to the new administrator account. The new administrator account is an account other than the original administrator account in the shared organization. Figure 4 As shown, the administrator of the sharing organization initiates the administrator transfer process through the administrator terminal, the user space executes the administrator transfer, and the administrator is changed on the user behavior side, so that the management authority of the sharing organization is transferred from the original administrator account to the new administrator account. The change record message is stored in the database, and the administrator transfer prompt is pushed to the new administrator through the message service.

[0064] Specifically, when the administrator performs the operation of removing a member through the front-end page of the mobile terminal, or receives a logout request from an account to be logged out in the sharing organization, the method further includes:

[0065] When receiving the removal information of the account to be withdrawn or the withdrawal request of the account to be withdrawn, the information of the account to be withdrawn is deleted from the organization member table of the sharing organization. The account to be withdrawn is the account of the member who needs to withdraw or be removed from the sharing organization.

[0066] like Figure 5 As shown, when the administrator performs the operation of removing members through the front-end page of the mobile terminal, the administrator terminal initiates the process of removing members, the user space removes the account to be logged out corresponding to the member to be removed, the user behavior side removes the information of the account to be logged out from the shared organization member table, and pushes a removal prompt to the removed member, and records the changes in the organization members in the database.

[0067] like Figure 6 As shown, when a request to exit the organization is received from a member of a shared organization, the process of exiting the organization is executed through the user space, the user behavior side deletes the information of the exiting member in the shared organization member table, pushes the exit message to the administrator, and stores the change record message in the database.

[0068] Specifically, when the manager performs the operation of disbanding the organization through the front-end page of the mobile terminal, the method further includes:

[0069] When receiving the operation information of disbanding the organization, the information of each account in the shared organization is removed from the organization member table.

[0070] like Figure 7 As shown, when the administrator performs the organization dissolution operation through the front-end page of the mobile terminal, the administrator terminal initiates the organization dissolution process, the user behavior space sends a notification of dissolution of the shared organization to the user behavior side, the user behavior side terminates the shared organization member table, and pushes the dissolution message of the shared organization to all members of the shared organization, and records the changes of the organization members in the database.

[0071] It should be noted that if Figure 8 As shown, before setting identity information for an account in a shared organization, the above system also needs to obtain the entry configuration, which specifically includes the process of the administrator terminal initiating an interface to obtain the entry through the Person_center_ad interface, the user space determining whether to filter the entry (low version, switch), and determining the hit situation of AB through AB testing, as well as determining whether the population is hit through user behavior, and finally the user space returns the judgment result to the administrator terminal.

[0072] S102: Setting business information query permissions for the account based on the identity information of the account.

[0073] Specifically, since different identity information requires different business information for the same business, business information query permissions can be set for accounts that have set identity information according to the identity information, so that business-related personnel can obtain the required business information and subsequent updated business information through their respective accounts.

[0074] Furthermore, the correspondence between identity information and business information query permissions can be pre-set or set based on actual needs. Taking orders in a freight scenario as an example, business information includes business-related information such as order information and address book information. The correspondence between identity information and business information query permissions can be that when the identity information is the shipper, the business information query permission is to allow querying the shipping order information, when the identity information is the consignee, the business information query permission is to allow querying the receipt information, and when the identity information is financial, the business information query permission is to allow querying transaction information. If the account does not have identity information, the minimum permission is set to the business information query permission of the account by default.

[0075] It should be noted that the address book can contain multiple addresses, and the address book has the function of searching addresses and member management options.

[0076] like Fig. 9As shown in the figure, when the administrator sets the business information query permission for the account based on the identity information of the account, the administrator terminal first initiates a business information query permission setting request to the user space. The user space sets the business information query permission for the account based on the administrator's operation. After the business information query permission of the account is changed, the message service pushes the business information query permission change message to the members corresponding to the account whose permission has been changed.

[0077] In a specific embodiment, the system may also automatically set business information query permissions for an account based on the account's identity information, including:

[0078] The first business information query permission is obtained from the historical data, and the first business information query permission is the business information query permission of the account with the same account identity information. The business information query permission of the account is set as the first business information query permission, so that the system can automatically set the business information query permission for the account based on the information in the historical data, further reducing the steps required for business information sharing and improving the efficiency of business information sharing.

[0079] S103: When receiving a business information query request of an account, generating a query result based on the business information query authority of the account.

[0080] The shared organization contains the business information that needs to be shared or the business information that the relevant business personnel need to query. The relevant business personnel send a business information query request to the shared organization through the account. After receiving the query request, the shared organization generates a query result based on the account's business information query authority and the content to be queried. In this way, accounts with different identity information can obtain business information that meets their own authority, realize hierarchical confidentiality in a low-coupling state of order information, and ensure enterprise information security.

[0081] The query results can be filtered by time, and the filtering time can be customized based on actual needs, such as displaying business information within a week, a month, or a year.

[0082] It should be noted that the content to be queried by the business information query request can be the business information of this account or other account business information. The business information of this account is the business information related to this account, and the business information of other accounts is the business information unrelated to this account. For example, when the identity information of the account is a business supervisor, the business information of the employees managed by the business supervisor can be queried by sending a business information query request.

[0083] The query results may also include the business interface. For example, if the business is an order, the order interface is divided into a delivery note and a receipt. The delivery note represents the complete set of orders sent by the organization to the outside, and the receipt represents the complete set of orders received by the organization members. If an order is sent between organization members, the decision is made based on whether the current viewer is the consignee or the consignor of the order. If the current viewer is the consignor, the order is a delivery note; if the current viewer is the consignee, the order is a receipt.

[0084] In an optional embodiment, when a business information query request of an account is received, a query result is generated based on the business information query authority of the account, including:

[0085] Receiving a business information query request of a first account; the information query request is used to indicate the business information of a second account that the first account wants to query;

[0086] If the business information query authority of the first account includes the authority to query the business information of the second account, the business information of the second account is provided to the first account; the first account and the second account are accounts in a shared organization.

[0087] When the first account has the authority to query the business information of the second account, the query result returned to the first account includes the business information of the second account. When the first account does not have the authority to query the business information of the second account, the query result returned to the first account is a prompt that it does not have the query authority, so that the system can return the query result that meets the business information query authority based on the identity information of the account.

[0088] For example, when the identity information of the first account is a business manager, if the second account that the first account wants to query is an employee, the first account has the authority to query the business information of the second account, and the query result returned to the first account includes the business information of the second account.

[0089] It should be noted that the first account and the second account can be the same account. For example, when the identity information of the first account is driver A, if the second account to be queried by the first account is the business information in driver A's own account, the first account has the authority to query the business information of the second account, and the query result returned to the first account includes the business information of the second account.

[0090] In an optional embodiment, the method further includes: setting business management authority for the first account based on the identity information of the first account;

[0091] When a service management request for a second account is received from a first account, management options are provided for the first account based on the service management authority of the first account.

[0092] Business management permissions include permissions to manage the account's own business information and permissions to manage other accounts' business information.

[0093] The business management request is used to indicate the second account to be managed by the first account. When the first account has the business management authority to manage the business of the second account, the management option for managing the second account is provided to the first account. When the first account does not have the business management authority to manage the business of the second account, the management option for managing the second account provided to the first account is empty.

[0094] Management options allow you to modify business information or current business processes, such as contacting drivers, communicating information, checking order costs, and other operations.

[0095] It should be noted that, in the embodiment of the present application, when the first account has the business management authority to manage the business of the second account, different business management authorities may also be provided for business management authorities of different levels.

[0096] In an optional embodiment, the above method further includes:

[0097] Generate an invitation link based on the invitation request of the invitation initiating account;

[0098] After the account to be added logs in based on the invitation link, verify the validity of the invitation link and the invitation authority of the invitation-initiating account;

[0099] If the invitation link is valid and the account initiating the invitation has invitation permissions, the account to be added will be added to the shared organization.

[0100] like Fig.10 As shown, the client can send a query request to the user service component (bfe_ubase_user_svc) through the query interface (bfe_qapi_api), or send an invitation request to the user service component through the user interface (bfe_uapi_api), and the user service component can communicate with the message service component (bfe_msgservice_svc).

[0101] Specifically, when an invitation is initiated to an account to be joined through an instant messaging platform other than the client, an invitation link is first generated and sent to the instant messaging platform. The client detects whether the invitation link has been clicked and has entered the mini-program group-order page. If so, it is further determined whether the account to be joined has been logged in on the mini-program page. After detecting that a third-platform user clicks the invitation link on the client and logs in to the account to be joined, a query request is sent to the user service component through the query interface to query the validity of the invitation link and whether the invitation-initiating account has invitation authority. If the invitation link is invalid, or the invitation-initiating account does not have invitation authority, an error prompt will pop up. If the invitation link is valid and the invitation-initiating account has invitation authority, the account to be joined will be added to the shared organization.

[0102] It should be noted that the invitation link can also be a shared invitation link of a shared order or a shared address book. When the invitation link is an invitation link of a shared order, after the account to be added accepts the invitation, the client jumps to the shared order page. When the invitation link is an invitation link of a shared address book, after the account to be added accepts the invitation, the client jumps to the shared address book page.

[0103] In another optional embodiment, the method further includes: sending an invitation request to the account to be added; when the account to be added accepts the invitation, adding the account to be added to the sharing organization.

[0104] Specifically, when an invitation is initiated to an account to be added through a client, the client sends an invitation request to the user service component through a user interface, and the user service component forwards the invitation request to the message service component, which pushes the invitation request to the account to be added, and when the account to be added accepts the invitation, a message of successful request is fed back to the user service component. The user service component adds the account to be added to the shared organization.

[0105] It should be noted that the invitation request may also be a sharing invitation request for a sharing order or a sharing address book.

[0106] When the invitation request is an invitation request for a shared address book, if the account to be added does not have any unread invitation requests, the invitation request page is hidden when the account to be added enters the address book page through the client. If the account to be added has any unread invitation requests, the invitation request page is displayed when the account to be added enters the address book page through the client, and the invitation request page is hidden when the account to be added chooses to agree or ignore. And when the account to be added enters the address book page again, the invitation request page corresponding to the processed invitation request is hidden.

[0107] When the invitation request is an invitation request for a shared order, if the account to be added does not have any unread invitation requests, the invitation request page will be hidden when the account to be added enters the shared order page through the client. If the account to be added has any unread invitation requests, the invitation request page will be displayed when the account to be added enters the shared order page through the client, and the invitation request page will be hidden when the account to be added chooses to agree or ignore. When the account to be added enters the shared order page again, the invitation request page corresponding to the processed invitation request will be hidden. When the invitation request page is displayed, it will be displayed in the shared order page as a half-screen pop-up window.

[0108] Furthermore, since the account to be joined may be offline when an invitation request is sent to the account to be joined, a request for obtaining unread invitation requests can be sent to the user service component through the user interface when the account to be joined comes online on the client. When the request is successful, the user service component returns the unread invitation requests to the client through the user interface, so that after the account to be joined logs in, the client can display the unread invitation requests on the page.

[0109] like Fig.11 As shown, the above method also includes: when the administrator terminal receives the organization joining request initiated by the account to be joined, the administrator terminal executes the process of joining the organization through the user space, the user behavior side adds the information of the member to be joined in the shared organization member table, and notifies the message service to push the joining message to the administrator. After receiving the response result returned by the message service, the user behavior side changes the record message to the database.

[0110] To facilitate understanding of the solutions in the embodiments of the present application, the following examples are given:

[0111] like Fig.12 As shown, the client can also send a multi-person sharing function activation invitation to the user service component through the user interface (bfe_uapi_api), so that the user service component forwards the multi-person sharing function activation invitation to the message service component, and the message service component pushes the invitation message to the invited members. The client can also communicate with the instant messaging platform to activate the multi-person sharing function on the instant messaging platform.

[0112] Taking the business information as an address book as an example, members of the sharing organization can actively share the address book through the multi-person sharing function. Before executing the sharing function, the client first sends a request to obtain the user's identity information to the user service component through the user interface, and returns the user's identity information to the client when the request is successful.

[0113] When a member who has not set a role in a sharing organization turns on the multi-person sharing function, the client first obtains the data to be shared through the user interface. The data to be shared can be an address book or an order, and initiates sharing on the instant messaging platform after obtaining the data to be shared. When the administrator in the sharing organization triggers the multi-person sharing function, the client provides the administrator with a list of members who have not shared through the user interface. The administrator can select members who need to be invited to turn on the multi-person sharing function from the list of members who have not shared, and send a multi-person sharing function turn-on invitation to the user service component through the user interface. The user service component sends the multi-person sharing function turn-on invitation to the message service component, and the message service component pushes the multi-person sharing function turn-on invitation to the member selected by the administrator. When the pushed member chooses to turn on the multi-person sharing function, the message service component returns a message of successful request to the user service component, and the user service component returns the message of successful request to the client logged in by the administrator through the user interface.

[0114] It should be noted that when an administrator enters a page shared by multiple people, such as a shared address book page, a shared order page, etc., the page shared by multiple people also includes a member management function. The administrator can enter the member management page through the member management function. When a member or administrator in a sharing organization enters a page shared by multiple people, the page also includes a function to filter individual members.

[0115] Taking shared orders as an example, the perspective of a shared organization under an account that has not joined the shared organization includes: illustrations, value description text, function description text, and the function of inviting new members. From the perspective of the creator, i.e. the administrator, it includes functions such as return function, member management function, order screening function, order card function, and pop-up reminder. From the perspective of members in the shared organization, it includes the status description text of those who have joined the shared order. When a member exits the shared organization, the system will pop up a confirmation window, and when a member is removed from the shared order, the system will pop up a reminder window.

[0116] When the creator views the order list, the system will display the View Shared Order entry. After the creator clicks the View Shared Order entry, the shared order page in the joined state will be displayed. When an account that has not joined a sharing organization views the order list, the system will display the View Shared Order entry. After the account that has not joined a sharing organization triggers the View Shared Order entry, the shared order page in the unjoined state will be displayed. After the account that has not joined a sharing organization triggers the close of the View Shared Order entry, the system triggers a pop-up window to allow the account that has not joined the sharing organization to confirm whether to close the View Shared Order entry.

[0117] By setting identity information for the account in the sharing organization, setting business information query permissions for the account based on the account's identity information, and generating query results based on the account's business information query permissions when receiving a business information query request from the account, the system can automatically set business information query permissions for the account based on the account's identity, and feedback business information corresponding to the query permissions to the account. This eliminates the need for business information sharing personnel to share multiple types of specific business information one by one with business personnel with different reading permissions when sharing business information, simplifying the business information sharing process and improving the efficiency of business information sharing.

[0118] like Fig.13 As shown, an embodiment of the present application provides a system for sharing business information, the system comprising:

[0119] The account identity setting module 1301 is used to set identity information for accounts in a shared organization.

[0120] The permission setting module 1302 is used to set business information query permissions for an account based on the identity information of the account.

[0121] The query module 1303 is used to generate a query result based on the business information query authority of the account when receiving a business information query request of the account.

[0122] In an optional embodiment, the query module 1303 is specifically used to:

[0123] Receiving a business information query request of a first account; the information query request is used to indicate the business information of a second account that the first account wants to query;

[0124] If the business information query authority of the first account includes the authority to query the business information of the second account, the business information of the second account is provided to the first account; the first account and the second account are accounts in a shared organization.

[0125] In an optional embodiment, the permission setting module 1302 is further used to:

[0126] Based on the identity information of the first account, set business management permissions for the first account;

[0127] When a service management request for a second account is received from a first account, management options are provided for the first account based on the service management authority of the first account.

[0128] In an optional embodiment, the system further includes a permission transfer module, and the permission transfer module is used to:

[0129] After transferring the management rights of the shared organization from the original administrator account to the new administrator account, push the management rights change message to the new administrator account.

[0130] In an optional embodiment, the system further includes an invitation module, and the invitation module is used to:

[0131] Generate an invitation link based on the invitation request of the invitation initiating account;

[0132] After the account to be added logs in based on the invitation link, verify the validity of the invitation link and the invitation authority of the invitation-initiating account;

[0133] If the invitation link is valid and the account initiating the invitation has invitation permissions, the account to be added will be added to the shared organization.

[0134] In an optional embodiment, the system further includes an invitation module, and the invitation module is used to:

[0135] An invitation request is sent to the account to be added; when the account to be added accepts the invitation, the account to be added is added to the sharing organization.

[0136] In an optional embodiment, the account identity setting module 1301 is specifically used for:

[0137] Set the account's identity information text;

[0138] Detect sensitive words in identity information text;

[0139] When the identity information text passes the sensitive word detection, it is determined that the identity information text is the identity information of the account.

[0140] In an optional embodiment, the system further includes an exit module, and the exit module is used to:

[0141] When the removal information for the account to be logged out or the logout request of the account to be logged out is received, the information of the account to be logged out is deleted from the organization member table of the sharing organization.

[0142] By setting the account identity setting module to set identity information for the account in the sharing organization, the permission setting module sets the business information query permission for the account based on the account identity information, and the query module generates a query result based on the business information query permission of the account when receiving the business information query request of the account, so that the system can automatically set the business information query permission for the account based on the identity of the account, and feedback the business information corresponding to the query permission to the account. As a result, when sharing business information, the business information sharing personnel do not need to share multiple types of specific business information one by one with business personnel with different reading permissions, which simplifies the business information sharing process and improves the efficiency of business information sharing.

[0143] The present application provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, any one of the above-mentioned information sharing methods is implemented.

[0144] It should be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of further restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0145] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0146] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A business information sharing method, characterized in that: The method comprises: Set up identity information for accounts in a shared organization; Setting business information query permissions for the account based on the account's identity information; When a business information query request of an account is received, a query result is generated based on the business information query authority of the account.

2. The method according to claim 1, characterized in that When receiving a business information query request of an account, generating a query result based on the business information query authority of the account includes: Receiving a business information query request of a first account; the information query request is used to indicate the business information of a second account to be queried by the first account; If the business information query authority of the first account includes the authority to query the business information of the second account, the business information of the second account is provided to the first account; the first account and the second account are accounts in the shared organization.

3. The method according to claim 2, characterized in that The method further comprises: Based on the identity information of the first account, setting business management permissions for the first account; When a service management request for the second account from the first account is received, management options are provided for the first account based on the service management authority of the first account.

4. The method according to claim 1, characterized in that: The method further comprises: After the management authority of the shared organization is transferred from the original administrator account to the new administrator account, a management authority change message is pushed to the new administrator account.

5. The method according to claim 1, characterized in that The method further comprises: Generate an invitation link based on the invitation request of the invitation initiating account; After the account to be added logs in to the account based on the invitation link, verify the validity of the invitation link and the invitation authority of the invitation-initiating account; If the invitation link is valid and the invitation initiating account has invitation authority, the account to be added is added to the sharing organization.

6. The method according to claim 1, characterized in that The method further comprises: An invitation request is sent to the account to be added; when the account to be added accepts the invitation, the account to be added is added to the sharing organization.

7. The method according to claim 1, characterized in that Setting identity information for an account in a shared organization includes: Set the identity information text of the account; Performing sensitive word detection on the identity information text; When the identity information text passes the sensitive word detection, it is determined that the identity information text is the identity information of the account.

8. The method according to claim 1, characterized in that: The method further comprises: When the removal information for the account to be logged out or the logout request of the account to be logged out is received, the information of the account to be logged out is deleted from the organization member table of the sharing organization.

9. A system for sharing business information, characterized in that: The system comprises: The account identity setting module is used to set identity information for accounts in a shared organization; A permission setting module, used to set business information query permissions for an account based on the account's identity information; The query module is used to generate a query result based on the business information query authority of the account when receiving a business information query request of the account.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, wherein when the computer program is executed by a processor, an information sharing method as claimed in any one of claims 1 to 8 is implemented.

Images