CN119484032A

CN119484032A - A method, system and storage medium for sharing business information

Info

Publication number: CN119484032A
Application number: CN202411484932.8A
Authority: CN
Inventors: 张淼
Original assignee: Shenzhen Yishi Huolala Technology Co Ltd
Current assignee: Shenzhen Yishi Huolala Technology Co Ltd
Priority date: 2024-10-23
Filing date: 2024-10-23
Publication date: 2025-02-18

Abstract

The embodiment of the application provides a method, a system and a storage medium for sharing service information, which are used for improving the sharing efficiency of the service information, wherein the method comprises the steps of setting identity information for account numbers in a sharing organization; setting service information inquiry authority for the account based on the identity information of the account, and generating an inquiry result based on the service information inquiry authority of the account when receiving the service information inquiry request of the account.

Description

Method, system and storage medium for sharing service information

Technical Field

The application relates to the technical field of computers, in particular to a method, a system and a storage medium for sharing business information.

Background

With the development of information technology, service information sharing can be performed in an online transmission mode, so that service related personnel located at different positions can acquire acquired service information. In the prior art, multiple types of specific service information are commonly shared to different service related personnel or groups one by one, so that the service related personnel can obtain the specific service information, and the risk of leakage of the service information is reduced. However, in the prior art, the service information sharing efficiency is low, so how to improve the service information sharing efficiency is a technical problem to be solved currently.

Disclosure of Invention

In view of the above problems, the present invention aims to provide a method, a system and a storage medium for sharing service information, so as to improve the sharing efficiency of the service information, and specifically, the following schemes are provided:

In a first aspect, the present application provides a service information sharing method, where the method includes:

Setting identity information for account numbers in a sharing organization;

Setting service information inquiry authority for an account based on the identity information of the account;

And when receiving a service information inquiry request of an account, generating an inquiry result based on the service information inquiry authority of the account.

Optionally, when receiving a service information query request of an account, generating a query result based on a service information query authority of the account includes:

receiving a service information inquiry request of a first account, wherein the information inquiry request is used for indicating service information of a second account to be inquired by the first account;

And if the service information query authority of the first account comprises the authority for querying the service information of the second account, providing the service information of the second account for the first account, wherein the first account and the second account are accounts in the sharing organization.

Optionally, the method further comprises:

Setting service management authority for the first account based on the identity information of the first account;

And when receiving a service management request of the first account for the second account, providing management options for the first account based on the service management authority of the first account.

Optionally, the method further comprises:

after the management authority of the sharing organization is transferred from the original manager account to the new manager account, a management authority change message is pushed to the new manager account.

Optionally, the method further comprises:

Generating an invitation link based on an invitation request of the invitation initiating account;

after an account to be added logs in based on an invitation link, verifying the validity of the invitation link and the invitation authority of an invitation initiating account;

And if the invitation link is valid and the invitation initiating account has the invitation authority, adding the account to be added to the sharing organization.

Optionally, the method further comprises:

and when the account to be added accepts the invitation, adding the account to be added to the sharing organization.

Optionally, the setting identity information for the account number in the sharing organization includes:

setting an identity information text of the account;

detecting sensitive words of the identity information text;

And when the identity information text passes the detection of the sensitive word, determining that the identity information text is the identity information of the account.

Optionally, the method further comprises:

and deleting the information of the account to be logged out from the organization member table of the shared organization when the removal information of the account to be logged out or the log-out request of the account to be logged out is received.

In a second aspect, an embodiment of the present application provides a system for sharing service information, where the system includes:

the account identity setting module is used for setting identity information for accounts in the sharing organization;

The permission setting module is used for setting service information inquiry permission for the account based on the identity information of the account;

And the query module is used for generating a query result based on the service information query authority of the account when receiving the service information query request of the account.

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 when executed by a processor implements a method of any one of the above information sharing.

Compared with the prior art, the application has the following beneficial effects:

By setting identity information for the account in the sharing organization, setting service information query permission for the account based on the identity information of the account, and generating a query result based on the service information query permission of the account when receiving a service information query request of the account, the system can automatically set the service information query permission for the account based on the identity of the account and feed back the service information corresponding to the query permission to the account. Therefore, service information sharing personnel do not need to share multiple types of specific service information one by one to service personnel with different reading authorities when the service information is shared, the service information sharing process is simplified, and the service information sharing efficiency is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flow chart of a method for sharing service information according to an embodiment of the present invention;

