Roles are assigned to web and device users throughout Field View to determine what they have permissions to do within the web application
and on devices.

Roles

Roles are assigned to web and device users throughout Field View
to determine what they have permissions to do within the web application and on devices.

People are assigned roles with permissions in business units and projects, and within those, permissions for working with forms, tasks, workflows, trades, causes, assets, locations, processes, drawings (geometry), packages, reports, and etc.

High-level Administrator roles should not be allocated to people in organizations outside your business unit. Once a person has been given a role in a business unit, he or she should not be given a role with fewer rights in a project or a child business unit belonging to that business unit. You can, however, give that person a role with more rights in a project or child business unit as needed.

There are many default System Roles that you can assign to users. You can also add roles as needed. You can also make specific roles inactive within a business unit.

The table describes the default System Roles. For a more specific view into the permissions given to each role in a business unit, navigate to Business Setup > Security > Roles. Click a role in the Roles pane, and the permissions display in folders in the left pane. Expand the folders to see the specific system permissions.

Role

Description

Business Unit Administrator

Can administer all aspects of the business unit and its projects. Should not be given to people outside your organization.

Client

Can maintain only tasks issued by their organization.

Client/Sub-Con Add Forms

Can add their forms onto your project.

Client/Sub-Con Add Package

Can add their packages of work onto your project.

Client/Sub-Con Add Task Type

Can add their task types onto your project.

Form Contributor

Can contribute to (answer questions on) forms on the project only when invited.

Inspector

Government inspectors, can add snags/punchlist items to your project.

Project Administrator

Can administer all aspects of the project. Should not be given to people outside your organization.

Business units are set up in a hierarchy that reflects the structure of your business.
Then each construction project is set up within the business unit that is administering
the project. Forms, tasks, processes, and other commonly used components of business
operations are all created in a business unit, and then can be shared among that business
unit's projects.

Using Viewpoint Field View™, Viewpoint Team™, and Vista™ by Viewpoint, you can create Field View form templates from Vista User Defined (UD) forms, and
Field View predefined answers from Vista UD lookups, and keep your data in sync
across all applications.

A project in Field View includes a hierarchical structure of individual locations
within the construction project. It also includes location-aware
plan drawings to guide users to the project locations where a
task, form, issue, or asset is located or needed. This structure enables you
to track and report on the progress of your construction project.

Barcodes and QR codes are used to identify locations and assets on the job site. You
print labels with barcodes and QR codes and affix them to their corresponding
locations and assets. Mobile device users scan the labels to quickly access the
associated information in Field View.

If you have an account in Viewpoint For Projects, you can add plan drawings from
Viewpoint For Projects into a Field View project. You can also replace plan drawings
in Field View with updated plan drawings from Viewpoint For Projects.