We are sorry, but you do not have access to...

Reply
minmanw
Neighbour

Ever since merging with Google with our business accounts I have slowly lost access to free Google Services. Clients can no longer send us any Google Document links since I no longer have access to Google Documents. Today, I lost access to Google Maps (which is a free service!). This is so infuriating. I've contacted Telus directly regarding this, and they have done nothing to help me. We had zero issues using Google Services before the Telus merge as we had created our Google Account prior to the merge.

 

Anyone else run into this problem and has it ever been resolved?


Accepted Solutions
Most Helpful
HSL
Connector

I might add, tentatively, that this issue appears to be a consequence of a group administrative setting that Telus *should* be able to turn off.

 

 

View solution in original post


All Replies
xray
Guardian

You need to log on to google services using your gmail account ( [your account] @ gmail.com ) not your Telus account. Your Telus email account is not a Google account, it's a Telus email service running on the GMail platform.

 

If you had previously used your Telus email address as your Google account email then you need to change your Google account email address to a GMail one.

https://support.google.com/accounts/answer/19870?co=GENIE.Platform%3DAndroid&hl=en

 

minmanw
Neighbour

My Telus account was a Google Account before the merge. My clients sent me PDF files all the time no problem. I've never had issues, until Telus took over. You do not need a Gmail account to access Google Services.

 

https://support.google.com/accounts/answer/27441?hl=en

"Tip: You don't need a Gmail account to create a Google Account. You can use your non-Gmail email address to create one instead."

 

This is unacceptable on Telus' part. I should be able to access a PDF link my client send me to download.

HSL
Connector

"Your Telus email account is not a Google account, it's a Telus email service running on the GMail platform."

 

It's a "Telus branded" Google Account.

 

I have set up Google Workspace on my Telus branded account.

 

This error message will occur if you are accessing your account via Webmail and try launching Google Maps in a new browser tab.

 

It can be avoided by launching a new "inPrivate" browser tab and running Google Maps from there.

Most Helpful
HSL
Connector

I might add, tentatively, that this issue appears to be a consequence of a group administrative setting that Telus *should* be able to turn off.

 

 

View solution in original post

minmanw
Neighbour

Yes, I'll have to contact them. The most important feature is Google Documents. As a printing company, we constantly have clients sending us Google Document links, which I can't even access now. I don't want to have to tell each client who sends us a Google Document link they have to now send it to an alternate email address.

 

I'll have to contact Telus again directly (again...) and see if this can be fixed. I cannot change anything on my end that I have found or has been shared here to allow access to these features. Seems so silly they would block these features when anyone with a Google Account (not only Gmail account holders) can use them.

 

Who thought merging with Google would create so many extra headaches...

Upcraft
Ambassador
Likely better if you have customers email you links to a company email address instead of the telus.net one.

Should be no reason to use isp email address for business use. Just forward the telus.net account and setup an autoreply telling people still using it to change their contacts to you business email account. That way you can look more professional with your own emails.

HSL
Connector

The Telus.net eMail services are being migrated to the Google Gsuite / Workspace platform. This is the Google business suite offering.

 

As such .. it is *extremely* likely that Telus has administrative and group policy rights over the Telus branded Gsuite / Workspace domain.

 

The problem described above appears to be a misapplication of a group policy. It is an error and should be easily fixable.