FIG. 2 is a schematic flow chart of setting identity information or remarks according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a front page provided by an embodiment of the present invention;

FIG. 4 is a schematic flow chart of a shared organization administrator transfer provided by an embodiment of the present invention;

FIG. 5 is a flowchart illustrating a method for removing members from a shared organization according to an embodiment of the present invention;

FIG. 6 is a schematic flow chart of exiting a shared organization provided by an embodiment of the present invention;

FIG. 7 is a schematic flow chart of shared organization dismissal provided by an embodiment of the present invention;

FIG. 8 is a schematic flow chart of obtaining an entry configuration according to an embodiment of the present invention;

fig. 9 is a schematic flow chart of setting service information inquiry authority provided by an embodiment of the present invention;

fig. 10 is a schematic structural diagram of a system for sharing service information according to an embodiment of the present invention;

Fig. 11 is a schematic flow chart of adding an account to be added to a sharing organization according to an embodiment of the present invention;

Fig. 12 is a schematic structural diagram of another system for sharing service information according to an embodiment of the present invention;

fig. 13 is a schematic structural diagram of a system for sharing service information according to another embodiment of the present invention.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, product, or apparatus.

According to analysis of the prior art, as different service related personnel have different reading rights for the same piece of service information, the prior art needs to share multiple types of specific service information to the service personnel with different reading rights one by one, the sharing steps are too many, the process is complicated, and the service information sharing efficiency is low. In order to solve the above problems, the present application provides a method, a system and a storage medium for sharing service information, and the specific scheme is as follows.

As shown in fig. 1, an embodiment of the present application provides a service information sharing method, where the method includes:

s101, setting identity information for account numbers in a sharing organization.

The sharing organization includes business related personnel, for example, orders in a shipping scenario, and may include accounts for individuals, order administrators, finances, drivers, etc. related to the orders.

The manager sets identity information for the account number in the sharing organization through the manager terminal, wherein the identity information can be the information of the business related personnel such as the position in the enterprise or the identity, the role and the like in the business. It should be noted that, in the embodiment of the present application, remarks may also be set for the account in the administrator terminal.

In an optional embodiment, setting identity information for an account in the shared organization specifically includes:

Setting an identity information text of an account;

detecting sensitive words of the identity information text;

Specifically, as shown in fig. 2, when setting identity information for an account in a sharing organization, an administrator initiates a process of setting identity information to a User space (User-space API, uapi) through an administrator terminal, and the User space sets identity information text based on User behavior. The wind control system performs sensitive word checking on the identity information text, and feeds back sensitive word reminding to the user when the sensitive word exists in the identity information text. When no sensitive word exists in the identity information text, the sensitive word passes the check, and the identity information of the account is updated. It should be noted that, in the embodiment of the present application, members are in one-to-one correspondence with account numbers.

Further, as shown in fig. 3, an administrator or creator of the sharing organization may enter an organization creation page through a front-end page of the mobile terminal, where the organization creation page includes a capability profile for order sharing and an invitation member portal. The identity of each member, the service information inquiry authority and the service management authority can be edited and adjusted through the organization member management interface. Adjustment operations such as removing members, inviting members, replacing administrators, organizing and dismantling can also be performed through the page.

Specifically, when the manager performs the operation of replacing the manager through the front-end page of the mobile terminal, the method further comprises the following steps:

After the management authority of the sharing organization is transferred from the original manager account to the new manager account, a management authority change message is pushed to the new manager account. The new administrator account is an account in the shared organization other than the original administrator account. As shown in fig. 4, an administrator of the sharing organization initiates an administrator transfer flow through an administrator terminal, and the user space performs administrator transfer and changes the administrator 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. And storing the change record information into a database, and pushing a prompt transferred by the administrator to the new administrator through a message service.

Specifically, when the manager performs the member removing operation through the front-end page of the mobile terminal or receives the exit request of the account to be exited in the sharing organization, the method further includes:

And deleting the information of the account to be logged out from the organization member table of the sharing organization when the removal information of the account to be logged out or the log-out request of the account to be logged out is received. The account to be logged out is an account of a member needing to be logged out or removed in the shared organization.

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

As shown in fig. 6, when a member in the shared organization initiates a request for exiting the organization, the user space is used to execute the process of exiting the organization, the user behavior side deletes the information of exiting the member in the shared organization member table, pushes the exiting message to the administrator, and stores the change record message in the database.

Specifically, when the manager executes the operation of organizing and disassembling through the front-end page of the mobile terminal, the method further comprises the following steps:

and when operation information of the disassembly organization is received, removing the information of each account number in the shared organization from the organization member table.

As shown in fig. 7, when an administrator performs an operation of organizing and disassembling through a front-end page of a mobile terminal, the administrator terminal initiates an organizing and disassembling process, a user behavior space sends a notification of performing shared organization and disassembling to a user behavior side, the user behavior side terminates a shared organization member table, and pushes a disassembling message of the shared organization to all members in the shared organization, so that a change record value database of the organization members is obtained.

It should be noted that, before setting identity information for account numbers in the shared organization, as shown in fig. 8, the system further needs to obtain an entry configuration, specifically includes a process that the administrator terminal initiates an interface to obtain an entry through a person_center_ad interface, the user space judges whether to filter the entry (low version, switch), judges the hit condition of the AB through the AB test, judges whether the crowd hits through the user behavior, and finally the user space returns the judgment result to the administrator terminal.

S102, setting service information inquiry authority for the account based on the identity information of the account.

Specifically, because the service information required to be acquired by different identity information for the same service is different, the service information inquiry authority can be set according to the identity information as the account number with the identity information, so that service related personnel can acquire the required service information and the service information after subsequent updating through the respective account numbers.

Further, the corresponding relation between the identity information and the service information inquiry authority can be preset or set based on actual requirements. Taking an order in a shipping scenario as an example, the service information includes information related to the service, such as order information and address book information. The correspondence between the identity information and the service information query authority may be that, when the identity information is a sender, the service information query authority is permission to query invoice information, when the identity information is a receiver, the service information query authority is permission to query receipt information, and when the identity information is a finance, the service information query authority is permission to query transaction information. If the account does not have the identity information, the lowest authority is set as the service information inquiry authority of the account by default.

It should be noted that the address book may contain a plurality of addresses, and the address book has a function of searching for an address, and a member management option.

As shown in fig. 9, when the manager sets a service information inquiry right for an account based on the identity information of the account, the manager terminal first initiates a service information inquiry right setting request to the user space. The user space sets the service information inquiry authority of the account based on the operation of the manager, and the message service pushes the service information inquiry authority changing message to the member corresponding to the account with the authority changed after the service information inquiry authority of the account is changed.

In a specific embodiment, the system may further automatically set a service information query authority for the account based on identity information of the account, including:

And acquiring a first service information inquiry authority from the historical data, wherein the first service information inquiry authority is the service information inquiry authority of the account with the same account identity information. The service information inquiry authority of the account is set as the first service information inquiry authority, so that the system can automatically set the service information inquiry authority for the account based on the information in the historical data, the steps required to be executed for service information sharing are further reduced, and the service information sharing efficiency is improved.

S103, when receiving a service information inquiry request of the account, generating an inquiry result based on the service information inquiry authority of the account.

The sharing organization contains the business information to be shared or the business information to be queried by related business personnel. And the related service personnel send a service information inquiry request to the sharing organization through the account, and the sharing organization generates an inquiry result based on the service information inquiry authority of the account and the content to be inquired after receiving the inquiry request. Therefore, the accounts with different identity information can acquire the business information conforming to the authority of the accounts, the hierarchical confidentiality of the order information in a low coupling state is realized, and the information security of enterprises is ensured.

The query results can be filtered according to time, and the filtering time can be set in a self-defined mode based on actual requirements, for example, service information in one week, one month or one year is displayed.

It should be noted that, the content to be queried in the service information query request may be the account service information or other account service information. The service information of the account is the service information related to the account, and the service information of other accounts is the service information not related to the account. For example, when the identity information of the account is a business director, the business information of the employee managed by the business director may be queried by sending a business information query request.

The query results may also include a business interface, for example, a business, the order interface being divided into an invoice representing the aggregate of the orders sent to the outside by the organization and an invoice representing the aggregate of the orders received by the organization members. If an order is encountered that is sent to each other among the organization members, then the current viewer is taken to make a decision as to whether the order is a consignee or a shipper. The current checking person is the sender, the order is the invoice, the current checking person is the receiver, and the order is the receipt.

In an alternative embodiment, when receiving a service information query request of an account, generating a query result based on a service information query authority of the account includes:

The method comprises the steps of receiving a service information inquiry request of a first account, wherein the information inquiry request is used for indicating service information of a second account to be inquired by the first account;

if the service information query authority of the first account includes the authority for querying the service information of the second account, the service information of the second account is provided for the first account, and the first account and the second account are accounts in a sharing organization.

