DEFAULT ACCOUNTS:

Bora Builder comes with a couple of pre-installed demo accounts. It is recommended that the Bora administrator should change passwords of these accounts after the installation, or delete them altogether. They are:

user: admin, password: admin:

Has all ACL privileges as listed earlier.

 

user: employee, password: employee:

Has only employee privileges.

 

user: sales, password: sales:

Has employee and sales privileges.

 

user: member, password: member:

This is an account opened for someone who is not a company employee. Account like this one might be for Beta testers, for people who are members of interest groups contributing to discussion forums, etc. Other than having a unique login Id, this account has no access control privileges.

 

user: partner, password: partner:

Has partner privileges as documented above. However, since no Bora application currently takes advantage of this ACL privilege, this account is identical to 'member' in nature.

CLIENT CATEGORIES:

Upon receiving a page hit, Bora applications analyze and put clients into different categories:

Visitor: If a client does not have a login ID, he/she is considered a visitor. Since access control privileges are associated with login IDs, absence of a login ID immediately implies no access control privileges.

Member: If the client does have a login ID, but if he/she is not an employee, then he/she is considered a 'member'. Members and employees share the same login namespace. A member, by default, is not granted any access control privileges, and the Bora Admin better not violate it. 'member/member' (username/password) and 'partner/partner' accounts are of this type. A member account can be identified with a type 'M' in its login record.

Employee: In this category login status indicates an 'employee', with a type 'e' in the login record. An employee normally should have at least employee access control privileges, however, he/she might have more than that.

Customer: Before giving the definition for this category, lets clarify the terminology conflict between a 'client' and a 'customer' first. By 'client', we mean to indicate a client (browser) of the server (Bora Builder), and by 'customer', we talk about a purchasing customer, having a credit card, etc.

A customer has a unique customer ID maintained by the Bora applications. A client, after going through certain order procedures (purchase), might be promoted to a customer status and get assigned a unique ID. A customer ID is different from a login ID. Although in many cases visitors are promoted to the customer category, there is no reason for a member or an employee not to make a purchase from company e-shop and acquire a customer status. I.e, a client might retain a customer ID and a login ID at the same time.

A customer is uniquely identified by his/her first name, last name and email address.

Having a grasp of these notions, let's now start with the Bora Applications: