Appearance
Bulk Operations
Bulk Operations let you update many customers at once. Open Bulk Operations from the sidebar and choose the action you need. Availability depends on your role and staff permissions; every operation is limited to your permitted ISP or reseller scope.
Enter customer IDs
Bulk customer actions accept a list of customer IDs. You can enter IDs with commas, spaces, or line breaks, and you can use an ascending range:
text
10, 15, 23
3901-3905Confirm that the selected IDs and the target reseller or package are correct before submitting. Some operations process eligible customers independently, so review the operation result and logs for skipped records.
Transfer customers
Use Transfer Customers to move multiple customers to a different reseller. Select the customer IDs, choose a reseller from your downline, and confirm the transfer.
The destination reseller must be in the same ISP and must be allowed to sell each customer's package. Customers that fail this validation are skipped while eligible customers transfer. Each transferred customer adopts the destination reseller's billing type.
Bulk customer settings
Use Bulk Customer Settings to apply the same change to multiple customers. Select only the fields you intend to update, then enter their new values. The available updates include:
- Address
- Password
- Package
- Profile status
- Expiry date
- Owning reseller
At least one field must be selected. Package and reseller changes must meet the same package-assignment and scope rules as an individual customer update.
Renew customers in bulk
Choose Renew Customers to activate or renew a group together. You can keep each customer's current package or select one package for all selected customers. Choose whether the resulting invoices are marked paid or kept unpaid, then confirm the action.
Bulk renewal uses the same pricing, wallet deductions, expiry calculations, and static-IP charges as a single customer renewal. A package change can disconnect an affected customer's active session so the new RADIUS policy takes effect; renewing the same package does not disconnect the session.
When available, review the renewal preview first. It shows the projected customer charges, wallet impact, and customers that cannot be processed before anything is billed.
Enable or disable customers
- Disable Customers changes selected accounts to disabled and immediately sends a disconnect request for active sessions.
- Enable Customers changes selected accounts to active so they can authenticate again.
Admins can manage customers in their ISP hierarchy. Lower reseller roles are limited to their own direct customers.
Delete and restore customers
Bulk Delete Customers is an admin-only soft-delete action. Customers must already be disabled; records that are still active are skipped. Soft-deleted customers lose RADIUS access but remain available in Customers → Deleted for review and restoration.
Restoring a deleted customer keeps it disabled and returns it to its original reseller when possible. If that reseller no longer exists, the customer is assigned to the ISP admin.
Permanent deletion is also admin-only and cannot be undone. It removes the customer's account, billing records, RADIUS data, session history, and related logs. Use it only after confirming that the soft-deleted record is no longer needed.
Bulk imports
Dream Radius also supports CSV imports for customers, policies, packages, resellers, and package assignments. Download the relevant sample template, keep its header names, add one item per row, and upload the file from the corresponding page.
Import rows are validated independently. A failed row does not stop valid rows from being created, so always review the summary and the Bulk Operation Logs after an import. Customer imports support separate modes to add new customers or update existing customers matched by username.
Review operation logs
Open Logs & Reports → Bulk Operation Logs to review imports, transfers, renewals, status changes, and bulk settings updates. The logs record the operator, time, summary, affected customers, and any failure reasons.
Use destructive actions carefully
Bulk changes can affect many live subscribers at once. Export or review the filtered customer list first, begin with a small test group, and verify the result in Bulk Operation Logs before processing a larger batch.