CHANGING ACL:

Modifying ACL of an account requires admin privileges. Log on as admin if you are not already one, and go to LeftNav->Accounts->ChangeACL:

Even though the login name is unique, database uses the loginId as the 'key' in all tables. Therefore, an admin likely prefers to use the loginId for all practical purposes. 'Change ACL' window accepts either one (loginId or login name), and if both are provided choses loginId over login name.

Now, enter the username of the account you just created (leaving login Id blank or 0), and submit. The same window will be returned with the loginId, login Name, and ACL privileges of the account all filled-in:

The 'elvis' account (or whatever username you just created) should have all its ACL privileges unchecked. For the sake of a practice, give 'elvis' the 'partner' privilege by checking the 'partner' radio box, and submit. By simply checking or unchecking the associated radio boxes, you can grant or revoke ACL privileges.

Granting partnership to an account won't do too good since none of the existing applications does anything special for partners. However, if you had granted 'employee' privileges to 'elvis' (even though he was not an employee), 'elvis' then for instance, could access the 'Associate Zone'.

We should point out a common pitfall here: At times an admin attempts to modify ACLs of multiple accounts, and satisfied with the result of the first, enters the next username and hits 'Find'. Only to find the first user again! You should remember to clear out the loginId of the first user if you intent to use a login name rather than the loginId to 'Find' again here.

Now if you log out and log back on as 'elvis' (or whatever account you just created and granted 'partner' privileges), and then go to LeftNav->Accounts, this is what your account info will look like:

This is all the magic there is to create and manipulate accounts. For now the next subject in line is Ticket Tracking.