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.
|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.|
|Project Editor||Can edit all processes on the project.|
|Subcontractor||Can maintain only own tasks on the project.|