This is the base monthly fee in dollars that an account must pay to continue to use a tool given the amount of storage and/or transactions to be secured through such payment. This fee amount is usually set by the plan the customer chooses, but management may edit it.

The name of the company, organization, or government agency managing the account. An account typically pays for access to its data and then allocates access to its data to its users.

If this is the name of an individual, that is the rare case of an individual whose name is used for the account. Most individuals are listed as users.

The Status of an account reflects whether the account is active or not and why. The Status picklist values are:

Active - Billable: This is the most common status. It indicates an account properly paying its monthly fees.

Active - Demo:  This is also a common status for entry into usage of a tool. All tools provide a way to try out the tool for a period, typically a month, before Access Meister (AcM) tries to convert such demos into billable accounts.

Active - KISS: This is a simple version of the tool where features are crippled, but there is no monhly fee. Unlike a demo version of the tool, a KISS version doesn't expire and convert to a billable account. The hope is that the user will see the grayed-out, inactive features, and eventually wish access to them and will switch to a billable status.

Active - Payment Error: When AcM tries to bill an account, but encounters a billing problem, such as an expired credit card, AcM converts a Status like Active - Billable to Active - Payment Error. After the primary sysadmin gets email about the billing problem, the account users continue to enjoy access, but a counter begins to count down to the date when access is cut, typically one month after the payment error.

Cancelled by Customer: Customers are free to cancel their account for whatever reason they choose. When they do so, this is the status assigned to the account. It cuts account access to the tool.

Cancelled by Mgmt: Webteam management is free to cancel a tool account for any reason, but the most common is automatically by AcM after a status of Active - Payment Error goes beyond its one-month grace period.

Awaiting Cleanup: Beyond the first 4 active statuses and the 2 cancelled statuses is this status which is technically active in that account users still have access. This status is a temporary condition and rarely used. It identifies an account as part of a group being processed in batch, typically to clean up defective or corrupted data.

This is the amount due or owed by the account. It is the sum of the currently due monthly fee plus any past-due monthly fees. It also includes any manually entered fees and credits.

For an itemized list of charges, credits, and payments, see the transactions listed on the billing record of the account.

The amount paid on the corresponding line, typically billed to the credit card attached to the account.

The balance is calculated as the difference between a total of all the amounts due, less a total of all the amounts paid.

On a statement, the balance is a running amount in that the previous line's balance has either added to it the above line's amount due or subtracted the above line's amount paid.

Note that if a customer pays ahead for some reason, the balance will be a negative number. That means each month's fee will produce an amount due that reduces such an amount paid ahead until the balance becomes a positive number, at which point the account's credit card will begin to be billed.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

As with old world memos and today's email, cc stands for carbon copy and indicates that you wish a copy of the note to be sent to the picklist values you select.

The picklist values begin with "eVarman" if the account has been posted to the contact management module of the eVarman software. Use this to post information that may be relevant for a salesperson contacting the account, for example, "Usage rates indicate it may be time for client to upgrade to a corporate account".

The next group of picklist values are the Access Meister (AcM) system managers, the users with access to all information about all AcM accounts.

The last group of picklist values are the users listed under the account.

When an individual is selected from the cc picklist, system manager or account user, they receive an email with the note text, along with information about where the note came from and a link to click on the source billing record. Because of this, it is not necessary to provide a great deal of background information to a cc'd individual.

This is the 16-digit number on the front of the credit card.

If we ever accept American Express, theirs has 15 digits.

This is the date a comment note was added.

The date the transaction occured, either posted automatically by Access Meister or manually by management.

This was the date an account was first opened to use the tool in the picklist to the right of the "Billing Record" label.

Note that the account may have opened the use of other tools on other dates.

This is the expiration date of the credit card.

It is in the form mm/yyyy where mm is the 2-digit number of the month (includes the beginning 0), and the yyyy is the complete 4-digit year (not just the last 2-digits).

For credit cards that show a day of the month, we need only the month and year.

This is the date the account was or will be billed for the first time. Most payment plans set this as 30 days from their signup date in order to give the customer some free testing time with a tool.

Management may extend the First Billing years into the future to give customers free usage of the tool, perhaps because it's part of a program paid in other ways. For obvious financial reasons, this should be granted for an important reason only.

L# is short for line number. It is the line or row number in a table. Use it to refer to a particular line when discussing a table.

This is the date the account was last billed.

The Last Login field begins by showing the date any user logged in to the designated tool of the account. After that, the field shows the name and username of the user who logged in on that date. An example would be, "Jul 11, 2009 by Peter Shikli [petershikli]".

This shows the total amount of storage in MB being used by the account for the designated tool. This is a sum of all file sizes, such as attachments and images

This is the maximum amount of hard drive storage in MB that the account may use as part of the fee they pay. This is usually set by their payment plan, but may be edited by management.

This is a comment note about a financial transaction line added by a manager, as opposed to entries to System Note, which are automatically added by Access Meister.

Try to add your comment notes to the notes section at the bottom of the billing record instead of to each transaction line with the Memo field. The notes section is where such things should collect and where people look for them. Use a line's Memo field only for a very brief (couple words) summary tightly related to that line.

This is the individual's name as it appears on the credit card.

We suggest not adding a middle initial to the first name, as "John J." for John J. Smith, or a title after the last name, as "Smith, jr" for John Smith jr, even when those things are part of the name as it appears on the credit card. The reason is that credit card banks are looking for an exact match to a name, and minor problems such as a missing period after a middle initial, could mismatch the name. For this reason, the credit card banks often enter the name as only a first and last name. Try just the first and last name to start, and try the other things only if that doesn't work.

This is the date the account is scheduled to be billed next. It is blank for inactive accounts.

This is the text of the comment note.

A pricing plan is a collection of software features with a given name and matched to a monthly fee, such as a maximum data storage that is part of a "Basic Pricing Plan", for example.

Click the "Pricing Plans" button on the main menu bar for tables listing the pricing plans for our tools and for how these plans are established and maintained.

The email address of the account's primary systems adminstrator. The email is clickable if you wish to email the sysadmin.

The login information of the account's primary systems adminstrator starting with the text "user:", then the username, then the text "pass:" and then the password.

To the right of that is the command text, "Login As". Clicking on that allows you to log into the designated tool of the designated account as the primary sysadmin. This allows you to see what he sees, to diagnose problems, to give tutorials looking at the client's real data, and such functions pretending to be the primary sysadmin. Note that the effect on your cookies may cause you to have to login again as yourself to go back to using Webteam tools under your regular username.

The first and last name of the account's primary systems administrator.

The area code and telephone number of the account's primary systems adminstrator.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

This field states any usage restrictions placed on the payment plan originally selected for the account.

The System Note is a comment entered about an unusual event related to the transaction line automatically by Access Meister, for example, noting an error when an attempt was made to secure payment against the account's credit card.

This specifies the maximum number of transactions per month that the account may request of a tool such as Address Meister.

The name or short description of the transaction.

This is the type of credit card we accept.

For now it is either Mastercard or VISA. Maybe in the future it will include American Express, but for now, their credit card fees are too high.

This is calculated as the total amount of year-to-date (YTD) billing that Access Meister (AcM) has tried to collect from the account for all the tools listed on the account. Note that this doesn't mean we collected all that was billed.

YTD means AcM totals all billing attempts between today's date and this date last year.

This is calculated as the total amount of year-to-date (YTD) billing that Access Meister (AcM) has tried to collect from the account just for the tool listed. This doesn't mean we have successfully collected all amounts billed.

YTD means AcM totals all billing attempts between today's date and this date last year.

The Status Edit form is where you change the Status field of an account.

We could have made this a simple picklist, but the pop-up form is designed to encourage adding a comment note whenever this is done. The reason is that a status change is an important change to an account, often making it inactive and no longer accessible to its users. If we get a call regarding that from a customer, we'll usually need a few words in the billing notes to answer them about who made the status change and why.

Using this table, you can change the primary sysadmin responsible for billing for the designated tool for this account. To do so, select a different account user with a radio button and press save.

Note that you cannot edit the particulars about the primary sysadmin, for example, his email address. You must do that the same way you change the particulars about any user, by clicking the edit pencil to the right of the several places they are listed as individual users.

On this form, you can edit the fields on an account related to their billing, and then add a comment note about why you made the change.

Remember that you can change all the fields at once by going back to the billing record and pressing the Change Account Plan button.

As anywhere in Access Meister, you may get help on any field by mousing over its name or clicking on its name.

This pop-up gives you the ability to select a different payment plan for the account, thereby changing all at once the fields Plan Name through Trans/mo Limit on the account's billing record. To make such a change, click the radio button of the desired payment plan name and click the Save button near the bottom.

You may edit those fields manually, but changing them through the Change Account Plan is not only faster, but it changes the fields to values the customer expects from the marketing website of the tool where the payment plans are described.

The most common reason to change a payment plan is when customers exceed their existing storage needs and wish to pay a higher fee for more storage. It is also possible as part of an economy imperative that customers delete information to reduce storage in order to downgrade a payment plan and its fee.

This is the pop-up where you can make quick changes to the credit card used to pay for the account's monthly fees.

Note that you must re-enter the credit card number even if you are only changing its expiration date. This is a security precaution to make sure only the credit card holder is making changes here.

Access Meister (AcM) normally bills customers their monthly fees and collects from their credit cards automatically. Sometimes, we need to adjust their bill manually. This is the form used to do that.

This is how you add a custom transaction line to an account, either to add an additional fee that they owe or some credit for an amount they paid. Note that a discount we grant is treated the same as an amount the customer paid.

Examples of such custom billing transactions include:

• We discover a billing error where the customer has been using the tool without paying. We negotiate an amount they owe, and we add that amount to their bill using this form.
   
• We discover a billing error where we have been double charging the customer. We add up such extra charges and enter a custom billing transaction with a negative amount to give the customer back the amount we overcharged.
   
• The customer requests a change to the tool's software on the basis that we will bell them for the programming. When complete, we add that charge to their bill.
   
• The customer takes a lot of our time to solve a tech support problem that turns out to be on their end. We decide to bill them per our policies using a custom billing transaction.
   
• The customer mails us a paper check. We enter that with a negative amount to show a credit to their account.
   
• The customer refers someone to become a billable Webteam customer. We add a transaction with a negative amount to show the credit to their account of a referral fee.

Just as each tool has a SecLev identifying the level of access available to a user, so too Access Meister (AcM) has its own SecLev granting a user different levels of access to features and data within AcM.

To understand what each SecLev value means and what access it provides, see the Security Access Table by the More Info label.

The name of the company, organization, or government agency managing the account. An account typically pays for access to its data and then allocates access to its data to its users.

If this is the name of an individual, that is the rare case of an individual whose name is used for the account. Most individuals are listed as users.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

This is the mailing city of the user.

This is the mailing country of the user, usually USA.

This is the date a comment note was added.

This is the user's email address.

Often, you can click on it to bring up your regular email software with an email message already addressed to them and ready for you to type into the message body.

This is the name of the person, the individual user, by first name and then family name.

The date the user last logged in.

This is an indication of how actively a user is making use of the tool.

This is the text of the comment note.

This is the password needed after entering a username to gain access to a tool.

The initial default is the same as the username, usually the first initial and last name of a user, lower case and without a space, but the user may change this. Changing it regularly is a good idea.

Although we do not enforce password size or its format, we recommend at least 6 characters to include letters mixed with numbers, as well as symbols such as @$%. Don't use other symbols, and use all lower case letters. The reason is that it is too easy to forget what is capitalized.

A cool trick is to think of a word and then replace letters with symbols and numbers as below:
a - replace with @
b - replace with the number 8, which looks like the capital B
e - replace with a 3, which is like a backward E
i - replace with the number 1
o - replace with the number 0
p - replace with the number 9, which is like a backward P

This is the date the password was last changed.

Access Meister automatically tracks this so that we may one day automatically send out email encouraging users to change their password periodically. Until then, it simply encourages the practice by reminding users how long it's been.

This is the telephone number of the user, preceded by the area code.

This is the postal mailing address of the user in case we wish to send them a letter, which we may do if their email bounces.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

Within each Webteam tool or application, different users get different levels of security access, controlled by what SecLev they are assigned.