When the first account has the right of inquiring the service information of the second account, the inquiring result returned to the first account comprises the service information of the second account. When the first account does not have the right of inquiring the service information of the second account, the inquiring result returned to the first account is a prompt without the inquiring right, so that the system can return the inquiring result conforming to the inquiring right of the service information based on the identity information of the account.

For example, when the identity information of the first account is a business director, if the second account to be queried by the first account is an employee, the first account has 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.

It should be noted that the first account number and the second account number may be the same account number. For example, when the identity information of the first account is the driver a, if the second account to be queried by the first account is the service information in the account of the driver a, the first account has authority to query the service information of the second account, and the query result returned to the first account includes the service information of the second account.

In an optional embodiment, the method further comprises setting service management authority for the first account based on the identity information of the first account;

The service management authority comprises the management authority of the service information of the account number and the management authority of the service information of other account numbers.

The service management request is used for indicating a second account to be managed by the first account, and when the first account has the service management right for managing the service of the second account, the management option for managing the second account is provided for the first account. When the first account does not have the service management right for carrying out service management on the second account, the management option for providing management on the second account for the first account is empty.

The management options can be to modify the business information or the current flow of the business, such as contacting drivers, information communication, order cost viewing, etc.

It should be noted that, in the embodiment of the present application, when the first account has the service management authority for performing service management on the second account, different service management authorities may also be provided for different levels of service management authorities.

In an alternative embodiment, the method further comprises:

after the account to be added logs in the account based on the invitation link, verifying 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 the invitation authority, adding the account to be added to the sharing organization.

As shown in fig. 10, the client may send a query request to the user service component (bfe _ ubase _user_svc) through the query interface (bfe _ qapi _api) or an invite request to the user service component through the user interface (bfe _ uapi _api), and the user service component may communicate with the message service component (bfe _ msgservice _svc).

Specifically, when an invitation is initiated to a joining account through an instant messaging platform outside the client, an invitation link is first generated, and the invitation link is sent to the instant messaging platform. The client detects whether the invitation link is clicked and has entered the applet group-order page. If yes, further judging whether the account to be added is logged in the applet page. After detecting that the third platform user clicks the invitation link on the client and logs in the account to be added, 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 the invitation authority. If the invitation link is invalid or the invitation initiating account does not have the invitation authority, popping up an error prompt. If the invitation link is valid and the invitation initiating account has the invitation authority, adding the account to be added to the sharing organization.

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

In another optional embodiment, the method further comprises sending an invitation request to the account to be added, and adding the account to be added to the sharing organization when the account to be added accepts the invitation.

Specifically, when an invitation is initiated to an account to be added through a client, the client sends an invitation request to a user service component through a user interface, the user service component forwards the invitation request to a message service component, the message service component 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 sharing organization.

It should be noted that the invitation request may also be a shared invitation request of a shared order or a shared address book.

When the invitation request is an invitation request of a shared address book, if the account to be added does not have an unread invitation request, hiding the invitation request page when the account to be added enters the address book page through the client. If the account to be added has an unread invitation request, displaying the invitation request page when the account to be added enters the address book page through the client, and hiding the invitation request page when the account to be added selects consent or neglect. And hiding the invitation request page corresponding to the processed invitation request when the account to be added reenters the address book page.

When the invitation request is an invitation request of a sharing order, if the account to be added does not have an unread invitation request, hiding the invitation request page when the account to be added enters the sharing order page through the client. If the account to be added has an unread invitation request, displaying the invitation request page when the account to be added enters the shared order page through the client, and hiding the invitation request page when the account to be added selects consent or neglect. And hiding the invitation request page corresponding to the processed invitation request when the account to be added reenters the shared order page. When the invitation request page is displayed, the invitation request page is displayed in the shared order page in the form of a half screen popup window.

Further, when the invitation request is sent to the account to be added, the account to be added is possibly in an offline state, so that when the account to be added is online on the client, a request for acquiring the unread invitation request can be sent to the user service component through the user interface, and when the request is successful, the user service component returns the unread invitation request to the client through the user interface, so that the unread invitation request is displayed in a page by the client after the account to be added logs in.

As shown in fig. 11, the method further includes that when the administrator terminal receives an organization joining request initiated by the account to be joined, the administrator terminal executes a process of joining the organization through the user space, and the user behavior side joins 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.

In order to facilitate understanding of the solution in the embodiments of the present application, the following is exemplified:

