Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| access:index [2022/02/19 10:51] – [Guest] Figured out the current logon requirements for asking about guest creation. Andre | access:index [2026/03/22 18:23] (current) – [Sysop] Add some text from the old sysop manual (sysop_commands.html) about sysop levels, multiple sysops per BBS digital man | ||
|---|---|---|---|
| Line 95: | Line 95: | ||
| real name or a handle instead. Synchronet automatically treats the alias of | real name or a handle instead. Synchronet automatically treats the alias of | ||
| Sysop specially and forwards any mail received for " | Sysop specially and forwards any mail received for " | ||
| + | |||
| + | There is usually one sysop (System Operator) per BBS - the owner and operator | ||
| + | of the hardware which Synchronet is running on and accepting remote users. | ||
| + | Quite often systems require more than one sysop and Synchronet is flexible in | ||
| + | this respect. Within Synchronet, a sysop is defined as any user with a security | ||
| + | level of 90 or above. Any user that qualifies as a sysop, will be prompted to enter | ||
| + | the //system password// during login and/or when invoking a sysop function. Users with | ||
| + | sysop access can cause serious damage to the system, so give out this ability with | ||
| + | caution. | ||
| + | |||
| + | === Multiple Sysops === | ||
| + | As stated above, any user with a security level of 90 or greater can perform | ||
| + | sysop functions, "So why have levels 91-99?" | ||
| + | can still restrict a user with sysop access from accessing BBS functions areas (e.g. Message Groups or | ||
| + | Sub-boards or File Libraries or Directories) by setting the minimum required | ||
| + | security level above that user's level. For example: If you have a sysop with a | ||
| + | security level of 90, you can still have a Message Group or Sub-board with a | ||
| + | minimum required level of 91. Now this sysop will not be able to access | ||
| + | that Group or Sub-board. While it is true that sysops can edit their own | ||
| + | and subordinate user's accounts, they can not edit a sysop of higher level' | ||
| + | account (when calling remotely). A sysop can't raise any user's level | ||
| + | above their own, or add flags or exemptions that they themselves don't already have. | ||
| + | |||
| ==== Guest ==== | ==== Guest ==== | ||
