Every person using Aconex Field has a project role, which comes with specific responsibilities and access privileges.
Field's project roles allow organizations to easily control and manage what your people can do in Aconex Field. There are two types of roles in Aconex Field – access roles and administrator roles.
An access role allows a person to login to Aconex Field on a project, and determines what they can actually do on that project.
This table shows which permissions are associated with the various user roles available in Aconex Field. All participants in a project that has Field enabled will have Observer permissions by default.
User roles | Export issues / inspections | View issues / inspections | Capture issues / inspections | Edit issues / inspections | Assign issues / inspections | Change status | Close issues / inspections |
---|---|---|---|---|---|---|---|
Observer | yes | yes | no | no | no | no | no |
Assignee | yes | yes | no | no | no | yes | no |
Inspector | yes | yes | yes | yes* | yes | yes | yes* |
* Inspectors can only edit and close issues/inspections that their organization has created.
Punchlists use the same permissions as issues. If Punchlists is not enabled for your organization, the Aconex-owning Project Admin should raise a service request, requesting us to enable it for you.
Daily report permissions are managed separately.
Inspectors are able to:
Assignees can:
Observers are able to:
Administrator roles allow a person to access Field settings as described below.
Project Administrators are able to:
Inspector Administrators can:
Assignee Administrators are able to:
Observer Administrators can: