Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| access:index [2021/01/18 20:23] – [Creating and Editing User Accounts] Add link to makeguest module digital man | 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 74: | Line 74: | ||
| There are multiple methods available for creating and editing user accounts: | There are multiple methods available for creating and editing user accounts: | ||
| + | * By calling or connecting to the BBS and selecting " | ||
| * [[module: | * [[module: | ||
| * [[module: | * [[module: | ||
| Line 82: | Line 83: | ||
| * " | * " | ||
| * e.g. ''; | * e.g. ''; | ||
| + | |||
| + | ==== Sysop ==== | ||
| + | |||
| + | The first user account created when connected to the [[server: | ||
| + | |||
| + | For this reason, the System Password is prompted for (with the SY: prompt) | ||
| + | during the first new user creation process. | ||
| + | |||
| + | The sysop account is traditionally the first user record in the database | ||
| + | (i.e., user #1). This user account should not have the alias of " | ||
| + | real name or a handle instead. Synchronet automatically treats the alias of | ||
| + | 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. | ||
| Line 93: | Line 128: | ||
| === Guest Account Creation === | === Guest Account Creation === | ||
| - | By default, if no '' | + | When a sysop with [[access:level|Security Level]] 99 logs into the [[server: |
| + | |||
| + | * Sysop' | ||
| + | * '' | ||
| + | * Sysop has not already been asked and said '' | ||
| + | |||
| + | If the sysop answers '' | ||
| * [[Restrictions]]: | * [[Restrictions]]: | ||
| * [[Exemptions]]: | * [[Exemptions]]: | ||
| + | |||
| + | If you answered '' | ||
| ===== See Also ===== | ===== See Also ===== | ||