I. Function Introduction

RiskGuard supports multi-level group architecture management. Branch company features include:

• Independent Operations: Separate account sets, permission systems, and business process configurations
• Data Isolation: Strict data permission isolation between branches
• Flexible Expansion: Supports unlimited levels of branch structures
• Unified Control: Group headquarters can view all branch data

II. Operation Steps

1. Add New Branch

1. Administrator logs into management backend
2. Navigation menu select: 【System Settings】→【Organization】
3. Click "New" button on toolbar

4. Fill in organization information:

• Organization Name (Required, e.g. "East China Branch")
• Organization Code (Recommended branch abbreviation, e.g. "EC")
• Organization Type: Select "Company"
• Parent Organization: Select affiliated group/region

5. Click "Save" to complete creation

2. Set Branch Administrator

1. Navigation menu select: 【System Settings】→【Users】
2. Create or select target user
3. Click "Edit" button to enter user details
4. Switch to "Role Authorization" tab
5. Select "Branch Administrator" role from available roles list
6. Click ">" to add to authorized roles
7. Click "Confirm" to save configuration

3. Branch Administrator Permissions

Branch administrators have the following core permissions:

• Organization Management: Create/manage departmental structure
• User Management: Manage user accounts
• Process Configuration: Customize approval workflows
• Template Management: Modify print templates
• Data Permissions: View/manage all company data
• Parameter Configuration: Set business parameters

III. Configure Branch Parameters

1. Basic Configuration

1. Log in using branch administrator account
2. 【System Settings】→【Configuration】
3. Set:
   • Company LOGO
   • System Name
   • Graphic Verification Code

2. Process Customization

1. 【System Settings】→【Workflow】
2. Customize:
   • Approval processes
   • Business rules
   • Notification templates

IV. Precautions

1. Coding Standards:
   • Branch codes must be globally unique
   • Recommended format: "GroupCode-RegionCode"
2. Permission Isolation:
   • Branch data is inaccessible across branches by default
   • Requires group administrator authorization for data sharing
3. Hierarchy Limitations:
   • Departments/groups can be created under branches
   • Cannot create sub-branches
4. Administrator Permissions:
   • Branch administrators cannot manage other branches
   • Cannot modify group-level configurations

V. Best Practices

1. Naming Conventions:
   • Include region identifier in branch name (e.g. "North China")
   • Keep codes concise (≤4 characters)
2. Permission Planning:
   • Create dedicated "Branch Administrator" role
   • Limit permission scope to own branch
3. Data Initialization:
   • Use templates to import initial data
   • Create test accounts to verify permissions
4. Regular Audits:
   • Quarterly checks on branch data isolation
   • Annual updates to branch administrator permissions