A TRACE user, also called project staff, is anyone that has been assigned a role and given a login to access a project in TRACE. A role in TRACE is similar to a user group in networking in that it determines a user's access rights for a given project. What sets TRACE roles apart is that only one role can apply to any user.

Note: Throughout this section this manual refers to projects and TRACE information (data). For additional information to aid in this discussion, refer to Data Organization.

A TRACE user can access TRACE and use its features to store and retrieve information depending on their assigned role.

TRACE user types include:

●      Project Administrator: A project administrator differs from a TRACE administrator in that their access to make changes is limited to the project-level. Project administrators may be assigned to any project role, and can perform the following tasks:

●      Modify the project that they are administrators on

●      Assign project roles and access to users

●      Create project form types

●      Create project field types

●      Have full access to all project forms

●      Regular: Have read/write access determined on a form-type and field basis.

When a TRACE administrator creates a new project, they identify the project team lead and assign them the Project Administrator role. The project administrator then adds users to the project and assigns them roles depending on the type of work they contribute to the project. Note that the project administrator only assigns the TRACE user to a role. A TRACE administrator must first create the user account.

When a project administrator assigns a role to a user, the user inherits the access rights assigned to the role in TRACE. These access rights determine what project staff can do and the information that they can see. For example, a product tester only requires access to the tests they need to record data on, but a PM requires access to add, edit, or delete anything used to properly manage the project in TRACE.

While the number of project staff can vary greatly between projects, the levels of responsibility necessary to manage project information determine the number of roles.

Note: Project administrators can create custom roles with custom access rights to meet project needs. See Customizing TRACE.

Table 3‑1 provides a breakdown of access rights by project role.

Table 3‑1: TRACE Access by Role

TRACE Roles	Read	Edit	Create	Delete	Execute	Internal
Wind River Project Manager	Yes	Yes	Yes	Yes	Yes	Yes
Wind River Lead Engineer	Yes	Yes	Yes	Yes	Yes	Yes
Wind River Engineer	Yes	Yes	Yes	Yes	Yes	Yes
Wind River Tester	Yes	Yes	Yes	No	Yes	Yes
Wind River Reader	Yes	No	No	No	No	Yes
Customer Project Manager	Yes	Yes	Yes	Yes	Yes	No
Customer Lead Engineer	Yes	Yes	Yes	Yes	Yes	No
Customer Engineer	Yes	Yes	Yes	No	Yes	No
Customer Tester	Yes	Yes	Yes	No	Yes	No
Customer Reader	Yes	No	No	No	No	No

Additionally, a user with any role can view, edit, create, and share reports and/or filters for any form type they have access to.

TRACE access rights include:

●      Read: Staff can read information from forms of this type.

●      Edit: Staff can edit forms of this type.

●      Create: Staff can create a new form of this type, such as a new bug, action item, and so on.

●      Delete: Staff can delete items of this type.

●      Execute: Provides the ability to perform test runs or other similar item in TRACE that uses the pass/fail feature.

●      Internal: Internal Staff can view internal comments and forms. See Internal vs. External.

Record Access Controls

User rights on a form are established by assigned role in the project. However, Project Administrator has the ability to override user rights on a form by restrict or loosen up than normal its access using Record Access Controls.