Skip to main content
Known Limitations

A list of known limitations of Team Forms

Updated over a month ago

The following is a list of known limitations of the Team Forms platform. Many of the documented limitations will be supported in future releases.

Public unauthenticated access to responses

Access to view and edit responses is currently only available to team members (and guests). Public unauthenticated access to responses is currently not supported.

Reduced functionality in public share links

Forms generated with the "anyone with the link" sharing method are accessible publicly and anonymously. Because of this there are currently some know limitations that are unique to these types of share links. This includes:

  • SharePoint data-sources are currently not supported in public links

  • For security reasons the user component is not supported in public links

  • Automatically identifying the logged in user is not supported in public links

Get Response Action in Power Automate "New Builder"

When using the "New Builder" in Microsoft Power Automate you may find that when adding the "Get Response" action to a workflow, the wrong action block is added. This is currently a known bug with the new Power Automate workflow builder. Microsoft is currently working on resolving this issue, however in the meantime you can switch to the classic builder or better yet, use the response data provided by the "When a form response is submitted" trigger.

Did this answer your question?