Each tool begins with a user with a SecLev of Primary Sysadmin, which is the person who first opens the tool subscription and is responsible for its billing, even if it's free. This person has unlimited access rights within that tool for the corresponding account or sub-account. No one can delete the Primary Sysadmin, although it can be edited to be a different user.

Almost all tools also have any number of users with a SecLev of a regular sysadmin. Such a sysadmin has all rights within the tool except billing and they may be deleted.

Below that, each tool starts to differ regarding the values it has for SecLev, which is always a picklist of values, not free text. These SecLev values differ based on the needs of users peculiar to the tool. KB Meister, for example, has a SecLev of Librarian, which confers certain access rights to manage an online knowledge base. Task Meister has no such online knowledge base, hence doesn't need a SecLev of Librarian. Task Meister, however, does have a SecLev of Contractor restricting contractors to edit only their own tasks within boundaries, a SecLev that KB Meister doesn't need or have.

Administered within each tool, we adhere to the concept of access groups in terms of assigning SecLev access values. That means we collect families of access rights, for example, to view certain data or issue certain commands, into long lists of detailed rights that are designated under a given SecLev value. That means new tool users are not given rights to do different things within the tool. Instead, they are assigned membership to an access group, another name for a SecLev, that automatically assigns or restricts rights based on how that SecLev was previously defined.

This is the mailing state of the user, if he resides in the US.

For Canada, it is the province. For other countries, it is whatever they have.

This denotes whether the user has been granted general entry into the tool of a (sub)account.

It can be "Not Assigned" to indicate that the user has yet to ever be allowed entry. It can be "Active", which means access is granted, but subject to whatever restrictions are in place within the tool based on the user's SecLev. "Inactive" means the user was once allowed entry, but no longer.

This shows if an account name is really a sub-account, in which case the "Sub of" column shows which account it is a sub-account of.

This user status can have one of the two values of active or inactive. We may add more status values if it becomes worthwhile.

A quick way to deny users all access to all tools and (sub)accounts is to change their status to inactive.

A username is a unique identifier Access Meister (AcM) needs to identify each individual granted access to any tool or application AcM manages.

When the record of an individual user is first entered into AcM, he/she is asked to select a username. We suggest the user's first initial followed by their last name, all lower case. We suggest lower case because most Windows users do not realize that lower case and upper case letters are considered different, for example, a jsmith username will not match JSmith.  We also do not allow spaces in a username, though we do allow certain special characters such as @ and &.

If a requested username already exists in AcM, the user requesting is advised, and they can try again, perhaps with variants such as jsmith1 after AcM tells them that jsmith is already taken.

Once a username is selected, it cannot be changed, as can the password that is used with a username to gain access.

This is the mailing ZIP code of the user, if he resides in the USA.

For other countries, it's their postal code.

Access to a tool is granted in two steps.

First, we determine if a user has any access at all, that is, are they an active user or not. If they are active, then we check their SecLev which determines what access rights they have once in the tool. See the "More Info" below for a SecLev definition.

Access Meister (AcM) determines whether a user is active or not in the same way for all tools, but each tool assigns a SecLev value that differs between tools and what that SecLev value allows the user to see and do within the corresponding tool.

The Account Access Edit form begins with a picklist you can use to change the SecLev for the tool in question. A user can have different SecLev values for different tools, but only one SecLev value for each tool, regardless of the account or its sub-account.

The best way to look at the radio button options for each account and sub-account is to follow the following sequence through which a user gains access and then loses it.

1. To begin, all users are described by the "Not Assigned" radio button. You won't see this for the main parent account because that changes to "Active" as soon as an access table is generated. You will see it for any sub-accounts on the table until a user is switched to "Active"
    
2. Once a user's "Active" radio button is selected for a sub-account, that user has the same access there as in the parent account. This is what users need for their SecLev to kick in and determine what they can do now that they have been allowed in the door by being "Active".
    
3. If a user's involvement ends in a sub-account, perhaps because a project finishes, that user may be better off with the "Not Active" radio button selected. This cuts that user's access to use the tool in that sub-account, but his data within that sub-account remains. Tasks he completed in Task Meister, for example, remain in that sub-account's Task Meister for historical records, but he can no longer look at those tasks or edit them. "Not Active" users can be made "Active" by simply pressing the radio button in this table, and they return to work in the sub-account's tool where they left off.
    
4. Finally, let's assume the user turned out to have little to no involvement with the sub-account, and there remains no reason to keep his data, if any, in the sub-account's tool. In this case, the "Remove" radio button breaks the connection between the user and the sub-account's tool.  Such a user's data will be deleted or connected to a different user depending on the policy on removed users within that tool. Note that the user is removed from the tool, but the user is not deleted from Access Meister. Users removed from a parent account are automatically removed from all sub-accounts of that account.

Just as each tool has a SecLev identifying the level of access available to a user, so too Access Meister (AcM) has its own SecLev granting a user different levels of access to features and data within AcM.

To understand what each SecLev value means and what access it provides, see the Security Access Table by the More Info label.

This is the status of the user regarding Access Meister (AcM). It can be either "Active" or "Not Active". This is a simple yes/no switch allowing access or not.

This is unrelated to the user's SecLev, which determines what he can do in AcM once this status setting allows him in.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

This is the mailing city of the user.

This is the mailing country of the user, usually USA.

This is the date a comment note was added.

This is the user's email address.

Often, you can click on it to bring up your regular email software with an email message already addressed to them and ready for you to type into the message body.

This is the individual's given name, like John or Zoltan, even though on lists and in a few cultures, this is shown after the family name.

This is the individual's family name, like Smith or Horvath, even though on lists and in a few cultures, this is shown before the given name.

This is the text of the comment note.

This is the password needed after entering a username to gain access to a tool.

The initial default is the same as the username, usually the first initial and last name of a user, lower case and without a space, but the user may change this. Changing it regularly is a good idea.

Although we do not enforce password size or its format, we recommend at least 6 characters to include letters mixed with numbers, as well as symbols such as @$%. Don't use other symbols, and use all lower case letters. The reason is that it is too easy to forget what is capitalized.

A cool trick is to think of a word and then replace letters with symbols and numbers as below:
a - replace with @
b - replace with the number 8, which looks like the capital B
e - replace with a 3, which is like a backward E
i - replace with the number 1
o - replace with the number 0
p - replace with the number 9, which is like a backward P

