Getting Input Data
In order to configure your environment on FieldPro, we require you to provide us with a couple of inputs.
The more accurate these inputs are, the quicker the deployment phase.
Some of the key input data required are;
Mobile Users
Web App users
Organizational structure -Teams
Mapping of users to teams
Product list
Clients list
Please, go through the explanation below of the data needed and populate the attached file below.
Template - FieldPro - Project kick-off - Input data required
For more explanation and understanding of each tab/category, we have added a link to a more detailed article.
The users will need to access the mobile app. Some of the mandatory fields on this section are the first name, last name, number and the team that the user belongs to.
Refer to this page to understand the fields of a mobile user and how to manage them.
These users will be able to access our web portal to:
Perform administration tasks, like managing users or lists, etc.
View the reporting dashboards
We have three key Web App user roles access rights:
Viewer.
Editor.
Admin.
Refer to this page to understand the fields of a Web App user and how to manage them
The teams are the organizational units to split the users, manage the access to workflows and dashboards.
Refer to this page to understand how the Teams work
We need to know how mobile and web users are assigned to the teams created.
For the mobile user, fill in the phone number as the primary key. For the web user, fill in the email.
To define the list, we have a set of standard fields for which the label and the options can be customized.
You can also add custom fields. The field can be of any of this type.
Refer to this page to understand the fields of a product list and how to manage them
To define the list, we have standard fields that we can customize and you can as well add custom fields.
You can also add custom fields. The field can be of any of this type.
Refer to this page to understand the fields of a place list and how to manage them
The more accurate these inputs are, the quicker the deployment phase.
Some of the key input data required are;
Mobile Users
Web App users
Organizational structure -Teams
Mapping of users to teams
Product list
Clients list
Please, go through the explanation below of the data needed and populate the attached file below.
Template - FieldPro - Project kick-off - Input data required
For more explanation and understanding of each tab/category, we have added a link to a more detailed article.
Mobile Users
The users will need to access the mobile app. Some of the mandatory fields on this section are the first name, last name, number and the team that the user belongs to.
Refer to this page to understand the fields of a mobile user and how to manage them.
Web App users
These users will be able to access our web portal to:
Perform administration tasks, like managing users or lists, etc.
View the reporting dashboards
We have three key Web App user roles access rights:
Viewer.
Editor.
Admin.
Refer to this page to understand the fields of a Web App user and how to manage them
Organizational structure (Teams)
The teams are the organizational units to split the users, manage the access to workflows and dashboards.
Refer to this page to understand how the Teams work
Mapping of users to teams
We need to know how mobile and web users are assigned to the teams created.
For the mobile user, fill in the phone number as the primary key. For the web user, fill in the email.
Product list
To define the list, we have a set of standard fields for which the label and the options can be customized.
You can also add custom fields. The field can be of any of this type.
Refer to this page to understand the fields of a product list and how to manage them
Clients list
To define the list, we have standard fields that we can customize and you can as well add custom fields.
You can also add custom fields. The field can be of any of this type.
Refer to this page to understand the fields of a place list and how to manage them
Updated on: 26/05/2023
Thank you!