Request response method, device and system, storage medium, and electronic device
By centrally saving data of the same customer account in the CRM system and responding to operation requests based on permission configuration, the problem of repeated data storage when multiple sales follow up customers at the same time is solved, improving the system maintenance efficiency and data security.
Patent Information
- Application Number
- CN202010976693.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-16
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-09-16
AI Technical Summary
When existing CRM systems follow up with the same customers at the same time, a large amount of junk data will be generated because each sales need to save the same customer data, which makes the system difficult to maintain.
Avoid repeatedly saving the same data by centrally saving the data of the same customer account in the database and responding to operation requests based on the permission configuration of the target account.
It effectively reduces the generation of garbage data, improves system maintenance efficiency and data security.
Smart Images

Figure CN112131192B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a request response method, device and system, storage medium, and electronic device. Background Art
[0002] CRM system, the full name of which is Customer relationship management system, is an information system that uses software, hardware and network technology to collect, manage, analyze and use customer information for enterprises. With customer data management as the core, it records various interactions between enterprises and customers during the marketing and sales process, as well as the status of various related activities, and provides various data models to support subsequent analysis and decision-making.
[0003] In the CRM system of related technologies, each salesperson can only see the customer data that he is responsible for, and can only add activity records, upload attachments, create sales opportunities, etc. for the customers that he is responsible for. For the problem that multiple salespeople follow up the same customer at the same time, the current solution in the CRM system is to create multiple customers with similar names, each of which has its own salesperson in charge. The data created by the salesperson for the customer can only be seen by the salesperson himself, and the salesperson who is not the person in charge of the customer cannot see any information about the customer. When the system runs for a long time, a lot of junk data will be generated, which will affect the maintenance of the system.
[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention
[0005] The embodiments of the present application provide a request response method, device and system, storage medium, and electronic device to at least solve the technical problem of excessive junk files in a CRM system in the related art.
[0006] According to one aspect of an embodiment of the present application, a method for responding to a request is provided, comprising: receiving an operation request of a target account, the operation request being used to request execution of data operations related to a customer account, wherein data belonging to the same customer account is centrally stored in a database; searching for operation permissions configured for the target account from the permission configuration of the customer account; and responding to the operation request according to the operation permissions of the target account.
[0007] According to another aspect of an embodiment of the present application, a request response device is also provided, including: a receiving unit, used to receive an operation request of a target account, the operation request is used to request to perform data operations related to a customer account, and data belonging to the same customer account is centrally stored in a database; a search unit, used to search for operation permissions configured for the target account from the permission configuration of the customer account; and a response unit, used to respond to the operation request according to the operation permissions of the target account.
[0008] According to another aspect of an embodiment of the present application, a request response system is also provided, including: a smart terminal logged in with a target account, used to send an operation request, the operation request is used to request to perform data operations related to the customer account; a server, used to, when receiving the operation request, search the operation authority configured for the target account from the authority configuration of the customer account, and respond to the operation request according to the operation authority of the target account; a database, in which data belonging to the same customer account is centrally stored.
[0009] According to another aspect of an embodiment of the present application, a storage medium is further provided, which includes a stored program, and the above method is executed when the program is run.
[0010] According to another aspect of an embodiment of the present application, an electronic device is further provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the above method through the computer program.
[0011] In an embodiment of the present application, when an operation request from a target account is received, the operation permissions configured for the target account are searched from the permission configuration of the customer account; the operation request is responded to according to the operation permissions of the target account. Since the data belonging to the same customer account is centrally stored in the database, rather than each salesperson storing the data of the same customer separately, the same data is avoided from being saved in multiple copies, which can solve the technical problem of too many junk files in the CRM system in the related technology, thereby achieving the technical effect of avoiding the generation of junk data. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0013] Figure 1 is a schematic diagram of a hardware environment of a request response method according to an embodiment of the present application;
[0014] Figure 2 is a flowchart of an optional request response method according to an embodiment of the present application;
[0015] Figure 3 is a flowchart of an optional request response method according to an embodiment of the present application;
[0016] Figure 4 is a schematic diagram of an optional permission configuration according to an embodiment of the present application;
[0017] Figure 5 is a schematic diagram of an optional permission configuration according to an embodiment of the present application;
[0018] Figure 6 is a schematic diagram of an optional request response device according to an embodiment of the present application;
[0019] as well as
[0020] Figure 7 It is a structural block diagram of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION
[0021] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings 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 should fall within the scope of protection of the present application.
[0022] It should be noted that the terms "first", "second", etc. 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 of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0023] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretation:
[0024] Sales opportunities: customers with purchasing tendencies, whose purchasing intentions have been confirmed, and sales opportunities that may be closed; Activities: records of follow-up processes by sales (represented by sales account in the text) after each follow-up with customers; Account: platform account associated with the customer (i.e., customer account); Contract: purchase contract signed by the customer; Attachments: attachments of relevant content uploaded by sales under the customer; Historical followers: sales who have historically followed up on this customer; Operation log: operation log recorded each time a customer account is edited; Customer team leader (represented by administrator account in the text): sales who is mainly responsible for following up under the customer, and can add team members and assign team members' permissions; View and edit personal data: sales has view and edit permissions for data created by him / her; View all data: sales has view permissions for all data under the customer, and can edit data created by him / her; Edit all data: sales has view and edit permissions for all data under the customer.
[0025] According to one aspect of the embodiments of the present application, an embodiment of a request response system is provided. In this embodiment, Figure 1 As shown, the system may be composed of a terminal 101 and a server 103 .
[0026] The server 103 is connected to the terminal 101 through a network, and information exchange between the two can be carried out through the network. Through the interaction, the server provides CRM services for the terminal or the client installed on the terminal (which can be a web client, application client, etc.). A database 105 can be set on the server or independently of the server to provide data storage services for the server 103, and data objects belonging to the same customer account are centrally stored in an independent database or in an area in the database for centralized storage. The above network includes but is not limited to: a wide area network, a metropolitan area network or a local area network, and the terminal 101 is not limited to a PC, a mobile phone, a tablet computer, etc.
[0027] like Figure 1 As shown, the terminal is a smart terminal with a target account of the user logged in (the target account represents sales, which can be a sales administrator or ordinary sales). When a data operation related to a customer account (the customer account represents a customer maintained by sales) needs to be requested, an operation request is sent to the server; the server can search for the operation permission configured for the target account from the permission configuration of the customer account, and respond to the operation request according to the operation permission of the target account.
[0028] In the customer data management CRM system, the customer data of multiple customers can be included. A corresponding customer group can be created for each customer, and the group members in each customer group can be divided into roles. For example, after the role division, two types of members can be obtained, one is the person in charge (i.e., administrator), and the other is the ordinary member (or group member, i.e., specific sales staff). The person in charge can manage the permissions of ordinary members, and the person in charge can also have a role such as the general person in charge. The specific number of roles divided and the operating permissions of each role in the system can be set according to needs. The operating permissions include but are not limited to the permissions to add group members, group leaders, view data, edit data, etc.
[0029] The above interactions between the terminal and the server have two main purposes. One is for the administrator to perform related operations. For example, in an organization that adopts sales teams, the head of the customer team can assign permissions to members, which can be specific to each data object. Member permissions can be strictly controlled to ensure the security of customer data, allowing different sales to follow up and maintain the same customer without affecting each other. The second is data access operations for ordinary sales, such as data reading, modification, deletion, and writing. When performing these operations, the server can authenticate ordinary sales based on operating permissions.
[0030] According to one aspect of the embodiment of the present application, a method embodiment of a request response method is provided. The request response method of the embodiment of the present application can be executed by the server 103, or can be executed by the server 103 and the terminal 101 together. Figure 2 is a flowchart of an optional request response method according to an embodiment of the present application, such as Figure 2 As shown, the method may include the following steps:
[0031] In step S202, the server receives an operation request sent by the user on the terminal in the name of the target account, requesting to perform a data operation related to the customer account. The data belonging to the same customer account is centrally stored in the database (such as storing the data in the database in the form of data objects), that is, the data belonging to the same customer account is centrally stored together instead of being stored separately. For example, a storage area identified by the customer account is established in the database, and all data of the customer is stored in this area.
[0032] The above-mentioned data objects refer to objects in customer data used to define a certain type of data. Specific data objects include but are not limited to contacts, sales opportunity information, activity information, account information, contracts, attachments, operation logs, etc., and may also refer to a more specific piece of information in the above-mentioned data objects.
[0033] Step S204: the operation authority of each target account is recorded in the authority configuration of the customer account, and the server can search the operation authority configured for the target account from the authority configuration of the customer account.
[0034] Step S206: respond to the operation request according to the operation authority of the target account.
[0035] Through the above steps, when receiving an operation request from a target account, the operation permission configured for the target account is searched from the permission configuration of the customer account; the operation request is responded to according to the operation permission of the target account. Since the data belonging to the same customer account is centrally stored in the database, rather than each salesperson storing the data of the same customer separately, the same data is avoided from being stored in multiple copies, which can solve the technical problem of too many junk files in the CRM system in the related technology, thereby achieving the technical effect of avoiding the generation of junk data.
[0036] The technical solution of this application mainly includes two parts, one is the authority management of members by the administrator in the customer group, and the other is the access management of members in the customer group. The following describes them respectively:
[0037] (1) The administrator manages the permissions of members in the customer group.
[0038] Step 11: The administrator account adds a sales account for a team member.
[0039] Each customer can be regarded as a customer group and followed up by multiple sales staff at the same time. Each customer has an account manager who has the authority to add group members, set group member permissions, remove group members, and withdraw customers from the high seas, mark them invalid, etc.
[0040] When adding a new team member, the server receives an add instruction sent by the administrator, which instructs to add the second account as a sales account that maintains the customer account; when the server responds to the add instruction, it adds the second account as a sales account that maintains the customer account, and configures default operation permissions or specified operation permissions for the second account.
[0041] For example, by default, members of a customer team can view all data under a customer, including activities, sales opportunities, follow-up records, operation logs, attachments, and other data objects under the customer, but team members can only edit the data they created. Configuring a default permission for sales people who join the team can reduce the increment of the database and relieve the pressure on the database server.
[0042] Step 12: If the default permissions do not meet the actual needs, the administrator configures the permissions of the group members individually.
[0043] Step 121: The server receives an operation request sent by the user on the terminal in the name of the target account.
[0044] Step 122, when the operation request indicates a request to perform a permission configuration operation (i.e., configuring the operation permission for the sales account to operate on the data object of the customer account, the sales account may be recorded as the first account), search the permission configuration of the customer account for the operation permission configured for the target account.
[0045] Step 123, authenticating the user, that is, determining whether the target account is an administrator account.
[0046] When the target account does not belong to the administrator account, the server returns a prompt message indicating that the request failed. By verifying the account, data security can be improved.
[0047] Step 124 , when the operation authority of the target account indicates that the target account is an administrator account, perform an authority configuration operation.
[0048] The above permission configuration operations include the following types:
[0049] 1) The permission of the first account is configured to view all data, allowing the first account to view all data objects of the customer account and edit the data objects created by the first account.
[0050] 2) The first account's permissions are configured to view and edit personal data, allowing the first account to view and edit data objects created by the first account, such as viewing and editing data objects such as activities and sales opportunities created by the first account.
[0051] 3) The first account's permission is configured to edit all data, allowing the first account to view and edit all data objects of the customer account.
[0052] 4) When configuring the operating permissions of each member of the team, it can be done on a data object by data object basis. The operating permissions of a specified data object can be configured for the first account, indicating that the first account is allowed to view the first data object or edit the first data object. The first data object is a data object specified by the administrator account among all data objects of the customer account.
[0053] By individually authorizing each data object under each customer, sales permissions can be clearly configured. This not only allows sales managers who are not members of the customer to view the customer, but also allows for secure settings of sales permissions for the customer, thus ensuring the security of customer data.
[0054] 5) Deleting the operation permissions configured by the administrator account for the first account, which may be deleting all permissions or deleting permissions for a specified data object.
[0055] 6) Changing the permissions configured by the administrator account for the first account from the current operation permissions to another operation permissions, such as changing viewing and editing personal data to editing all data.
[0056] Step 13, member exits.
[0057] When the sales account is deleted from the customer team, the third data object is handed over to the administrator account for maintenance. The third data object is the data object created or maintained by the sales account among all the data objects of the customer account. When a team member quits, member management can be performed through the unbinding process. That is, when a team member quits, the data he is responsible for will be automatically assigned to the customer person in charge.
[0058] In the above-mentioned customer data management solution, managing customer data through customer groups can facilitate members of the customer group to access and edit the customer data of the customer, avoiding the problem of data being unable to be shared between members, and also reducing the garbage data generated by the customer data management system due to setting up multiple similar customer accounts, reducing the pressure on the server, and the same customer is managed by the corresponding customer group, which also facilitates system maintenance.
[0059] (2) Access management for members of the customer team.
[0060] Step 21, the server receives an operation request sent by a team member on a terminal in the name of a sales account (ie, a second account).
[0061] Step 22, when the operation request indicates a request to perform a customer data operation on the customer account, search the permission configured for the second account from the permission configuration of the customer account, and the customer data operation is an operation on the second data object of the customer account.
[0062] Step 23, authenticating the second account, that is, whether the second account has the authority to operate the second data object, such as viewing authority, deletion, modification, addition and other editing authority.
[0063] The process of determining viewing permissions is as follows:
[0064] Step 231, determining whether the second account has the authority to view the customer account.
[0065] Step 232: if the second account has the permission to view the customer account, determine whether the second account has the permission to view the second data object.
[0066] Step 233: If the second account has the permission to view the second data object, the second account is allowed to view the second data object.
[0067] The process for determining editing permissions is as follows:
[0068] Step 231, determining whether the second account has the authority to view the customer account.
[0069] Step 232: if the second account has the permission to view the customer account, determine whether the second account has the permission to view the second data object.
[0070] Step 233: if the second account has the viewing permission for the second data object, determine whether the second account has the editing permission for the second data object.
[0071] Step 234: if it is determined that the second account has the editing authority for the second data object, allow the second account to edit the second data object.
[0072] As an optional embodiment, the following is combined with Figure 3 The steps shown further detail the technical solution of the present application.
[0073] Step S301, adding team members of the customer team. One customer can be followed up by multiple team members at the same time, and each customer has an account manager.
[0074] Step S302, configure the operation rights of each member of the customer team. The customer manager has the operation rights of adding team members, setting team member rights, removing team members, and leaving the customer, marking invalid, etc.
[0075] By default, account team members can view all data under the customer, including customer activities, sales opportunities, follow-up records, operation logs, attachments and other data objects, but team members can only edit the data they created.
[0076] The head of the customer team can set the permissions of the members, which are divided into: view and edit personal data, view all data, and edit all data. View and edit personal data means that the team members can only view and edit the data objects such as activities and sales opportunities created by themselves; view all data means that the team members can see all the data of the specified data objects under the customer, and can edit the data they created; edit all data means that the team members can view and edit all the data of the specified data objects under the customer.
[0077] For example: when the permissions of a customer's contacts are set to view and edit their own data, team members can only view and edit the contact data they created. If the permissions of a contact are set to view all data, sales can see the data of all contacts under the customer, but can only edit the data they created. If the permissions of a contact are set to edit all data, team members can view all contacts under the customer and edit them.
[0078] A reference for setting permissions for individual data objects such as sales opportunities, activities, accounts, attachments, historical followers, and operation logs Figure 4 , Figure 4 Schematic diagram of the interface for permission configuration.
[0079] Step S303: the terminal sends a customer data viewing request, where the data viewing request carries a customer identifier and an account identifier.
[0080] Step S304, determining whether the account contains the viewing authority corresponding to the customer identification. If it contains the viewing authority, execute step S306, otherwise execute step S305.
[0081] Step S305: the terminal receives the unauthorized prompt information returned by the server.
[0082] Step S306: the terminal receives the client data returned by the server.
[0083] Step S307: the terminal sends a data object viewing request, which carries the target data object and account.
[0084] Step S308, determine whether the account has the permission to view the data object. If yes, execute step S310, otherwise execute step S309. After the account manager completes the permission configuration, the team members can view the data of the customers under the account team. When viewing the data objects such as sales opportunities, contacts, activities, attachments, historical followers, operation logs, etc. under the customer, it is necessary to determine whether the sales has the permission to view the data object (access rights).
[0085] Step S309: the terminal receives the unviewable prompt information returned by the server.
[0086] Step S310, the terminal receives the data object returned by the server. When the group member's authority is to view and edit his own data, the group member can only view the data created by himself, for example: the group member can only see the sales opportunities created by himself, and cannot see the sales opportunities created by others; when the group member's authority is to view all data, the group member can view all data of the specified data object under the current customer (that is, the data created by himself and other group members), for example: the group member can view the operation log of everyone and the activity data created by everyone.
[0087] Step S311: the terminal sends a data editing request, and the editing request may carry an account and a data object.
[0088] Step S312, determining whether the account has the editing authority to edit the data object. If the account has the editing authority, executing step S314, otherwise, executing step S313.
[0089] Step S313: the terminal receives the non-editable prompt information returned by the server.
[0090] Step S314, editing the data object.
[0091] In one embodiment, referring to Figure 5 , Figure 5 The present invention is an association diagram of data tables in a customer data management method in an embodiment, including a customer table, an employee table, a customer group member table and a customer group authority setting table, wherein the customer table is used to store customer data, and the customer table includes a customer ID and a customer name. The employee table is used to store employee information, and the employee table includes an employee ID and an employee name, etc. The customer group member table is used to store customer group member information, and the customer group member table includes a customer ID and an employee ID. The customer ID and the employee ID are associated through the customer group member table, that is, the customer ID and the employee ID are bound. The customer group authority setting table includes a customer ID, an employee ID, a data object type and a data object authority, and an association relationship between the customer ID, the employee ID, the data object type and the data object authority is established through the customer group authority setting table.
[0092] In one embodiment, when a team member needs to operate a data object, such as editing customer data, editing sales opportunities, setting an activity to complete, downloading and deleting attachments, etc., it is necessary to verify whether the data object is created by the team member himself. If so, the team member can edit it. If not, it is necessary to verify whether the team member has the editing authority for the data object of this type, that is, the authority to edit all data. If so, the team member can edit it. If not, the team member cannot edit it.
[0093] The above-mentioned customer data management method can clearly configure sales permissions by individually authorizing each data object under each customer. It not only enables the sales manager who is not the customer to view the customer's function, but also can securely set the sales permissions under the customer, thereby ensuring the security of customer data.
[0094] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.
[0095] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.
[0096] According to another aspect of an embodiment of the present application, a request response device for implementing the above-mentioned request response method is also provided. Figure 6 is a schematic diagram of an optional request response device according to an embodiment of the present application, such as Figure 6 As shown, the device may include:
[0097] A receiving unit 61, configured to receive an operation request of a target account, wherein the operation request is used to request to perform a data operation related to a customer account, and data belonging to the same customer account is centrally stored in a database;
[0098] A search unit 63 is used to search the operation permissions configured for the target account from the permission configuration of the customer account;
[0099] The response unit 65 is used to respond to the operation request according to the operation authority of the target account.
[0100] It should be noted that the receiving unit 61 in this embodiment can be used to execute step S202 in the embodiment of the present application, the searching unit 63 in this embodiment can be used to execute step S204 in the embodiment of the present application, and the responding unit 65 in this embodiment can be used to execute step S206 in the embodiment of the present application.
[0101] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules as part of the device can be run in Figure 1 In the hardware environment shown, it can be implemented by software or by hardware.
[0102] Through the above module, when an operation request of a target account is received, the operation permission configured for the target account is searched from the permission configuration of the customer account; the operation request is responded to according to the operation permission of the target account. Since the data belonging to the same customer account is centrally stored in the database, rather than each salesperson storing the data of the same customer separately, the technical problem of too many junk files in the CRM system in the related technology can be solved, thereby achieving the technical effect of avoiding the generation of junk data.
[0103] Optionally, the target account includes an administrator account, wherein the search unit may further be used to: when the operation request indicates a request to perform a permission configuration operation, search for the operation permission configured for the target account from the permission configuration of the customer account, wherein the permission configuration operation is used to indicate that the target account configures the operation permission for the first account on the data object of the customer account, and the first account is a sales account that maintains the customer account; the response unit may further be used to: when the operation permission of the target account indicates that the target account is an administrator account, perform the permission configuration operation.
[0104] Optionally, the response unit can also be used to: configure the permission of the first account as a first operation permission, wherein the first operation permission indicates that the first account is allowed to view data objects of the customer account and edit data objects created by the first account; configure the permission of the first account as a second operation permission, wherein the second operation permission indicates that the first account is allowed to view and edit data objects created by the first account; configure the permission of the first account as a third operation permission, wherein the third operation permission indicates that the first account is allowed to view and edit all data objects of the customer account.
[0105] Optionally, the response unit may also be used to configure the permission of the first account as a fourth operation permission, where the fourth operation permission indicates that the first account is allowed to view or edit a first data object, where the first data object is a data object specified by the administrator account among all data objects of the customer account.
[0106] Optionally, the response unit may also be used to: delete the operation permission configured by the administrator account for the first account; and change the permission configured by the administrator account for the first account from the current operation permission to another operation permission.
[0107] Optionally, the target account includes a second account that is a sales account, wherein the search unit may also be used to: when the operation request indicates a request to perform a customer data operation on the customer account, search for operation permissions configured for the second account from the permission configuration of the customer account, wherein the customer data operation is an operation on a second data object of the customer account; and the response unit may also be used to: when the operation permissions of the second account indicate that the second account is allowed to operate on the second data object, perform the customer data operation.
[0108] Optionally, the customer data operation includes an operation of viewing a second data object, and the response unit may further be used to: determine whether the second account has viewing authority for the customer account; if the second account has viewing authority for the customer account, determine whether the second account has viewing authority for the second data object; if the second account has viewing authority for the second data object, allow the second account to view the second data object.
[0109] Optionally, the customer data operation includes an operation of editing a second data object, and the response unit may further be used to: determine whether the second account has viewing authority over the customer account; if the second account has viewing authority over the customer account, determine whether the second account has viewing authority over the second data object; if the second account has viewing authority over the second data object, determine whether the second account has editing authority over the second data object; if it is determined that the second account has editing authority over the second data object, allow the second account to edit the second data object.
[0110] Optionally, the device of the present application may also include a configuration unit for receiving an add instruction before receiving an operation request from the target account, wherein the add instruction is used to instruct to add the second account as a sales account for maintaining the customer account; in response to the add instruction, the second account is added as a sales account for maintaining the customer account, and default operation permissions or specified operation permissions are configured for the second account.
[0111] Optionally, the configuration unit of the present application may also be used to: after responding to the operation request according to the operation authority of the target account, when the second account is deleted from the sales account that maintains the customer account, hand over the third data object to the administrator account for maintenance, wherein the third data object is a data object created or maintained by the second account among all data objects of the customer account.
[0112] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules as part of the device can be run in Figure 1 In the hardware environment shown, it can be implemented by software or by hardware, wherein the hardware environment includes a network environment.
[0113] According to another aspect of an embodiment of the present application, a server or terminal for implementing the above-mentioned request response method is also provided.
[0114] Figure 7 is a structural block diagram of a terminal according to an embodiment of the present application, such as Figure 7 As shown, the terminal may include: one or more ( Figure 7 (only one is shown) processor 701, memory 703, and transmission device 705, as shown in Figure 7 As shown, the terminal may also include an input and output device 707.
[0115] Among them, the memory 703 can be used to store software programs and modules, such as the program instructions / modules corresponding to the request response method and device in the embodiment of the present application. The processor 701 executes various functional applications and data processing by running the software programs and modules stored in the memory 703, that is, realizing the above-mentioned request response method. The memory 703 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 703 may further include a memory remotely arranged relative to the processor 701, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.
[0116] The above-mentioned transmission device 705 is used to receive or send data via a network, and can also be used for data transmission between a processor and a memory. Specific examples of the above-mentioned network may include a wired network and a wireless network. In one example, the transmission device 705 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers via a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 705 is a radio frequency (Radio Frequency, RF) module, which is used to communicate with the Internet wirelessly.
[0117] Specifically, the memory 703 is used to store application programs.
[0118] The processor 701 may call the application stored in the memory 703 through the transmission device 705 to perform the following steps:
[0119] receiving an operation request of a target account, wherein the operation request is used to request to perform a data operation related to a customer account, and data belonging to the same customer account is centrally stored in a database;
[0120] Find the operation permissions configured for the target account from the permission configuration of the customer account;
[0121] Respond to the operation request based on the operation permissions of the target account.
[0122] The processor 701 is further configured to execute the following steps:
[0123] Determine whether the second account has the authority to view the customer account;
[0124] If the second account has viewing authority for the customer account, determining whether the second account has viewing authority for the second data object;
[0125] If the second account has viewing authority for the second data object, determining whether the second account has editing authority for the second data object;
[0126] If it is determined that the second account has the editing authority for the second data object, the second account is allowed to edit the second data object.
[0127] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.
[0128] It can be understood by those skilled in the art that Figure 7 The structure shown is for illustration only, and the terminal may be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 7 It does not limit the structure of the above electronic device. For example, the terminal may also include Figure 7 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 7 Different configurations shown.
[0129] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.
[0130] The embodiment of the present application also provides a storage medium. Optionally, in this embodiment, the storage medium can be used to execute the program code of the request response method.
[0131] Optionally, in this embodiment, the storage medium may be located on at least one network device among a plurality of network devices in the network shown in the above embodiment.
[0132] Optionally, in this embodiment, the storage medium is configured to store program codes for executing the following steps:
[0133] Receiving an operation request of a target account, wherein the operation request is used to request to perform a data operation related to a customer account, and objects belonging to the same customer account are centrally stored in a database;
[0134] Searching for the operation permissions configured for the target account from the permission configuration of the customer account;
[0135] The operation request is responded to according to the operation authority of the target account.
[0136] Optionally, the storage medium is further configured to store program codes for executing the following steps:
[0137] Determining whether the second account has permission to view the customer account;
[0138] In the case where the second account has the permission to view the customer account, determining whether the second account has the permission to view the second data object;
[0139] If the second account has viewing authority for the second data object, determining whether the second account has editing authority for the second data object;
[0140] If it is determined that the second account has the editing authority for the second data object, the second account is allowed to edit the second data object.
[0141] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.
[0142] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.
[0143] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0144] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
[0145] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.
[0146] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.
[0147] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0148] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0149] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. A request response method, characterized in that: include: Receive an operation request from a target account, wherein the operation request is used to request the execution of a data operation related to a customer account, and the data belonging to the same customer account is centrally stored in a storage area in a database identified by the customer account, and the sales accounts of each team member in the customer team to which the target account belongs simultaneously follow up the customers corresponding to the customer account, and the customer team members are allowed to view all the data under the customer accounts followed by the customer team by default, but the customer team members can only edit the data created by themselves, and the default permissions are configured for the sales accounts entering the customer team; Searching for the operation permissions configured for the target account from the permission configuration of the customer account; Responding to the operation request according to the operation authority of the target account; The target account includes an administrator account, wherein: Searching for the operation permission configured for the target account from the permission configuration of the customer account includes: searching for the operation permission configured for the target account from the permission configuration of the customer account when the operation request indicates a request to perform a permission configuration operation, wherein the permission configuration operation is used to indicate that the target account configures the operation permission for the first account to the data object of the customer account, and the first account is a sales account that maintains the customer account; Responding to the operation request according to the operation authority of the target account includes: performing the authority configuration operation when the operation authority of the target account indicates that the target account is an administrator account.
2. The method according to claim 1, characterized in that Executing the permission configuration operation includes one of the following: Configuring the permission of the first account as a first operation permission, wherein the first operation permission indicates that the first account is allowed to view the data objects of the customer account and edit the data objects created by the first account; Configuring the permission of the first account as a second operation permission, wherein the second operation permission indicates that the first account is allowed to view and edit data objects created by the first account; The permission of the first account is configured as a third operation permission, wherein the third operation permission indicates that the first account is allowed to view and edit all data objects of the customer account.
3. The method according to claim 1, characterized in that Executing the permission configuration operation includes: The permission of the first account is configured as a fourth operation permission, wherein the fourth operation permission indicates that the first account is allowed to view or edit a first data object, and the first data object is a data object specified by the administrator account among all data objects of the customer account.
4. The method according to claim 1, characterized in that: Executing the permission configuration operation includes one of the following: Deleting the operation authority configured by the administrator account for the first account; The authority configured by the administrator account for the first account is changed from the current operation authority to another operation authority.
5. The method according to claim 1, characterized in that The target account includes a second account which is a sales account, wherein: Searching for the operation permission configured for the target account from the permission configuration of the customer account includes: searching for the operation permission configured for the second account from the permission configuration of the customer account when the operation request indicates a request to perform a customer data operation on the customer account, wherein the customer data operation is an operation on a second data object of the customer account; Responding to the operation request according to the operation authority of the target account includes: performing the customer data operation if the operation authority of the second account indicates that the second account is allowed to operate the second data object.
6. The method according to claim 5, characterized in that The customer data operation includes an operation of viewing the second data object, wherein, if the operation authority of the second account indicates that the second account is allowed to view the second data object, performing the customer data operation includes: Determining whether the second account has permission to view the customer account; In the case where the second account has the permission to view the customer account, determining whether the second account has the permission to view the second data object; In the case that the second account has the permission to view the second data object, the second account is allowed to view the second data object.
7. The method according to claim 5, characterized in that The customer data operation includes an operation of editing the second data object, wherein, when the operation authority of the second account indicates that the second account is allowed to edit the second data object, performing the customer data operation includes: Determining whether the second account has permission to view the customer account; In the case where the second account has the permission to view the customer account, determining whether the second account has the permission to view the second data object; If the second account has viewing authority for the second data object, determining whether the second account has editing authority for the second data object; If it is determined that the second account has the editing authority for the second data object, the second account is allowed to edit the second data object.
8. The method according to claim 5, characterized in that Before receiving the operation request of the target account, the method further includes: receiving an adding instruction, wherein the adding instruction is used to instruct to add the second account as a sales account for maintaining the customer account; In response to the adding instruction, the second account is added as a sales account for maintaining the customer account, and a default operation authority or a specified operation authority is configured for the second account.
9. The method according to claim 5, characterized in that After responding to the operation request according to the operation authority of the target account, the method further includes: When the second account is deleted from the sales account maintaining the customer account, the third data object is handed over to the administrator account for maintenance, wherein the third data object is a data object created or maintained by the second account among all data objects of the customer account.
10. A request response device, characterized in that: include: A receiving unit, configured to receive an operation request of a target account, wherein the operation request is used to request to perform a data operation related to a customer account, and the data belonging to the same customer account is centrally stored in a storage area in a database identified by the customer account, and the sales accounts of each team member in the customer team to which the target account belongs simultaneously follow up the customers corresponding to the customer account, and the customer team members are allowed to view all data under the customer accounts followed by the customer team by default, but the customer team members can only edit the data created by themselves, and the default permissions are configured for the sales accounts entering the customer team; A search unit, used to search the permission configured for the target account from the permission configuration of the customer account; A response unit, configured to respond to the operation request according to the operation authority of the target account; The target account includes an administrator account, wherein: Searching for the operation permission configured for the target account from the permission configuration of the customer account includes: searching for the operation permission configured for the target account from the permission configuration of the customer account when the operation request indicates a request to perform a permission configuration operation, wherein the permission configuration operation is used to indicate that the target account configures the operation permission for the first account to the data object of the customer account, and the first account is a sales account that maintains the customer account; Responding to the operation request according to the operation authority of the target account includes: performing the authority configuration operation when the operation authority of the target account indicates that the target account is an administrator account.
11. A request response system, characterized in that: include: Logging into the smart terminal with the target account to send an operation request, wherein the operation request is used to request to perform a data operation related to the customer account; The server is used for, upon receiving the operation request, searching the permission configured for the target account from the permission configuration of the customer account, and responding to the operation request according to the operation permission of the target account, wherein the operation request is used to request to perform data operations related to the customer account, and the data belonging to the same customer account is centrally stored in a storage area in the database identified by the customer account, and the sales accounts of each team member in the customer team to which the target account belongs follow up the customers corresponding to the customer account at the same time, and the customer team members are allowed to view all the data under the customer accounts followed by the customer team by default, but the customer team members can only edit the data created by themselves, and the sales account configuration for entering the customer team The target account includes an administrator account, wherein searching for the operation permission configured for the target account from the permission configuration of the customer account includes: searching for the operation permission configured for the target account from the permission configuration of the customer account when the operation request indicates a request to perform a permission configuration operation, wherein the permission configuration operation is used to indicate that the target account configures the operation permission for the first account to the data object of the customer account, and the first account is a sales account for maintaining the customer account; responding to the operation request according to the operation permission of the target account includes: executing the permission configuration operation when the operation permission of the target account indicates that the target account is an administrator account; A database, in which data objects belonging to the same customer account are centrally stored.
12. A storage medium, characterized in that: The storage medium includes a stored program, wherein the program executes the method described in any one of claims 1 to 9 when executed.
13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: The processor executes the method described in any one of claims 1 to 9 through the computer program.
Citation Information
Patent Citations
Control system and method of customer information
CN101996348A
Method, device and system of access authentication
CN104202306A
Customer relationship management system
CN108241981A
Cloud storage account authentication method and device
CN109510849A
Method, system and program product for authenticating a user seeking to perform an electronic service request
US20080066165A1
