How to Use WPS Chat File Upload Control on macOS

Last updated:July 23, 2026

Use Chat File Upload Control through 6 how-to topics, all completed in the enterprise admin console.

How-to Index

How-to Guide

1. Open the Chat File Management page

Feature path: Enterprise Admin Console > WPS Collaboration > Chat File Management > File Control

  1. Sign in to the enterprise admin console.
  2. In the left navigation pane, click WPS Collaboration to expand the collaboration menu.
  3. Click Chat File Management to open the chat file management page.
  4. Click the File Control tab.

Success Criteria

  • Interface result: The page switches to the File Control tab under chat file management.
  • Next action available: You can continue to view the chat file upload control area.

Tips While Using

  • Permission requirement: An enterprise administrator account is required.
  • Environment note: A working network connection is required.

2. Open chat file upload control settings

Feature path: Chat File Management > File Control > Chat File Upload Control > Settings

  1. Open the Chat File Management page.
  2. Click the File Control tab to switch to the file control settings page.
  3. In the Chat File Upload Control area, click Settings.

Success Criteria

  • Interface result: The upload control rule management page opens.
  • Next action available: You can review rules or create a new rule.

Tips While Using

  • Common mistake: If you do not switch to the File Control tab first, the settings entry may not appear.

3. Review the created rule list

Feature path: Chat File Upload Control page > Rule List

  1. Open the upload control rule management page.
  2. Check the number of created rules shown at the top of the page.
  3. Review the rule list, including rule name, condition, control category, control action, status, and operations.

Success Criteria

  • Interface result: The rule list is displayed and the created rule count is visible.
  • Next action available: You can continue to edit, enable, or disable rules.

Tips While Using

  • Environment note: You can create up to 10 control rules.

4. Create a new upload control rule

Feature path: Upload Control Rule List > New Rule

  1. On the upload control rule list page, click New Rule.
  2. Enter a rule name in the Rule Name field.
  3. In the Condition area, choose a condition type such as File Size or File Format.
  4. Enter the specific condition value.
  5. If you need more than one condition, click Add Condition.
  6. Continue to configure the remaining rule items.

Success Criteria

  • Interface result: The rule editing page shows the entered rule name and condition content.
  • Next action available: You can continue to set the control category, control action, and hit message.

Tips While Using

  • Common mistake: Multiple file extensions in a file format condition should be entered in the format required by the page.

5. Set the control category and control action

Feature path: Rule Editing Page > Control Category > Control Action

  1. In the Control Category area, choose Allow or Block.
  2. In the Control Action area, select Upload.
  3. Check whether the selected category and action match your policy goal.

Success Criteria

  • Interface result: The selected control category and control action are visible on the page.
  • Next action available: You can continue to configure the hit message and save the rule.

Tips While Using

  • Common mistake: If the category and action do not match the intended policy, the rule result may not match your goal.

6. Set the hit message

Feature path: Rule Editing Page > Hit Message

  1. In the Hit Message area, choose Default Message or Custom Message.
  2. If you choose Custom Message, enter the message text in the input box.
  3. After the rule is saved, members see this message when they upload a file that matches the rule.

Success Criteria

  • Interface result: The hit message type and content are saved in the rule.
  • Next action available: Members see the configured message when a rule is triggered.

Tips While Using

  • Common mistake: If a custom message is too short, members may not clearly understand the reason for the restriction.