Wrike Form Requiring Company Email

We recently ran into an interesting user error for our forms. We had a user submit a personal email in the submitter's email field. Since we have non-Wrike users who can submit our forms, we can't make it a user-specific field. Is it possible to have it only accept certain email addresses that have a company domain versus a gmail or yahoo to avoid the user error?

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Anna Giacobbe

Hi @Kat Riddler!

I came across your post and was wondering if you can expand on the issue you're facing to better understand what's going on.

From my understanding, you're using an external form. Note that you can still have this form enabled for folks on your account as an internal link/form (Wrike users) to avoid making your users have to fill in the required name/email address fields. Something worth mentioning which I believe you already know iis that if your form is enabled for external use, you won't be able to add user fields (where you search and add Wrike users to the question) as it's a privacy issue.

If the issue is that you want your internal users to be able to use user fields, I would suggest duplicating the form:

1. Keep your original form as the external version for non-Wrike users

2. Keep your duplicate form only for internal Wrike users and add your user field in!

Duplicating it will be the best way to ensure that the same questions and automations and settings kick in, but will allow you to include that user field question. The only downside is that you'll need to remember to maintain both forms in the event that changes are needed.

Hope this helps and hope I understood it correctly

Pietro Poli

Hi @Kat Riddler the solution given by @Anna Giacobbe is the only solution you have now.
Wrike doesn't have rules (to avoid some domains) for email field in forms.

You can achieve this creating a custom form outside Wrike or using CRM system (e.g. HubSpot), HubSpot can be integrated with Wrike and your custom form by API.

Rohan V

Thank you so much, @Anna Giacobbe and @Pietro Poli, for stepping in and helping our Community members as always! @Kat Riddler, I hope this workaround is useful for your use case. Nonetheless, your post has been forwarded to our Product Team as well. If there are any updates in the future, I’ll keep you posted 👍