Skip to main content
Visit Freshworks.com Visit Freshworks

I was wondering if anyone else has experienced this issue and if so, how they have resolved it.

We have our People and Culture team with a separate Workspace as IT and as their interactions with employees and potential candidates require interaction with people via a personal email address this can sometimes cause issues when forwarding or including key stakeholders into email communications. If you are not careful your emails can sometimes be sent to a personal email address instead of a organizational email address.

Is there a way to restrict access to personal email addresses to only our P&C workspace? I can see that Requesters sits under the Global Workspace so not sure if this is possible.

Any insights would be greatly appreciated

 

 

The latest release may solve this for you

 

 

To restrict email notifications to only the requester's organizational email address, you can implement the following steps:

  1. Verify Email Domain: Ensure that the email address provided by the requester belongs to the organization’s domain (e.g., @company.com).

  2. Set Email Validation Rules: In your system or application, set up validation rules that only allow email addresses from the organization’s domain. This can be done through regex checks or custom validation scripts.

  3. Update Notification Settings: Adjust your email notification system to check that only requests from valid organizational email addresses are processed for notifications.

  4. Reject External Emails: If a requester provides a personal or external email, the system should either block or request them to use an organizational email.

you're facing an issue with keeping email communications streamlined between different workspaces while ensuring that personal email addresses aren’t mixed up with organizational ones. To restrict email notifications to use only organizational email addresses, you might need to enforce email domain restrictions for users within your workspaces. For instance, you could configure your system or platform (e.g., your CRM or ticketing system) to only allow emails from specific domains tied to your organization. Depending on the platform you use, this might be a setting in the workspace or global settings, where you can define valid email domains. Alternatively, you could add a validation step where email addresses are checked before being used, ensuring only valid organizational addresses are allowed. For additional tools to manage your workflows efficiently, you can check out RookieSideLoader.

Thank you for your feedback. ​@Roxwell, I had a look at this and while it almost fulfils my requirement it falls short from an Agent perspective. I would be looking to avoid agents from searching for requesters that was outside of the organization's domain. 

Most recent example had an agent send an invoice to an external party for approval instead on internal party because they had the same exact first and last name. 

Thank you for your feedback. ​@Roxwell, I had a look at this and while it almost fulfils my requirement it falls short from an Agent perspective. I would be looking to avoid agents from searching for requesters that was outside of the organization's domain. 

Most recent example had an agent send an invoice to an external party for approval instead on internal party because they had the same exact first and last name. 

Off the top of my head, I can’t think of a way to do that. maybe someone else has solve this one.

Reply


Terms of Use