ToB SaaS Product user management modes: active and passive invited to register

First, the differences in the nature of the business, determine the product's core objectives

2B SaaS Product user system design

2C products for individual users is the core of the system is user-acquisition, so most of the 2C product design focuses on the user's system user registration, login, users can establish accurate portrait, so as to achieve the goal of cash flow.

2B products for corporate users, users of the system is the core of the organization, staff and meticulous management, improve people efficiency, in order to achieve cost savings goals.

 

Second, the demand difference business scenarios, determine the details of the product's features

1.  Register a scene

2C registered products are mainly used for personal user registration scenario, the focus is to provide multiple channels of registration methods, such as account number, phone, third-party social applications (micro-channel, microblogging, etc.), the core objective is not only user-friendly registration, and It can open up multi-channel multi-platform account.

2B product registration is divided into two parts: Enterprise Administrator on behalf of business registration and business registration staff.

2B platform-based SaaS product, and 2C biggest difference is that the product requires users to pay. Therefore, the party platform for the enterprise (tenant platform) provides a registration entrance, on the one hand the need to facilitate the tenants can quickly register trial products through other channels, on the one hand companies need to verify information, identify the user does potential users.

1) Registered:

When the enterprise administrator on behalf of business registration, registration information needs to be provided: Administrator nickname, phone number, email, enterprise business information (name, organization code, address, legal information, etc.).

In which the integrity of the information industry and commerce, different product requirements are not the same, need to be based on specific products. If convenient pull new registration to minimize industrial and commercial enter the required information, if higher product safety requirements, requirements of industry and commerce can try to be filled out completely.

2) Enterprise Business Information Certification:

This part is not the strong demand scenario, depending on the security requirements of the product. General security require a higher platform products, will be registered in the enterprise, industrial and commercial enterprises to enter authentication information link. This part of either platform administrator manual review or verify enterprise business information for compliance through third-party certification. After the completion of the enterprise certification, you can try the product.

Such as higher non-safety requirements of the product, you can skip this part, completed by the tenant after the registration page either registered successfully.

3) Employees Registration:

  • Registration information: Nickname, phone number, email, other personal information;
  • Passive Invitation: General B-end products and more employees as a daily working tool, and therefore use more system administrator to open the account, the administrator through the background to the employee information registration system, employees can log on. Passive invitation-employee company is strong and binding relationship, employee accounts can not exist independently;
  • Initiative Registration: active employee registration scenario, employees take the initiative to register the product account, and then apply to join the company, after examination by the enterprise administrator, and business associates. The way individual users can be used independently as a platform for product users, but also can be used as a platform for users as a company employee. Nail that is a typical representative of such products, an employee can join multiple companies at the same time;
  • Profile: After registering employees, registering the employee information to the system, and be able to show in the system, query, complete personal information.

 

2. Log scene

Login scene easier to understand, the current B-side product comparison C-terminal product is still more traditional, multi-use email / phone log.

The future hope to achieve, B and end products can open up more C-terminal product platform, can log in through a common third-party account, achieve business and social connections.

 

3. User-portrait

User portrait 2C is a vital element in the product, the user only accurate portrait, more accurate service to good customers. Whether it is electricity supplier, or the information platform, is the core product delivery precision marketing based on user portrait.

2B products rarely speak portraits user relevant content, in fact 2B for products, user portrait is also crucial.

The author is currently engaged in CRM product-related work, the question CRM core to be solved is to help your customer acquisition (CPA), then how to build the customer's corporate label, to follow corporate tag attributes, with big data analysis, help your customer find his client group, is the subject of the author in a recent study.

  • The establishment of corporate property Dimensions tab: such as industry, size, scope of business, customer base ranges.
  • Competitive business model label correlation analysis: easy to understand the market environment, competitors analysis, timely adjustment of the company's strategy.
  • Potential audience (business) label correlation model analysis: analysis using the data model to help companies identify potential customers, improve user acquisition rates.

 

4. Structure

2C product In essence, there is no organization, individual users is the main product, but there is the concept of group / community.

