Understand your user permissions

Polarion has a sophisticated, multitier security architecture with extensive control over user permissions, which regulates who has what level of access to what. Permissions can be defined for user roles, and/or for specific types of content in the system. Polarion's permissions sit atop the access control mechanisms of the underlying repository.

If you encounter any of the following or similar problems, the most likely reason is that you are not currently granted the requisite permissions:

• You cannot create a Work Item in the Tracker or a Document.

• You cannot use Work Items, Requirements, or Test Cases, for example, after initial import from Microsoft Word or Excel.

• You cannot overwrite a referenced Work Item of some type in a Document.

• You cannot move a Work Item of some type to or from a Document.

• You cannot create linked or linking Work Items of some type.

• You cannot create artifacts in a project, such as Documents, Plans, or Test Runs.

• You cannot create or open a project.

To create new projects your user account must be assigned a user role which has been granted that permission. If your system is configured to support multiple repositories, you must have the necessary permissions for the repository that hosts the new project.

User permissions are defined in the User Management topic of Administration, and configured by administrators. If you cannot create, modify, or view any content that you believe you should have access to, either contact your administrator directly or follow whatever contact chain your team or organization has established.