| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| access:requirements [2018/03/01 12:10] – Links to util:binkit changed to module:binkit digital man | access:requirements [2018/03/01 12:21] – old revision restored digital man |
|---|
| ===== Overview ===== | ===== Overview ===== |
| |
| You will find in [[module:binkit]] and other Synchronet [[:config:|configuration]] files, places where the sysop may specify requirements to access a specific area or feature of the BBS. Usually these items will have ARS (Access Requirement String) or just "Requirements" as part of the name. | You will find in [[util:SCFG]] and other Synchronet [[:config:|configuration]] files, places where the sysop may specify requirements to access a specific area or feature of the BBS. Usually these items will have ARS (Access Requirement String) or just "Requirements" as part of the name. |
| |
| Most ''Access Requirements'' are "default allow", meaning, if there are no requirements specified (i.e. the requirement string is blank), then the default behavior is **allow** access to that specific area/function to //any// user. | Most ''Access Requirements'' are "default allow", meaning, if there are no requirements specified (i.e. the requirement string is blank), then the default behavior is **allow** access to that specific area/function to //any// user. |
| ===== Configuration ===== | ===== Configuration ===== |
| |
| [[module:binkit]] has an interactive ''Requirements'' dialog screen which allows easy addition or clearing of the most common requirement parameters. | [[util:SCFG]] has an interactive ''Requirements'' dialog screen which allows easy addition or clearing of the most common requirement parameters. |
| |
| <code> | <code> |
