List groups, sorting, bulk operations and duplication

Lists with many entries can be grouped, sorted manually, searched and changed in bulk, and the controls work the same way on every page. Order and groups only affect how the admin UI displays the list; changing them does not restart running instances or drop connections.

Supported lists

Page	Lists
Dynamic DNS	Tasks; DNS records within a task
STUN Traversal	Rules
Port Forwarding	Rules
SSL Certificates	Certificates
Web Services	Sites within a listener (listeners themselves can be moved up and down)
WAF Firewall	Instances
Intrusion Prevention	Log rules
frp	frpc instances, frps instances, proxies
Cloudflare Tunnel	Tunnels
File Browser	Instances
Storage Mounts	Mounts
Wake-on-LAN	Devices
Scheduled Tasks	Tasks
Notifications	Channels, rules
Web Terminal	Saved connections
API Tokens	Tokens

Most of these lists offer both "Card view" and "Compact view", switched at the top right of the list; on narrow screens the card view is always used.

Groups

Fill in "Group" in the edit dialog (up to 64 characters; you can pick an existing group). Leave it empty for no group. As soon as one entry has a group, the list is shown as collapsible sections by group: groups appear in the order they first occur, ungrouped entries come last, and the collapsed state of each group is saved in the browser. The search box filters entries by name, group, remark and similar fields, and expands all groups while searching.

Hover over a group heading and click the pencil button to rename the group: all entries in the group take the new name and keep their position and order. If you rename it to the name of an existing group, the two groups are merged after confirmation.

Sort mode

Click "Sort & batch" to enter sort mode. All entries are shown, and search and filters are paused:

• Use the arrows to move entries up or down within a group, or on a group heading to move the whole group;
• On desktop you can drag entries directly; dropping onto an entry or heading of another group adds the entry to that group;
• After selecting several entries (the checkbox on a group heading selects the whole group), drag any one of them and all selected entries move together in their current order;
• The toolbar can move the selected entries to a given group in one step ("Move to group"); leaving it empty removes them from their group.

Phones and other narrow screens do not support dragging; use the arrows and the toolbar to do the same.

Bulk operations

After checking entries in sort mode, the toolbar can also:

• Enable / Disable: saves all checked entries at once; entries already in the target state are not restarted;
• Delete: the confirmation dialog lists the entries to be deleted, and deletion cannot be undone. If any entry cannot be deleted (for example a certificate still used by a site), nothing is deleted and the reason is shown.

A bulk operation handles up to 500 entries. It is saved only when every entry passes validation; if any entry fails, nothing changes. Wake-on-LAN devices have no enable switch and only support bulk delete; API tokens do not offer bulk enable, disable or delete yet. Web Services also has bulk domain and option changes, see Web Services. Sites can also be moved to another listener, see Moving sites.

Duplicating entries

Every entry in the table above except API tokens can be duplicated, and so can subscribed IP lists, backup destinations, Web Terminal credential presets, records within a DDNS task and sites within a Web Service listener. Click "Duplicate" on an entry to open the add dialog with that entry as a template; the name gets a "(copy)" suffix. Change the settings that need to differ and save to add a new entry. The original is left unchanged, and the copy is placed right after it.

• Secrets are taken from the original: saved passwords, tokens and private keys stay masked in the dialog. If you leave them unchanged, the copy uses the original's values, and the plaintext never passes through the browser. The eye button shows the original's plaintext. For Web Terminal connections and credential presets, you must accept the user agreement and pass two-factor verification before secrets are reused.
• Content maintained by the system is not copied: certificates obtained through ACME or read from files are issued or read again with the copy's settings, while an uploaded certificate is copied together with its private key. Certificate deployment records are cleared, subscribed IP lists are downloaded again, and site share links are not copied because their tokens bypass authentication.
• Certificate deploy targets are disabled in the copy so it does not write to the same files as the original certificate. Enable them after checking that the file names do not clash.
• Web Service: when duplicating a site you can place it under another listener (for example from an HTTP listener to an HTTPS one). When duplicating a listener you can choose whether to copy its sites as well.
• The copy keeps the original's enabled state. Before saving, change the ports, domains, records and other settings that must differ so the copy does not conflict with the original.

Notes for specific pages

• Dynamic DNS: "Sort records" on a task card opens a dialog for the order and groups of the DNS records in that task. Saving takes effect immediately and does not trigger a new sync. When editing a task, the same dialog is also available in the "DNS records" tab and is saved together with the task. When records have groups, the records on the card are shown by group, and each group can be collapsed on its own.
• frp: The proxy list can be filtered by frpc instance; sort mode shows all proxies and adjusts the full order.
• API Tokens: Until you sort them manually, tokens are shown by creation time, newest first. After the order has been adjusted, they are shown in the saved order, and new tokens are placed first.
• Auth users: "Sites using shared users" is shown by listener, and the sites within a listener are grouped by their groups in Web Services. Listeners and groups can each be collapsed, and the toolbar can collapse or expand all of them at once.

API

Every general list endpoint provides PUT <list path>-order (body {"keys": [...]}, which must contain all entries) to change the order and PUT <list path>-group (body {"keys": [...], "group": "..."}) to set the group in bulk, PUT <list path>-enable (body {"keys": [...], "enable": true}) to enable or disable in bulk, and POST <list path>-delete (body {"keys": [...]}) to delete in bulk, for example PUT /api/stun/rules-group and POST /api/portforward/rules-delete. Records within a DDNS task use PUT /api/ddns/tasks/{key}/records-layout, and API tokens use PUT /api/tokens/order and PUT /api/tokens/group. See the API reference for details.

Duplicating uses POST <list path>/{key}/copy. The body is the new entry, and secrets that are still the ******** placeholder take the values of entry {key}, for example POST /api/frp/clients/{key}/copy.