9 1:Administration-Administrator User Accounts

From Pnet-Community

Revision as of 19:56, 5 April 2010 by Dkassman (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Contents

[edit] Project.net Application Administrator User Accounts

Project.net's built-in administrator account appadmin has the capability to administer licenses, user accounts, projects, etc; these capabilities can be given to other accounts, as well. Because of their abilities, administrator accounts should be treated differently than regular user accounts.

[edit] Best Practices for Administrator-enabled Accounts

  • Do not use any administration-enabled user account, including appadmin, to do "regular" project management-type task. Administrator accounts should be reserved for administration tasks only, such as correcting a user's account or restoring a deleted workspace. A best-practice is for an administrator to have two accounts: a regular, "every day" account and a separate "admin" account. If Tom is an administrator he would have accounts with names like 'Tom' and 'Tom-admin'.
Here is why you do not want to use an administrator's account as a normal account. Since an administrator-enabled account lets the use do things he or she would not be able to do as a regular user, like enter projects he or she is not invited to, it is possible to create items that normal users cannot access. The best approach is to use a regular account for normal project management tasks, and only login with an administrator account when the person needs one of its special capabilities.
  • Limit who has access to administrator accounts. Application administration privileges have a lot of control over Project.net and it is possible to damage your installation if an administrator does not know what he or she is doing. Therefore, it is recommended that you limit administration capabilities to those who need those capabilities and who are trained.
  • Give each administrator his or her own administrator account; instead of sharing the appadmin account keep it as a reserve with a known safe password. This eliminates the possibility of an administrator accidentally locking all administrators out of the system by changing the appadmin's password. It also means an individual administrator's account can be deleted without affecting the other administrators.

[edit] Giving Application Administration capabilities to a user account

There is a way to give a user account application administration privileges. As mentioned above, the best practice is not to do this with the person's everyday user account, though, but to create a separate "admin" account for use when that person needs administrator's privileges.

To give an account administrative permissions the account must already exist, then follow these steps:

  1. Log into the system with an account with administration capabilities.
  2. Click [Admin] next to the [Log out] link in the upper right of the page; this will open the Application Administration module.
  3. Select [Directory] from the menu bar.
  4. Click [Invite Member] from the Toolbox.
  5. To give an existing user account administrative privileges enter the first name, last name and email address associated with the user account; make sure to use the same email address.
  6. Click the down-arrow to add the account to the invitee list.
  7. Decide whether or not to send an email notification and, if so, enter an optional message.
  8. Click [Add New Invitees]
  9. Fill in the title and responsibility, if desired.
  10. Check Space Administrator then click [Submit].

The next time the user logs in he or she will have access to the Application Administration area.

[edit] More Help

Personal tools