This is the telephone number of the user, preceded by the area code.

This is the postal mailing address of the user in case we wish to send them a letter, which we may do if their email bounces.

This is the user's primary account.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

This is the mailing state of the user, if he resides in the US.

For Canada, it is the province. For other countries, it is whatever they have.

A username is a unique identifier Access Meister (AcM) needs to identify each individual granted access to any tool or application AcM manages.

When the record of an individual user is first entered into AcM, he/she is asked to select a username. We suggest the user's first initial followed by their last name, all lower case. We suggest lower case because most Windows users do not realize that lower case and upper case letters are considered different, for example, a jsmith username will not match JSmith.  We also do not allow spaces in a username, though we do allow certain special characters such as @ and &.

If a requested username already exists in AcM, the user requesting is advised, and they can try again, perhaps with variants such as jsmith1 after AcM tells them that jsmith is already taken.

Once a username is selected, it cannot be changed, as can the password that is used with a username to gain access.

This is the mailing ZIP code of the user, if he resides in the USA.

For other countries, it's their postal code.

Just as each tool has a SecLev identifying the level of access available to a user, so too Access Meister (AcM) has its own SecLev granting a user different levels of access to features and data within AcM.

To understand what each SecLev value means and what access it provides, see the Security Access Table by the More Info label.

The name of the company, organization, or government agency managing the account. An account typically pays for access to its data and then allocates access to its data to its users.

If this is the name of an individual, that is the rare case of an individual whose name is used for the account. Most individuals are listed as users.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

This is the mailing city of the user.

This is the mailing country of the user, usually USA.

This is the date a comment note was added.

This is the user's email address.

Often, you can click on it to bring up your regular email software with an email message already addressed to them and ready for you to type into the message body.

This is the name of the person, the individual user, by first name and then family name.

The date the user last logged in.

This is an indication of how actively a user is making use of the tool.

This is the text of the comment note.

This is the password needed after entering a username to gain access to a tool.

The initial default is the same as the username, usually the first initial and last name of a user, lower case and without a space, but the user may change this. Changing it regularly is a good idea.

Although we do not enforce password size or its format, we recommend at least 6 characters to include letters mixed with numbers, as well as symbols such as @$%. Don't use other symbols, and use all lower case letters. The reason is that it is too easy to forget what is capitalized.

A cool trick is to think of a word and then replace letters with symbols and numbers as below:
a - replace with @
b - replace with the number 8, which looks like the capital B
e - replace with a 3, which is like a backward E
i - replace with the number 1
o - replace with the number 0
p - replace with the number 9, which is like a backward P

This is the date the password was last changed.

Access Meister automatically tracks this so that we may one day automatically send out email encouraging users to change their password periodically. Until then, it simply encourages the practice by reminding users how long it's been.

This is the telephone number of the user, preceded by the area code.

This is the postal mailing address of the user in case we wish to send them a letter, which we may do if their email bounces.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

Within each Webteam tool or application, different users get different levels of security access, controlled by what SecLev they are assigned.

Each tool begins with a user with a SecLev of Primary Sysadmin, which is the person who first opens the tool subscription and is responsible for its billing, even if it's free. This person has unlimited access rights within that tool for the corresponding account or sub-account. No one can delete the Primary Sysadmin, although it can be edited to be a different user.

Almost all tools also have any number of users with a SecLev of a regular sysadmin. Such a sysadmin has all rights within the tool except billing and they may be deleted.

Below that, each tool starts to differ regarding the values it has for SecLev, which is always a picklist of values, not free text. These SecLev values differ based on the needs of users peculiar to the tool. KB Meister, for example, has a SecLev of Librarian, which confers certain access rights to manage an online knowledge base. Task Meister has no such online knowledge base, hence doesn't need a SecLev of Librarian. Task Meister, however, does have a SecLev of Contractor restricting contractors to edit only their own tasks within boundaries, a SecLev that KB Meister doesn't need or have.

Administered within each tool, we adhere to the concept of access groups in terms of assigning SecLev access values. That means we collect families of access rights, for example, to view certain data or issue certain commands, into long lists of detailed rights that are designated under a given SecLev value. That means new tool users are not given rights to do different things within the tool. Instead, they are assigned membership to an access group, another name for a SecLev, that automatically assigns or restricts rights based on how that SecLev was previously defined.

This is the mailing state of the user, if he resides in the US.

For Canada, it is the province. For other countries, it is whatever they have.

This denotes whether the user has been granted general entry into the tool of a (sub)account.

It can be "Not Assigned" to indicate that the user has yet to ever be allowed entry. It can be "Active", which means access is granted, but subject to whatever restrictions are in place within the tool based on the user's SecLev. "Inactive" means the user was once allowed entry, but no longer.

This shows if an account name is really a sub-account, in which case the "Sub of" column shows which account it is a sub-account of.

This user status can have one of the two values of active or inactive. We may add more status values if it becomes worthwhile.

A quick way to deny users all access to all tools and (sub)accounts is to change their status to inactive.

A username is a unique identifier Access Meister (AcM) needs to identify each individual granted access to any tool or application AcM manages.

When the record of an individual user is first entered into AcM, he/she is asked to select a username. We suggest the user's first initial followed by their last name, all lower case. We suggest lower case because most Windows users do not realize that lower case and upper case letters are considered different, for example, a jsmith username will not match JSmith.  We also do not allow spaces in a username, though we do allow certain special characters such as @ and &.

If a requested username already exists in AcM, the user requesting is advised, and they can try again, perhaps with variants such as jsmith1 after AcM tells them that jsmith is already taken.

Once a username is selected, it cannot be changed, as can the password that is used with a username to gain access.

This is the mailing ZIP code of the user, if he resides in the USA.

For other countries, it's their postal code.

This is the base monthly fee in dollars that an account must pay to continue to use a tool given the amount of storage and/or transactions to be secured through such payment. This fee amount is usually set by the plan the customer chooses, but management may edit it.

The name of the company, organization, or government agency managing the account. An account typically pays for access to its data and then allocates access to its data to its users.

If this is the name of an individual, that is the rare case of an individual whose name is used for the account. Most individuals are listed as users.

