Optional ISP module¶
The ISP module can be considered an extension to the billing module. It handles the management and tracking of items specific to running an Internet service provider.
The main part of this module is the user account. It is attached to the service group which defines many of the features of the accounts. In this entity we track the following fields.
The User ID is generated by the system. It is used to connect various services and features to the user. It is also the UID of the user in the Unix file system when required.
This is a unique name in the system. When the group does not have a virtual domain this becomes the only way to log in. If not filled in it defaults to the UID.
Group Edit Privs¶
If this flag is set then the user is considered the group leader and can perform operations for the other users in the group such as password changes.
This is the name that the user is presented to the world as. In Unix systems this is the GCOS field.
While email will generally be supplied by the enterprise, the user has the option here to have all of the mail to this account forwarded.
If the user is part of a group with one or more domains then this field becomes their user name within their domains. For example, if their domain is example.com and you enter user into this field then their email address is email@example.com. This address can be used to log into various places in the system such as the control panel and email as an alternative to their login name.
Like client and group records, ad-hoc notes can be entered for accounts. They will be listed below the edit screen. The system will also add events such as when details in the record are modified.
Domains, like user accounts, can be attached to service groups. A single group can have any number of domains attached or none at all. If any domains are attached, and the appropriate account type is selected, then all of the accounts in the group are considered part of those domains. There are three fields related to domains.
The domain name without any sub-domain information such as “www”.
This is when the domain is due to expire. This is a display only field as the actual expiry is filled in from external sources.
This is the number of years that the client should be billed for when the domain is up for renewal. A value of zero means “do not renew” and indicates that the client is abandoning the domain at the end of the current year.
As was mentioned above, domain expiry is filled in from external sources. The domain names are checked as well and if there is a domain that is not in the database it will be added anyway to a special service group for orphaned domains.
Features are used to describe anything that might be attached to a user such as white lists, vacation messages, phone service, etc. Features are defined by admins but by themselves they don’t do much. They require that processes be set up to apply them. VybeBooks includes many scripts for this purpose already but specialized ones can be added.
Once a feature has been set up, users can select them and fill in details. The details to be filled in vary by the feature. A help message can be added to a feature when setting it up.
As mentioned above, the username on a user account is used as the email address within a domain. There can also be ad hoc aliases added. These act the same as the username alias but without the special handling. An alias can point to one or more email addresses. These addresses can be within the system or outside. addresses can be separated by commas, whitespace or both. Their are a few ways to specify an address:
user - Refers to a login on the host system.
user@ - refers to the username within the groups’ domains
firstname.lastname@example.org - any valid address on the Internet.