How to Add Branch Companies
About 392 wordsAbout 1 min
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
- Administrator logs into management backend
- Navigation menu select: 【System Settings】→【Organization】
- Click "New" button on toolbar

- 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
- Click "Save" to complete creation
2. Set Branch Administrator
- Navigation menu select: 【System Settings】→【Users】
- Create or select target user
- Click "Edit" button to enter user details
- Switch to "Role Authorization" tab
- Select "Branch Administrator" role from available roles list
- Click ">" to add to authorized roles
- 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
- Log in using branch administrator account
- 【System Settings】→【Configuration】
- Set:
- Company LOGO
- System Name
- Graphic Verification Code
2. Process Customization
- 【System Settings】→【Workflow】
- Customize:
- Approval processes
- Business rules
- Notification templates
IV. Precautions
- Coding Standards:
- Branch codes must be globally unique
- Recommended format: "GroupCode-RegionCode"
- Permission Isolation:
- Branch data is inaccessible across branches by default
- Requires group administrator authorization for data sharing
- Hierarchy Limitations:
- Departments/groups can be created under branches
- Cannot create sub-branches
- Administrator Permissions:
- Branch administrators cannot manage other branches
- Cannot modify group-level configurations
V. Best Practices
- Naming Conventions:
- Include region identifier in branch name (e.g. "North China")
- Keep codes concise (≤4 characters)
- Permission Planning:
- Create dedicated "Branch Administrator" role
- Limit permission scope to own branch
- Data Initialization:
- Use templates to import initial data
- Create test accounts to verify permissions
- Regular Audits:
- Quarterly checks on branch data isolation
- Annual updates to branch administrator permissions