2B is the main application products business, and organizational structure is a necessary means and methods of business operations management. Therefore, the organizational structure of management is an important part of the user's system.

1) establish the organizational structure

Organizational units are department, so administrators need to be able to establish, adjust (edit, merge), delete departments in accordance with the organizational structure of the enterprise.

2B SaaS Product user system design

2) Sector tree

Sector as a unit organizational structure, but the molecular structure of the organization, and to form organizations, we must follow the form of business enterprise requires a certain hierarchy. Therefore sector is not just a simple description, also need to have level description, which we need to follow when building department hierarchy established departments, clearly defined established department is the higher authorities, the lower sector.

2B SaaS Product user system design

3) address book display

After the administrator has been created by the organizational structure of the background, employees can query the address book according to the department structure shown by the front desk.

 

5. Role Management (This section is important and difficult system design 2B users)

Role Management is a unique feature of B-end products, according to its employees in charge of business modules divided into different job responsibilities.

Due to corporate data with high security and privacy requirements, according to different job responsibilities of employees in different positions for the operation of business data / different view permissions.

Therefore, we designed a management role, this role is not the role of job functions in the strict sense, and in order to distinguish between different employees different system privileges designed system role , which is RBAC design.

1) establish the role

The main objective of the establishment is the role of the establishment of a user group permissions, user rights within the group have the same privileges.

2B SaaS Product user system design

2) assign roles privileges

Role-based distribution system permissions in order to achieve the user in different roles have different permissions.

2B SaaS Product user system design

  • Functional competence: What product features used to set the character can use, if you do not belong to function in the role of business category can shield directly to the user, to avoid excessive interference function menu users of the product.
  • Function operating authority: Enterprise Management finer, more specific employee responsible for the work, within a function, different people perform different operations division in accordance with its responsibilities, in order to ensure the accuracy and security of data, you need to assign the same function to different roles under different operating authority.
  • Description fields within the competence of features: a business function has different attributes description field, but attribute different roles of interest is not the same, in order to be able to distinguish different roles need to be set to read different fields / write permissions.
  • Data permissions: enterprise resource on the nature of enterprise data, but also has both privacy and sharing. Operating authority must have the function of a role, but he can operate what data this function? Data can only be operated his own creation, or can manipulate the data created by other employees need data? This need to control data access. This requires that when the data is created, the article also requires a corresponding data fields to describe their ownership of the record, the data belongs to which user, which belongs to the department, and ultimately achieve the association and the data available to implement role-based employees rights management.

 

6. Employee Management

Staff management functions are unique to the B-side products, employees are an important part of the organization, employees are also real end-user products.

B end product is essentially to be able to help employees improve work efficiency, improve people efficiency, in order to achieve the goal of reducing business managers operating costs.

1) New employees

The aforementioned user registration process is the new employees. Including passive invitation and active registration in two forms, the main goal is to register employee information to the system, and to establish the relationship between employees and related businesses.

2) establishment of employee reporting relationships structure

In order to achieve fine management, internal organizational structure set in accordance with the general reporting relationships of employees, from the CEO to junior staff therefore will form a tree organizational relationships, organizational structure and the structure can be completely correspondence that all employees in the department are report to department heads, but there are some different groups within the department, reporting to different people responsible for different groups of people.

Therefore, reporting relationships and organizational structure of relationships have some relevance, but not entirely correspond , so we need to design employee reporting relationships function.

2B SaaS Product user system design

3) employee turnover set

In order to ensure the security of corporate data, the staff after leaving, the need to freeze the accounts of employees, former employees will not be able to log in as the employees of the system to ensure the security of corporate data.

  • Set to leave : The employee account is set to leave the state, employee account is frozen;
  • Data Transfer: When employees leave, their business needs other employees to take over, so when the employee responsible for serving business data needs to be transferred to a new user, this function needs to be part of the planning data transfer function.

So far, users of the system function 2B basic design complete with a weight difficulty lies in the organizational structure, access control , need to focus on

Published 39 original articles · won praise 3 · Views 2415

Guess you like

Origin blog.csdn.net/Hotice888/article/details/105330038