Administration permissions
To access Polarion's administration interface you must have a user account that is granted administrator-level access permissions. Access permissions are granted to a Role, which can then be assigned to user accounts.
Administrator permissions may be granted for either or both of two scopes:
Global: administrator permissions for the entire repository, including all projects.
Project: administrator permissions for a specific project.
The default administrator account
After a new installation there is one default user account with user name System Administrator which has Global administrator permissions.
The default log-in credentials for this account are:
User ID: admin
Password: admin
The default System Administrator account provides access to all Polarion administration and configuration features for the Polarion system, to all projects in the integrated Subversion repository, and to the repository itself.
It is good practice to periodically change the password for the System Administrator account. For information about passwords in general, see Passwords.
Define additional administrators
The System Administrator may find it useful or necessary to grant administrator permissions to other Polarion users. For example, if the main administrator is absent for some reason, someone else in the organization should be able to perform all system administration functions with Polarion. Also, the managers or leaders of projects can be given administrator permissions for the projects they oversee. This enables them to perform such tasks as adding user accounts, assigning project user roles, and modifying the project configuration and properties.
A prospective administrator must have a user account on your Polarion system. Some global roles should already be assigned in the process of creating the user account. Some project-scope role assignments may also exist on the account. To grant administrator permissions, you need to edit the user's account and specify administrator role(s) for the Global scope, if applicable, and per project for project-scope administrator permissions.
For information on creating user accounts and defining user roles, see Managing Users & Permissions.