The Status of an account reflects whether the account is active or not and why. The Status picklist values are:

Active - Billable: This is the most common status. It indicates an account properly paying its monthly fees.

Active - Demo:  This is also a common status for entry into usage of a tool. All tools provide a way to try out the tool for a period, typically a month, before Access Meister (AcM) tries to convert such demos into billable accounts.

Active - KISS: This is a simple version of the tool where features are crippled, but there is no monhly fee. Unlike a demo version of the tool, a KISS version doesn't expire and convert to a billable account. The hope is that the user will see the grayed-out, inactive features, and eventually wish access to them and will switch to a billable status.

Active - Payment Error: When AcM tries to bill an account, but encounters a billing problem, such as an expired credit card, AcM converts a Status like Active - Billable to Active - Payment Error. After the primary sysadmin gets email about the billing problem, the account users continue to enjoy access, but a counter begins to count down to the date when access is cut, typically one month after the payment error.

Cancelled by Customer: Customers are free to cancel their account for whatever reason they choose. When they do so, this is the status assigned to the account. It cuts account access to the tool.

Cancelled by Mgmt: Webteam management is free to cancel a tool account for any reason, but the most common is automatically by AcM after a status of Active - Payment Error goes beyond its one-month grace period.

Awaiting Cleanup: Beyond the first 4 active statuses and the 2 cancelled statuses is this status which is technically active in that account users still have access. This status is a temporary condition and rarely used. It identifies an account as part of a group being processed in batch, typically to clean up defective or corrupted data.

This is the amount due or owed by the account. It is the sum of the currently due monthly fee plus any past-due monthly fees. It also includes any manually entered fees and credits.

For an itemized list of charges, credits, and payments, see the transactions listed on the billing record of the account.

The amount paid on the corresponding line, typically billed to the credit card attached to the account.

The balance is calculated as the difference between a total of all the amounts due, less a total of all the amounts paid.

On a statement, the balance is a running amount in that the previous line's balance has either added to it the above line's amount due or subtracted the above line's amount paid.

Note that if a customer pays ahead for some reason, the balance will be a negative number. That means each month's fee will produce an amount due that reduces such an amount paid ahead until the balance becomes a positive number, at which point the account's credit card will begin to be billed.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

As with old world memos and today's email, cc stands for carbon copy and indicates that you wish a copy of the note to be sent to the picklist values you select.

The picklist values begin with "eVarman" if the account has been posted to the contact management module of the eVarman software. Use this to post information that may be relevant for a salesperson contacting the account, for example, "Usage rates indicate it may be time for client to upgrade to a corporate account".

The next group of picklist values are the Access Meister (AcM) system managers, the users with access to all information about all AcM accounts.

The last group of picklist values are the users listed under the account.

When an individual is selected from the cc picklist, system manager or account user, they receive an email with the note text, along with information about where the note came from and a link to click on the source billing record. Because of this, it is not necessary to provide a great deal of background information to a cc'd individual.

This is the 16-digit number on the front of the credit card.

If we ever accept American Express, theirs has 15 digits.

This is the date a comment note was added.

The date the transaction occured, either posted automatically by Access Meister or manually by management.

This was the date an account was first opened to use the tool in the picklist to the right of the "Billing Record" label.

Note that the account may have opened the use of other tools on other dates.

This is the expiration date of the credit card.

It is in the form mm/yyyy where mm is the 2-digit number of the month (includes the beginning 0), and the yyyy is the complete 4-digit year (not just the last 2-digits).

For credit cards that show a day of the month, we need only the month and year.

This is the date the account was or will be billed for the first time. Most payment plans set this as 30 days from their signup date in order to give the customer some free testing time with a tool.

Management may extend the First Billing years into the future to give customers free usage of the tool, perhaps because it's part of a program paid in other ways. For obvious financial reasons, this should be granted for an important reason only.

L# is short for line number. It is the line or row number in a table. Use it to refer to a particular line when discussing a table.

This is the date the account was last billed.

The Last Login field begins by showing the date any user logged in to the designated tool of the account. After that, the field shows the name and username of the user who logged in on that date. An example would be, "Jul 11, 2009 by Peter Shikli [petershikli]".

This shows the total amount of storage in MB being used by the account for the designated tool. This is a sum of all file sizes, such as attachments and images

This is the maximum amount of hard drive storage in MB that the account may use as part of the fee they pay. This is usually set by their payment plan, but may be edited by management.

This is a comment note about a financial transaction line added by a manager, as opposed to entries to System Note, which are automatically added by Access Meister.

Try to add your comment notes to the notes section at the bottom of the billing record instead of to each transaction line with the Memo field. The notes section is where such things should collect and where people look for them. Use a line's Memo field only for a very brief (couple words) summary tightly related to that line.

This is the individual's name as it appears on the credit card.

We suggest not adding a middle initial to the first name, as "John J." for John J. Smith, or a title after the last name, as "Smith, jr" for John Smith jr, even when those things are part of the name as it appears on the credit card. The reason is that credit card banks are looking for an exact match to a name, and minor problems such as a missing period after a middle initial, could mismatch the name. For this reason, the credit card banks often enter the name as only a first and last name. Try just the first and last name to start, and try the other things only if that doesn't work.

This is the date the account is scheduled to be billed next. It is blank for inactive accounts.

This is the text of the comment note.

A pricing plan is a collection of software features with a given name and matched to a monthly fee, such as a maximum data storage that is part of a "Basic Pricing Plan", for example.

Click the "Pricing Plans" button on the main menu bar for tables listing the pricing plans for our tools and for how these plans are established and maintained.

The email address of the account's primary systems adminstrator. The email is clickable if you wish to email the sysadmin.

The login information of the account's primary systems adminstrator starting with the text "user:", then the username, then the text "pass:" and then the password.

To the right of that is the command text, "Login As". Clicking on that allows you to log into the designated tool of the designated account as the primary sysadmin. This allows you to see what he sees, to diagnose problems, to give tutorials looking at the client's real data, and such functions pretending to be the primary sysadmin. Note that the effect on your cookies may cause you to have to login again as yourself to go back to using Webteam tools under your regular username.

The first and last name of the account's primary systems administrator.

