This section briefly introduces the division and roles of HIVE console managers. The HIVE console clarifies the roles between the managers and supports smooth business operation.
Manager division and role
HIVE console managers are divided into 3 roles.
|GAMEVIL, Com2uS, GCP
|Manage company registration
Manage access authority
Create big menu
Register menu and authorization managers
|Create product menu
Set up permission
|Create and manage groups
The system manager is the super manager of the HIVE console and the authority will be granted to some of the development and management personnel of the HIVE console.
The product manager is responsible for developing each product and back office for each product. The authority is given to the developers of HIVE products and you’ll be able to control all functions required for development and management, such as menu management and permission settings. However, the product manager cannot grant the authority to use the product since only the authorization manager can perform such operation.
The authorization manager grants permission to users of back office for the products that have been developed. The PIC of each company will perform the role.
New Product Addition and Usage Flow
1. Product planning
The stage for product planning such as product composition and policy. We plan product through various discussions about what kind of product is needed in various related departments such as platform planner, developer, business department, and what function should be included.
2. Product development
The stage to develop the actual product to fit the plan. Development schedules are included, including development and QA (test) schedules.
3. Create product
This is the actual first step in putting the product on the HIVE console. Create a menu corresponding to the product name and add it to the console. This task is handled by the system manager of the HIVE console.
4. Product manager setup
Set up the planners and developers who will be in charge of product development in the HIVE console as product managers. This is done by the system manager.
5. Permission registration
The product manager registers the permission to be used by the product through the permission management menu. By default, the permission to read is set automatically. In the case of simple inquiry page with no function, there is no need to register separate permissions.
6. Menu setup
This is the actual step of setting up the back office menu needed to use the product. Register the categories and pages under the product and prepare to use the product. This step will be performed by the developer in charge of the product managers. Once this step is complete, the final deployment for product use is complete.
7. Request authority
Once the product is ready to be used and the guide is released, requests for authority will be delivered. This will be done through each company’s approval system, and the contents of the request will be passed to the authorization manager of each company.
8. Create group
The authorization manager will create groups and grant authority according to the authorization request from the user.
9. Perform operation
All preparation is complete and the product is ready to be used.