...
- Private - only the owner can edit, test or use the form. The owner must log in to .
- Public In Tenant - the form is usable to anyone who has an account (username/password) and is logged in to your tenant.
- Public - anyone can use it even if they are not logged in.
- Custom - The owning designer always has access to the form/flow. Additionally, the designer may configure selected users and/or roles (i.e. users with these roles) to have runtime access to the form. Custom is not supported for flows because roles and users are assigned to the steps in a flow to indicate who has permission to perform that step.
Note |
---|
The Visibility property has been removed from the form/flow properties pane in the designer. You can no longer change form/flow permissions in this manner. When is embedded in another product such as Atlassian's Confluence wiki, you do not have access to the icons described above. |
...
Section | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Click Finish or continue with the next option in the Permission dropdown.
The Expense Report in the above images can be used by anyone in the tenant with the role of Employee, Manager or Accounting, the user id of the Reviewer and the user Sue. Notice the Reviewer role is encased between curly braces. This is an example of a form template. Templates are like variables in your form that will be evaluated at runtime and replaced with the actual values entered. For templates to work, there must be a control in your form with the name given inside the curly braces.
The user, Jack, who has the role of frevvo.Publisher, is not a Reviewer for anyone in the company and of course, is not Sue, will be denied access to the form. He will see this error:
You can publish any form regardless of whether it is public or private, but if it is private, only the person who created it can edit it or test it. Another user may log in using your ID and password, however, so it is possible to collaborate on a form without sharing it, as long as two of you are not editing the same form at the same time. Two or more people may test the form and view submissions at the same time.
Similarly, if a form is public in tenant, only users with accounts in the tenant will be able to access the form.
...
The designer can set other permissions, such as who can view/edit submissions for forms and flows via the Access Control wizard. Roles and users that can view the audit trail or be designated as flow administrators are specified through the same wizard.
Note |
---|
Anonymous users can now access public Public forms that include the save/load feature or digital signatures. These features , require a login. When the anonymous user clicks to save or sign, they will be prompted with the login screen. |