Best practice for sending email to an external user at a company address


Badge

If an external person needs to be able to receive at an @company.com address, but without paying for a user or giving them google access, what’s the preferred method of everyone? Content Compliance Rule? Group? Custom Cloud Role?


12 replies

Badge

Personally I would do a mail routing rule for that


Open Thread in Slack
Badge

You have to map it to another email in that case though, and they wouldn’t be able to send from that email


Open Thread in Slack
Badge

That’s how I’ve previously done it but just wanted to do a sanity check as I’m just getting back into Google admin after not for awhile


Open Thread in Slack
Badge

Yeah, we only want them to receive and not send


Open Thread in Slack
Badge

Yeah, then I think that would be the easiest way. I suppose if you’re only receiving and not sending, then a group should also work


Open Thread in Slack
Badge +1

We use groups for this purpose. Create a group and and the external users email and your done.


Open Thread in Slack
Userlevel 2
Badge +2

Just remember to set a reminder when that external person is done to remove the group/email. 😬



Open Thread in Slack
Badge

It looks like for this usecase, they actually need to SSO via Google into an app. Is there a way to do this while avoiding a gsuite user cost?



Open Thread in Slack
Badge

Cloud Identity Free will get you Oauth access



Open Thread in Slack
Badge

Hmm, I guess I need our reseller to add that, it doesn’t show we have that under licenses



Open Thread in Slack
Badge

Yeah, your reseller should be able to add those pretty easily!



Open Thread in Slack
Badge

just a warning: If the user is able to receive emails he may also be able to send them as well via gmail "send as"



Open Thread in Slack

Reply