The area code and telephone number of the account's primary systems adminstrator.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

This field states any usage restrictions placed on the payment plan originally selected for the account.

The System Note is a comment entered about an unusual event related to the transaction line automatically by Access Meister, for example, noting an error when an attempt was made to secure payment against the account's credit card.

This specifies the maximum number of transactions per month that the account may request of a tool such as Address Meister.

The name or short description of the transaction.

This is the type of credit card we accept.

For now it is either Mastercard or VISA. Maybe in the future it will include American Express, but for now, their credit card fees are too high.

This is calculated as the total amount of year-to-date (YTD) billing that Access Meister (AcM) has tried to collect from the account for all the tools listed on the account. Note that this doesn't mean we collected all that was billed.

YTD means AcM totals all billing attempts between today's date and this date last year.

This is calculated as the total amount of year-to-date (YTD) billing that Access Meister (AcM) has tried to collect from the account just for the tool listed. This doesn't mean we have successfully collected all amounts billed.

YTD means AcM totals all billing attempts between today's date and this date last year.

The Status Edit form is where you change the Status field of an account.

We could have made this a simple picklist, but the pop-up form is designed to encourage adding a comment note whenever this is done. The reason is that a status change is an important change to an account, often making it inactive and no longer accessible to its users. If we get a call regarding that from a customer, we'll usually need a few words in the billing notes to answer them about who made the status change and why.

Using this table, you can change the primary sysadmin responsible for billing for the designated tool for this account. To do so, select a different account user with a radio button and press save.

Note that you cannot edit the particulars about the primary sysadmin, for example, his email address. You must do that the same way you change the particulars about any user, by clicking the edit pencil to the right of the several places they are listed as individual users.

On this form, you can edit the fields on an account related to their billing, and then add a comment note about why you made the change.

Remember that you can change all the fields at once by going back to the billing record and pressing the Change Account Plan button.

As anywhere in Access Meister, you may get help on any field by mousing over its name or clicking on its name.

This pop-up gives you the ability to select a different payment plan for the account, thereby changing all at once the fields Plan Name through Trans/mo Limit on the account's billing record. To make such a change, click the radio button of the desired payment plan name and click the Save button near the bottom.

You may edit those fields manually, but changing them through the Change Account Plan is not only faster, but it changes the fields to values the customer expects from the marketing website of the tool where the payment plans are described.

The most common reason to change a payment plan is when customers exceed their existing storage needs and wish to pay a higher fee for more storage. It is also possible as part of an economy imperative that customers delete information to reduce storage in order to downgrade a payment plan and its fee.

This is the pop-up where you can make quick changes to the credit card used to pay for the account's monthly fees.

Note that you must re-enter the credit card number even if you are only changing its expiration date. This is a security precaution to make sure only the credit card holder is making changes here.

Access Meister (AcM) normally bills customers their monthly fees and collects from their credit cards automatically. Sometimes, we need to adjust their bill manually. This is the form used to do that.

This is how you add a custom transaction line to an account, either to add an additional fee that they owe or some credit for an amount they paid. Note that a discount we grant is treated the same as an amount the customer paid.

Examples of such custom billing transactions include:

• We discover a billing error where the customer has been using the tool without paying. We negotiate an amount they owe, and we add that amount to their bill using this form.
   
• We discover a billing error where we have been double charging the customer. We add up such extra charges and enter a custom billing transaction with a negative amount to give the customer back the amount we overcharged.
   
• The customer requests a change to the tool's software on the basis that we will bell them for the programming. When complete, we add that charge to their bill.
   
• The customer takes a lot of our time to solve a tech support problem that turns out to be on their end. We decide to bill them per our policies using a custom billing transaction.
   
• The customer mails us a paper check. We enter that with a negative amount to show a credit to their account.
   
• The customer refers someone to become a billable Webteam customer. We add a transaction with a negative amount to show the credit to their account of a referral fee.

Just as each tool has a SecLev identifying the level of access available to a user, so too Access Meister (AcM) has its own SecLev granting a user different levels of access to features and data within AcM.

To understand what each SecLev value means and what access it provides, see the Security Access Table by the More Info label.

The name of the company, organization, or government agency managing the account. An account typically pays for access to its data and then allocates access to its data to its users.

If this is the name of an individual, that is the rare case of an individual whose name is used for the account. Most individuals are listed as users.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

This is the mailing city of the user.

This is the mailing country of the user, usually USA.

This is the date a comment note was added.

This is the user's email address.

Often, you can click on it to bring up your regular email software with an email message already addressed to them and ready for you to type into the message body.

This is the name of the person, the individual user, by first name and then family name.

The date the user last logged in.

This is an indication of how actively a user is making use of the tool.

This is the text of the comment note.

This is the password needed after entering a username to gain access to a tool.

The initial default is the same as the username, usually the first initial and last name of a user, lower case and without a space, but the user may change this. Changing it regularly is a good idea.

Although we do not enforce password size or its format, we recommend at least 6 characters to include letters mixed with numbers, as well as symbols such as @$%. Don't use other symbols, and use all lower case letters. The reason is that it is too easy to forget what is capitalized.

A cool trick is to think of a word and then replace letters with symbols and numbers as below:
a - replace with @
b - replace with the number 8, which looks like the capital B
e - replace with a 3, which is like a backward E
i - replace with the number 1
o - replace with the number 0
p - replace with the number 9, which is like a backward P

This is the date the password was last changed.

Access Meister automatically tracks this so that we may one day automatically send out email encouraging users to change their password periodically. Until then, it simply encourages the practice by reminding users how long it's been.

This is the telephone number of the user, preceded by the area code.

This is the postal mailing address of the user in case we wish to send them a letter, which we may do if their email bounces.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

Within each Webteam tool or application, different users get different levels of security access, controlled by what SecLev they are assigned.

Each tool begins with a user with a SecLev of Primary Sysadmin, which is the person who first opens the tool subscription and is responsible for its billing, even if it's free. This person has unlimited access rights within that tool for the corresponding account or sub-account. No one can delete the Primary Sysadmin, although it can be edited to be a different user.

Almost all tools also have any number of users with a SecLev of a regular sysadmin. Such a sysadmin has all rights within the tool except billing and they may be deleted.

