Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

The form/workflow visibility feature is integrated with the Access Control feature. Both features open the same wizard where you may specify form/workflow permissions or grant view/edit submission permissions to specific users/roles. The form/workflow visibility property is discussed here. 

Setting Visibility for Forms/Workflows

...

The frevvo designer can specify the visibility of a form/workflow from either the Forms and Workflows Homepage or the Guided Designer: Settings mode.

...

  • Image Added Action Menu on a form/workflow and select

...

  • Image Added Set Permissions.
  • In the Guided Designer: Settings mode, open the Access Control tab.
    Workflow:

...

  • Image Added
    Form:
    Image Added
Image RemovedWhen Who can start the form or Who can start the workflow is displayed in the Permission field, the designer can select one of the dropdown choices to specify form/workflow visibility. Until you set your form/workflow visibility to Anyone (login not required) all other users will see this

Excerpt

The default value for forms is Anyone (login not required) while and for workflows default to is Authenticated Users (login required). The choices for designer can select one of the following choices to specify form/workflow visibility are:

oles and users
  • Anyone (login not required) - anyone can use it even if they are not logged in. A form/workflow made public this way is accessible to anyone with the form/workflow's URL. The other options have higher levels of security. See form security for details.
  • Authenticated Users (login required) - the form is usable to anyone who has an account (username/password) and is logged in to your tenant. 
  • Designers/Owner Only - only the designer user who created the form/workflow (owner) can edit, test or use the formuse it. They must be logged into frevvo.
  • Custom - The

    owning designer always has access to the form/workflow. Additionally, the

    designer may configure selected users and/or roles (i.e. users with these roles) to have runtime access to the form.

    Use this option to auto-start workflows programmatically.
Note

When  is embedded in another product such as Atlassian's Confluence wiki, you do not have access to the icons described above.

The designer can grant form/workflow access to explicit users/roles by selecting the Custom option. R
  • Users and Roles can be selected via an editable combo-box control. As the user types,

  will
  •  frevvo will try to find any roles and users in the tenant that contain the typed string. Up to 5 matches are displayed below the combo box.

Selecting
  • Selecting a role/user from the dropdown inserts the selection into the list. 

    Info

    The owning designer always has access to the form/workflow, even when Custom permissions are used. 


Image Modified

Click Submit or continue with the next option in the Access Control wizard. 

Here is an Expense Report that 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 control 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.

Image Removed

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:

Image Removed 

You can publish any form/workflow regardless of whether it can be started by Anyone (No login required) or just the Designer/Owner. If Designer/Owner Only is selected, the person who created it or any user given the Who can edit the form/workflow permission can edit it or test it. It is possible for more than one designer to collaborate on forms/workflows in development if the form/workflow owner (the designer that created the form/workflow) gives this permission to other designers. However, if one designer is working on the form, other designers will be denied access. Form/workflow owners can also designate the Who can view submissions or Who can edit submissions permissions to other users so two or more people may view/edit submissions at the same time.

Warning
Note
  • When frevvo is embedded in another product such as Atlassian's Confluence wiki, you do not have access to the icons described above.
  • Templates are not supported for this permission.

User Experience

Users who have "Who can start the form/workflow" access will see the form/workflow and be able to fill it out when it is shared with them (e.g. via a share link, Space, or embedded in a website.) If the permission is set to authenticated users and/or roles, the user must be logged in to see the form/workflow.

Users who are not logged in and trying to access a form/workflow with "Who can start the form/workflow" permission set to all or custom authenticated users will be prompted to log in.

Logged in users who do not have "Who can start the form/workflow" access will see an error message when they try to access the form: "Error Access Denied. Authentication required. Are you trying to access a private form or workflow?

Similarly, if a form visibility " This error will never be shown when this permission is set to Authenticated UsersAnyone (login not required), only users with accounts in the tenant will be able to access the form..

Public forms that include the save/load feature or digital signatures will prompt the user with the login screen when they click to save or sign. These frevvo features require a login.

Deploying to Production

You can publish any form/workflow regardless of the Who can start the form/workflow? permission. Publishing involves sharing your form/workflow with users (e.g. via a share URL, embedding in Space, or embedding in your website). Set the Deployment State to "Production" via the Form/Workflow Settings or the Action Menu to remove the watermark and (for Cloud customers) begin counting submissions towards your license.

Editing Forms/Workflows in Production

If you set the form/workflow visibility to

...

anything other than "Designer/Owner only" and users have begun submitting it, you'll need to use caution when modifying your form. If users access it while you are editing it, they will see error messages indicating that the page is being refreshed or that the form is invalid.

...

 

Please see the Administrator Best Practices for Updating a Form/Workflow in Production.

Info

ACL settings set by the designer are retained when you download/upload a form/workflow/project to another designer user in the same or different tenant and when you copy a form/workflow.

Other Permissions

The designer can set other permissions

...

via the Access Control wizard

...

 such as roles and users that can edit the form/workflow, view/edit submissions, view the audit trail or be designated as workflow administrators

...