Page Comparison

1. Setting - User/Admin Management:

1. change label to Settings → Admin

2. Access right update: Currently only MAF Admin (user_id == 1) is able to view this page, now we change to

   1. user_type != 0 is able to view this page

   2. tables access right:

      1. User Management table: No limitation as long as able to view this page

      2. Subscription Management table: Only user_id == 1 is able to view

      3. Sales Code Management table (new add): only user_type == 1 is able to view

Logic:

Only User Type not 0 can access User Management table

Only MAF Admin: User ID = 1; so only MAF Admin can access Subscription Management

Only User Type = 1 can access Sales Code Management table, once user is assigned in sales code management table, their user type will become 1

MAF Admin will assign sales code to Agency (User Type becomes 1) first (Parent is MAF), then Agency will be able to access the Sales Code Management table to assign sales code to each agent (Parent is Agency)

Details:

Open inspect to check the data in network to determine user type is 1 or 0

SALES_CODE_TYPES:
0: client
1: ‘AGENCY’,
2: ‘AGENT’

so if 0, means client

if 1, means agency

if 2, means agent or sales

so user_type is the value to control; if the user in sales code, then should be 1 or 2; otherwise, it is 0

Any sales agency is able to create sales code and assign to the user so sales agency is able to create his own sales agencies or sales agents under his umbrella; even for user with existing account, user can be under any agency if a sales code is assigned to the user; so the user could be both client and sales agent/agency

New Feature

2. Admin Management - Add Sales Code table under

1. Sales Code table after Subscription Management table

2. this table is able to view, edit, add, delete

3. this table only accessible if user_type == 1

New Feature

3. General Ledger - add FCM STATEMENT tab

1. Add FCM Statement tab (after General Ledger)

2. 经纪商结算单

3. Start Date and End Date

   1. Start Date:

      1. key: s_date

      2. default 2 weeks from today

      3. cache in FE

      4. reset after login

   2. End_date:

      1. key: e_date

      2. default today

      3. cache in FE

      4. reset after login

New Feature