Below that, each tool starts to differ regarding the values it has for SecLev, which is always a picklist of values, not free text. These SecLev values differ based on the needs of users peculiar to the tool. KB Meister, for example, has a SecLev of Librarian, which confers certain access rights to manage an online knowledge base. Task Meister has no such online knowledge base, hence doesn't need a SecLev of Librarian. Task Meister, however, does have a SecLev of Contractor restricting contractors to edit only their own tasks within boundaries, a SecLev that KB Meister doesn't need or have.

Administered within each tool, we adhere to the concept of access groups in terms of assigning SecLev access values. That means we collect families of access rights, for example, to view certain data or issue certain commands, into long lists of detailed rights that are designated under a given SecLev value. That means new tool users are not given rights to do different things within the tool. Instead, they are assigned membership to an access group, another name for a SecLev, that automatically assigns or restricts rights based on how that SecLev was previously defined.

This is the mailing state of the user, if he resides in the US.

For Canada, it is the province. For other countries, it is whatever they have.

This denotes whether the user has been granted general entry into the tool of a (sub)account.

It can be "Not Assigned" to indicate that the user has yet to ever be allowed entry. It can be "Active", which means access is granted, but subject to whatever restrictions are in place within the tool based on the user's SecLev. "Inactive" means the user was once allowed entry, but no longer.

This shows if an account name is really a sub-account, in which case the "Sub of" column shows which account it is a sub-account of.

This user status can have one of the two values of active or inactive. We may add more status values if it becomes worthwhile.

A quick way to deny users all access to all tools and (sub)accounts is to change their status to inactive.

A username is a unique identifier Access Meister (AcM) needs to identify each individual granted access to any tool or application AcM manages.

When the record of an individual user is first entered into AcM, he/she is asked to select a username. We suggest the user's first initial followed by their last name, all lower case. We suggest lower case because most Windows users do not realize that lower case and upper case letters are considered different, for example, a jsmith username will not match JSmith.  We also do not allow spaces in a username, though we do allow certain special characters such as @ and &.

If a requested username already exists in AcM, the user requesting is advised, and they can try again, perhaps with variants such as jsmith1 after AcM tells them that jsmith is already taken.

Once a username is selected, it cannot be changed, as can the password that is used with a username to gain access.

This is the mailing ZIP code of the user, if he resides in the USA.

For other countries, it's their postal code.

Access to a tool is granted in two steps.

First, we determine if a user has any access at all, that is, are they an active user or not. If they are active, then we check their SecLev which determines what access rights they have once in the tool. See the "More Info" below for a SecLev definition.

Access Meister (AcM) determines whether a user is active or not in the same way for all tools, but each tool assigns a SecLev value that differs between tools and what that SecLev value allows the user to see and do within the corresponding tool.

The Account Access Edit form begins with a picklist you can use to change the SecLev for the tool in question. A user can have different SecLev values for different tools, but only one SecLev value for each tool, regardless of the account or its sub-account.

The best way to look at the radio button options for each account and sub-account is to follow the following sequence through which a user gains access and then loses it.

1. To begin, all users are described by the "Not Assigned" radio button. You won't see this for the main parent account because that changes to "Active" as soon as an access table is generated. You will see it for any sub-accounts on the table until a user is switched to "Active"
    
2. Once a user's "Active" radio button is selected for a sub-account, that user has the same access there as in the parent account. This is what users need for their SecLev to kick in and determine what they can do now that they have been allowed in the door by being "Active".
    
3. If a user's involvement ends in a sub-account, perhaps because a project finishes, that user may be better off with the "Not Active" radio button selected. This cuts that user's access to use the tool in that sub-account, but his data within that sub-account remains. Tasks he completed in Task Meister, for example, remain in that sub-account's Task Meister for historical records, but he can no longer look at those tasks or edit them. "Not Active" users can be made "Active" by simply pressing the radio button in this table, and they return to work in the sub-account's tool where they left off.
    
4. Finally, let's assume the user turned out to have little to no involvement with the sub-account, and there remains no reason to keep his data, if any, in the sub-account's tool. In this case, the "Remove" radio button breaks the connection between the user and the sub-account's tool.  Such a user's data will be deleted or connected to a different user depending on the policy on removed users within that tool. Note that the user is removed from the tool, but the user is not deleted from Access Meister. Users removed from a parent account are automatically removed from all sub-accounts of that account.

Just as each tool has a SecLev identifying the level of access available to a user, so too Access Meister (AcM) has its own SecLev granting a user different levels of access to features and data within AcM.

To understand what each SecLev value means and what access it provides, see the Security Access Table by the More Info label.

This is the status of the user regarding Access Meister (AcM). It can be either "Active" or "Not Active". This is a simple yes/no switch allowing access or not.

This is unrelated to the user's SecLev, which determines what he can do in AcM once this status setting allows him in.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

This is the mailing city of the user.

This is the mailing country of the user, usually USA.

This is the date a comment note was added.

This is the user's email address.

Often, you can click on it to bring up your regular email software with an email message already addressed to them and ready for you to type into the message body.

This is the individual's given name, like John or Zoltan, even though on lists and in a few cultures, this is shown after the family name.

This is the individual's family name, like Smith or Horvath, even though on lists and in a few cultures, this is shown before the given name.

This is the text of the comment note.

This is the password needed after entering a username to gain access to a tool.

The initial default is the same as the username, usually the first initial and last name of a user, lower case and without a space, but the user may change this. Changing it regularly is a good idea.

Although we do not enforce password size or its format, we recommend at least 6 characters to include letters mixed with numbers, as well as symbols such as @$%. Don't use other symbols, and use all lower case letters. The reason is that it is too easy to forget what is capitalized.

A cool trick is to think of a word and then replace letters with symbols and numbers as below:
a - replace with @
b - replace with the number 8, which looks like the capital B
e - replace with a 3, which is like a backward E
i - replace with the number 1
o - replace with the number 0
p - replace with the number 9, which is like a backward P

This is the telephone number of the user, preceded by the area code.

This is the postal mailing address of the user in case we wish to send them a letter, which we may do if their email bounces.

This is the user's primary account.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

This is the mailing state of the user, if he resides in the US.

For Canada, it is the province. For other countries, it is whatever they have.

