...
When creating a new form, users can choose which team(s) can create or edit a request/job/asset with this form, and which teams can view requests/jobs/assets created. So we the request and jobs. If you do not set a permission, Gruntify defaults to allowing all users in the workspace to have access.
We have 3 types of permissions, and they work separately:
Who can create - only users inside of the team(s) assigned to this form can create requests, assets or jobs using this form. Other users/teams can’t view this form from the form list.
Who can edit - only users inside of the team(s) assigned to this form can edit requests (jobs, assets) which are created using this form. Other users/teams won’t have the edit option available.
In the case of editing, you can also set it to Nobody (cannot be edited once saved) or only edited by the creator of the request (job, asset). Nobody is useful for Requests and Assets where once the data is created it should never be changed, say for legal reasons.
Note: The Nobody option is not appropriate for jobs. We suggest setting editors to one or more teams, or not setting any editing permissions for jobs. Remember leaving the option blank means everyone has access.Who can view - only users inside of the team(s) assigned to this form option can view requests and jobs which are created using this form from the request/map list. Other users/teams won’t have access to them. This option does not exist for Assets - all users in the workspace can see all assets.
You can assign more than one team for all permissions described here, or you can limit the access to nobody or request creator. All permissions work in the same way across all platforms: Web, Android, and iOS.
...
| Widget Connector | ||||||
|---|---|---|---|---|---|---|
|
...
Related articles
...
Page:
...
Page:
Creating a Form from a Form Template
...
Page:
Page:
...
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|