As shown in fig. 12, the client may also send a multi-person shared function open invitation to the user service component via the user interface (bfe _ uapi _api) to cause the user service component to forward the multi-person shared function open invitation to the message service component, which pushes the invite message to the invited member. The client can also communicate with the instant information platform to enable the multi-user sharing function even on the information platform.

Taking service information as an address book as an example, members in a sharing organization can actively share the address book through a multi-person sharing function. Before executing the sharing function, the client side firstly sends a request for acquiring the identity information of the user to the user service component through the user interface, and returns the identity information of the user to the client side when the request is successful.

When a member with no role in the sharing organization starts a multi-person sharing function, the client side firstly acquires data to be shared through a user interface, the data to be shared can be an address book or an order, and sharing is initiated on an instant information platform after the data to be shared is acquired. When an administrator in the sharing organization triggers the multi-person sharing function, the client provides the administrator with a list of members that are not being shared through the user interface. The administrator may select a member from the list of members that has never been shared that needs to invite to open the multi-person sharing function and send the multi-person sharing function open invitation to the user service component via the user interface. The user service component sends a multi-person sharing function open invitation to the message service component, which pushes the multi-person sharing function open invitation to the member selected by the administrator. When the pushed member selects to start 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.

It should be noted that, when the administrator enters a multi-person shared page, such as a shared address book page, a shared order page, and the like, the multi-person shared page further includes a member management function. An administrator can enter a member management page through a member management function. When members or administrators in the sharing organization enter a multi-person shared page, the page also includes a function of screening individual members.

Taking a sharing order as an example, the view of the sharing organization under the account number of the non-joining sharing organization includes an illustration, a value description, a function description and an invite new member function. The system comprises a return function, a member management function, an order screening function, an order card function, a popup window reminding function and the like under the view of a creator, namely an administrator. Under the view angle of the members in the sharing organization, including the state statement of the added sharing order, the system can perform popup confirmation when the members exit the sharing organization, and the system can perform popup reminding when the members are moved out of the sharing order.

When the creator views the order list, the system displays a view shared order entry, and after the creator clicks the view shared order entry, the system displays a shared order page in a joined state. When the account number of the non-joining sharing organization checks the order list, the system displays a checking sharing order entry, after the account number of the non-joining sharing organization triggers the checking sharing order entry, a sharing order page in a non-joining state is displayed, and after the account number of the non-joining sharing organization triggers the closing of the checking sharing order entry, the system triggers a popup window so that the account number of the non-joining sharing organization confirms whether to close the checking sharing order entry.

As shown in fig. 13, an embodiment of the present application provides a service information sharing system, which includes:

An account identity setting module 1301 is configured to set identity information for an account in a sharing organization.

The permission setting module 1302 is configured to set a service information query permission for the account based on identity information of the account.

The query module 1303 is configured to generate a query result based on a service information query authority of an account when receiving a service information query request of the account and when receiving a service information query request of the account based on a service information query of the account.

In an alternative embodiment, the query module 1303 is specifically configured to:

In an alternative embodiment, the rights setting module 1302 is further configured to:

In an alternative embodiment, the system further includes a rights transfer module for:

In an alternative embodiment, the system further includes an invitation module, where the invitation module is configured to:

and adding the account to be added to the sharing organization when the account to be added accepts the invitation.

In an alternative embodiment, the account identity setting module 1301 is specifically configured to:

Setting an identity information text of an account;

detecting sensitive words of the identity information text;

In an alternative embodiment, the system further comprises an exit module for:

And deleting the information of the account to be logged out from the organization member table of the sharing organization when the removal information of the account to be logged out or the log-out request of the account to be logged out is received.

The method comprises the steps that through setting an account identity setting module to set identity information for an account in a sharing organization, a permission setting module sets service information inquiry permission for the account based on the identity information of the account, and when a service information inquiry request of the account is received, an inquiry module generates an inquiry result based on the service information inquiry permission of the account, so that a system can automatically set the inquiry permission of the service information for the account based on the identity of the account, and service information corresponding to the inquiry permission is fed back to the account. Therefore, service information sharing personnel do not need to share multiple types of specific service information one by one to service personnel with different reading authorities when the service information is shared, the service information sharing process is simplified, and the service information sharing efficiency is improved.

The present application provides a computer readable storage medium having a computer program stored thereon, wherein the computer program when executed by a processor implements a method of any one of the above information sharing.

It should be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in 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 comprises:

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, wherein setting identity information for an account in a shared organization comprises:

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, the information sharing method according to any one of claims 1 to 8 is implemented.