A username is a unique identifier Access Meister (AcM) needs to identify each individual granted access to any tool or application AcM manages.

When the record of an individual user is first entered into AcM, he/she is asked to select a username. We suggest the user's first initial followed by their last name, all lower case. We suggest lower case because most Windows users do not realize that lower case and upper case letters are considered different, for example, a jsmith username will not match JSmith.  We also do not allow spaces in a username, though we do allow certain special characters such as @ and &.

If a requested username already exists in AcM, the user requesting is advised, and they can try again, perhaps with variants such as jsmith1 after AcM tells them that jsmith is already taken.

Once a username is selected, it cannot be changed, as can the password that is used with a username to gain access.

This is the mailing ZIP code of the user, if he resides in the USA.

For other countries, it's their postal code.

Just as each tool has a SecLev identifying the level of access available to a user, so too Access Meister (AcM) has its own SecLev granting a user different levels of access to features and data within AcM.

To understand what each SecLev value means and what access it provides, see the Security Access Table by the More Info label.

The name of the company, organization, or government agency managing the account. An account typically pays for access to its data and then allocates access to its data to its users.

If this is the name of an individual, that is the rare case of an individual whose name is used for the account. Most individuals are listed as users.

This identifies the author of a comment note.

It can be an individual user or the Access Meister system if the note was automatically generated.

This is the mailing city of the user.

This is the mailing country of the user, usually USA.

This is the date a comment note was added.

This is the user's email address.

Often, you can click on it to bring up your regular email software with an email message already addressed to them and ready for you to type into the message body.

This is the name of the person, the individual user, by first name and then family name.

The date the user last logged in.

This is an indication of how actively a user is making use of the tool.

This is the text of the comment note.

This is the password needed after entering a username to gain access to a tool.

The initial default is the same as the username, usually the first initial and last name of a user, lower case and without a space, but the user may change this. Changing it regularly is a good idea.

Although we do not enforce password size or its format, we recommend at least 6 characters to include letters mixed with numbers, as well as symbols such as @$%. Don't use other symbols, and use all lower case letters. The reason is that it is too easy to forget what is capitalized.

A cool trick is to think of a word and then replace letters with symbols and numbers as below:
a - replace with @
b - replace with the number 8, which looks like the capital B
e - replace with a 3, which is like a backward E
i - replace with the number 1
o - replace with the number 0
p - replace with the number 9, which is like a backward P

This is the date the password was last changed.

Access Meister automatically tracks this so that we may one day automatically send out email encouraging users to change their password periodically. Until then, it simply encourages the practice by reminding users how long it's been.

This is the telephone number of the user, preceded by the area code.

This is the postal mailing address of the user in case we wish to send them a letter, which we may do if their email bounces.

The Pvt designation for a comment note indicates it is a private note for the eyes of a system manager only.

This can be a sensitive credit or billing issue such as a pending attempt at forced collections. If the Pvt checkbox is checked, none of the account's users, not even their primary sysadmin, will see the note.

Within each Webteam tool or application, different users get different levels of security access, controlled by what SecLev they are assigned.

Each tool begins with a user with a SecLev of Primary Sysadmin, which is the person who first opens the tool subscription and is responsible for its billing, even if it's free. This person has unlimited access rights within that tool for the corresponding account or sub-account. No one can delete the Primary Sysadmin, although it can be edited to be a different user.

Almost all tools also have any number of users with a SecLev of a regular sysadmin. Such a sysadmin has all rights within the tool except billing and they may be deleted.

Below that, each tool starts to differ regarding the values it has for SecLev, which is always a picklist of values, not free text. These SecLev values differ based on the needs of users peculiar to the tool. KB Meister, for example, has a SecLev of Librarian, which confers certain access rights to manage an online knowledge base. Task Meister has no such online knowledge base, hence doesn't need a SecLev of Librarian. Task Meister, however, does have a SecLev of Contractor restricting contractors to edit only their own tasks within boundaries, a SecLev that KB Meister doesn't need or have.

Administered within each tool, we adhere to the concept of access groups in terms of assigning SecLev access values. That means we collect families of access rights, for example, to view certain data or issue certain commands, into long lists of detailed rights that are designated under a given SecLev value. That means new tool users are not given rights to do different things within the tool. Instead, they are assigned membership to an access group, another name for a SecLev, that automatically assigns or restricts rights based on how that SecLev was previously defined.

This is the mailing state of the user, if he resides in the US.

For Canada, it is the province. For other countries, it is whatever they have.

This denotes whether the user has been granted general entry into the tool of a (sub)account.

It can be "Not Assigned" to indicate that the user has yet to ever be allowed entry. It can be "Active", which means access is granted, but subject to whatever restrictions are in place within the tool based on the user's SecLev. "Inactive" means the user was once allowed entry, but no longer.

This shows if an account name is really a sub-account, in which case the "Sub of" column shows which account it is a sub-account of.

This user status can have one of the two values of active or inactive. We may add more status values if it becomes worthwhile.

A quick way to deny users all access to all tools and (sub)accounts is to change their status to inactive.

A username is a unique identifier Access Meister (AcM) needs to identify each individual granted access to any tool or application AcM manages.

When the record of an individual user is first entered into AcM, he/she is asked to select a username. We suggest the user's first initial followed by their last name, all lower case. We suggest lower case because most Windows users do not realize that lower case and upper case letters are considered different, for example, a jsmith username will not match JSmith.  We also do not allow spaces in a username, though we do allow certain special characters such as @ and &.

If a requested username already exists in AcM, the user requesting is advised, and they can try again, perhaps with variants such as jsmith1 after AcM tells them that jsmith is already taken.

Once a username is selected, it cannot be changed, as can the password that is used with a username to gain access.

This is the mailing ZIP code of the user, if he resides in the USA.

For other countries, it's their postal code.

This is the base monthly fee in dollars that an account must pay to continue to use a tool given the amount of storage and/or transactions to be secured through such payment. This fee amount is usually set by the plan the customer chooses, but management may edit it.

The name of the company, organization, or government agency managing the account. An account typically pays for access to its data and then allocates access to its data to its users.

If this is the name of an individual, that is the rare case of an individual whose name is used for the account. Most individuals are listed as users.