Sysop Commands

5.0 Sysop Commands (Remote / Local)

Sysop work happens in two places:

• Local — on the BBS host via SCFG, Control Panel, and exec/ utilities (uedit, allusers, node, EchoCfg, etc.).
• Remote / online — while logged into the Terminal Server as a sysop-level user, using ; string commands and the ! sysop menu in the Classic shell.

Both paths honor the same security model: level, flags, exemptions, and restrictions on the user record.

Wiki: https://wiki.synchro.net/access:index · https://wiki.synchro.net/module:str_cmds · https://wiki.synchro.net/util:SCFG

5.1 Sysop Definition (security level 90 and above)

In Synchronet, security levels 90–99 are reserved for operators of the system (sysops / co-sysops). That level band is what most documentation means by “sysop,” though fine-grained power also depends on:

• Flags (four sets A–Z) you invent for area access
• Exemptions (A–Z) that lift specific limits (time, anonymous, etc. — predefined meanings)
• Restrictions (A–Z) that deny specific features
• ARS strings on menus, subs, directories, and doors

A user at level 90+ typically can:

• Open the online sysop menus (! in Classic shell)
• Run ;UEDIT and other sysop string commands (subject to remote-sysop limits)
• Meet default “Operator Requirements” style ARS checks when those require sysop level

Exact command availability still filters through exemptions and the string-command module logic — higher level alone is not a blanket root shell.

Remote sysop ceilings

When editing users online, a remote sysop:

• Cannot raise another user’s level above their own
• Cannot grant flags or exemptions they do not themselves have
• Cannot edit a user with a higher security level (sensitive fields stay hidden)

That prevents a co-sysop from promoting themselves past the primary sysop via the BBS UI.

Wiki: https://wiki.synchro.net/access:index · https://wiki.synchro.net/access:user_editor

5.2 Multiple Sysops

Multiple operator accounts are normal:

1. Create additional user records (or promote trusted users).
2. Set level into the 90–99 band as appropriate for their role.
3. Grant only the flags/exemptions they need (least privilege).
4. Use ARS on dangerous external programs (SCFG, shell doors) so only specific ops can launch them.
5. Prefer local scfg / OS access for the primary sysop; give co-sysops online tools for daily moderation.

Document who owns network links (QWK/Fido passwords), DNS, and the OS account — those are outside the BBS user file but part of “being a sysop.”

Wiki: https://wiki.synchro.net/access:index

5.3 Local configuration (SCFG)

SCFG (Synchronet Configuration Utility) edits the primary configuration INI files under ctrl/. It is the main local (or operator-door) UI for system structure.

How to invoke

• Windows Control Panel: BBS → Configure
• Command line: scfg from exec (or full path if exec is not on PATH)
• In-BBS: Operator External Programs → “Synchronet Configuration (ANSI)” or “(dumb)”

Native binary: exec/scfg.exe (Windows) or exec/scfg (Unix).

Useful command-line options

From scfg -? / scfg --help (summary — check live help for your build):

What you configure in SCFG (map)

• System information and toggle options
• New user values and passwords
• Nodes
• Message groups and sub-boards
• File libraries and directories
• External program sections and editors
• Network configuration (Internet e-mail policy, QWK hubs, FidoNet, MQTT)
• Text-file sections
• Chat features
• Server-related menus (where exposed)

After sensitive changes, recycle affected sbbs threads or restart so listeners and caches pick up new data.

Wiki: https://wiki.synchro.net/util:SCFG

5.4 Online Sysop Commands (str_cmds)

Stock string commands live in the JavaScript module str_cmds.js under exec/ (override via mods/ if needed). The Classic command shell loads them; other shells may expose different subsets.

Usage conventions

• Commands are preceded by ; and end with Enter
• <> required parameter, [] optional, () required exemption in the docs
• Inline help: ;HELP
• Sysop menu: ! from main/transfer in Classic shell; ? often shows additional ops commands in context

Commands available to (many) users

Examples from the module documentation:

Sysop-oriented groups

The wiki tables split sysop commands into areas such as:

• User & mail management — e.g. ;UEDIT, mail-related ops
• Message base / moderation — delete, edit, close, etc. (see also Sysop Bible / moderation howto)
• File area maintenance
• Node / chat / system control
• External / miscellaneous

Exact letters and parameters change with Synchronet revisions — treat ;HELP and the wiki command tables as authoritative for your version, not memory from another BBS package.

Safety habits

• Prefer local backups before bulk online deletes.
• Remember remote-sysop ceilings when using ;UEDIT.
• Do not grant the exemptions that unlock destructive commands to casual co-sysops.
• For bulk security changes, use allusers offline instead of dozens of manual ;UEDIT sessions.

Wiki: https://wiki.synchro.net/module:str_cmds

Quick comparison

Wiki: https://wiki.synchro.net/access:index · https://wiki.synchro.net/util:SCFG · https://wiki.synchro.net/module:str_cmds · https://wiki.synchro.net/access:user_editor