If you are able to get this to work on your domain with the DS_USER function, you don't need to turn on Filter by Email at all. Just put the ACL fitler on the report level and you'll be good to go.
Great @@smithviz and one more thing do we need to give view access to all the stakeholder so that when they access this report that filter will applied?? OR it automatically give the access when mail id matches with our column value?
@@PrakharBharas Once it is set up, only people that have their email address in the database will be able to access the data. Please keep in mind, this is for emails associated with Google accounts. (It doesn't have to be a @gmail.com though).
@@smithviz What if the client email is not associated with Google Accounts. Then how can we share the reports with them? I tried searching the answer but didn't get any. Can you please help?
Everything worked for me initially but when I updated (add to my emails column), it did not refresh to capture the updated emails no matter what I tried. Eventually, something triggered and no one had access up see any data. It was as if it did not recognize my email even though I granted/confirmed my email the first time. It did not recognized any users in the email field. I turned off the filter by email option and voila I was able to see the data again. I’m going to try it again.
Wow. I'm so sorry to hear you had that issue. I haven't ran into that so far. I wonder if it was something with the domain? That's very strange indeed.
great, thank you very much! However, for two people of the same organization the data doesn't display (the have the same domain as everyone. Any idea why?
The only place I have seen this is when the emails are not accurate. Filter by Email is case-sensitive. Make sure the email in the data is the same as the email being used in the domain. For example, some emails might be JSmith@email.com or Jsmith@email.com. If your data has emails with all lowercase (jsmith@email.com) it will not work.
No need for the paid version. It works with some domains and not others. I'm not sure why. If you are unable to get it to work on the account you are using, try another gmail account and it might work.
Thanks for the question. I had a similar issue and I needed to a bit of a work around. I know not ideal, but something you can try is to share the dashboard with another gmail account that you have access for. For example, I shared my work account with my personal account. I then tried to do the same calculated field and it worked on the work account, but no the personal account. No idea why. I went through my account settings and everything, but couldn't figure it out. However, once I set it up on my work account, I was able to use it on my personal account for that report. Not ideal, but a bit of a work around.
@@smithviz My work account (where I need to run this filtering) does not allow me to share outside of our domain. The formula is erroring when I create this field. I just get Invalid Formula. Do I need to set @DS_USER_EMAIL as a parameter?
@@g4sacademyinternational I wish I had an answer for you. I have also had issues with the DS_USER_EMAIL on my private account, but not work account. I have raised a ticket on GDS about this. I'm still waiting to hear back. I will update more once I hear back.
The level of access would depend on the email addresses associated with that row. You could set up a system called an ACL (access control list). You can then use a checkbox system to decide which emails have access to certain groups (G1, G2, etc).
I am having following error Data Studio encountered an error running this report and was unable to send scheduled email to recipients. View the report in your browser to troubleshoot the error.
Try viewing the report to see what it gives you. Also, you might want to check your emails to make sure it is consistent. Emails in data studio are case-sensitive. Check and make sure your capital and lower case letters match up.
Thanks for your question. Based on the tests I have done, yes, it seems to work for gmail accounts or those accounts backed with a Google Workspace domain.
@@inwizyprivatelimited Unfortunately, it seems to work with only Google emails. One work around I have seen is to embed the dashboard into a password-protected site such as Word Press and then have users access the site. It doesn't limit the data in the dashboard to the user, but it does protect it and allow those without Google emails to access it.
@@smithviz Thanks Smith, that's the reason we decided to design our own API's since PBI is license is too much and not a viable solution for large number of users.
Some domains don't work for this. I'm not sure why and I have been trying to figure it out. Google Developers have yet to answer as well. A work around is to share it with a different Google account and test. If it works on another account and you get the green check mark, save the calculated field and then you will be able to use it on the original account even if you have the red mark.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Thanks for this video. It helps me a lot
The ds_user_email tip for multiple email addresses is very helpful
only one word for you
LOVE YOU. the way you teach this is awesome
Man, you just saved my year. thanks a lot
hello from Brazil, ty for you work. you are a savior!
Dear Sir, While using this filter do we need to enable the Filtering by email option under Edit Data source?
If you are able to get this to work on your domain with the DS_USER function, you don't need to turn on Filter by Email at all. Just put the ACL fitler on the report level and you'll be good to go.
Great @@smithviz and one more thing do we need to give view access to all the stakeholder so that when they access this report that filter will applied?? OR it automatically give the access when mail id matches with our column value?
@@PrakharBharas Once it is set up, only people that have their email address in the database will be able to access the data. Please keep in mind, this is for emails associated with Google accounts. (It doesn't have to be a @gmail.com though).
@@smithviz Thank you so much for your help
@@smithviz What if the client email is not associated with Google Accounts. Then how can we share the reports with them?
I tried searching the answer but didn't get any. Can you please help?
Hello from Ukraine! Thank you for your work. It's really useful.
Thanks for the comment. I'm glad you found it useful.
Everything worked for me initially but when I updated (add to my emails column), it did not refresh to capture the updated emails no matter what I tried. Eventually, something triggered and no one had access up see any data. It was as if it did not recognize my email even though I granted/confirmed my email the first time. It did not recognized any users in the email field. I turned off the filter by email option and voila I was able to see the data again.
I’m going to try it again.
Wow. I'm so sorry to hear you had that issue. I haven't ran into that so far. I wonder if it was something with the domain? That's very strange indeed.
Hi I tried, but it is not working for other users, I am not sure why? i did follow the steps
Please make sure you check to see if you are getting the green checkmark when you use the DS_USER_EMAIL function in your calculated field.
You solved my problem today! Many thanks!
Glad I could help!
great, thank you very much! However, for two people of the same organization the data doesn't display (the have the same domain as everyone. Any idea why?
The only place I have seen this is when the emails are not accurate. Filter by Email is case-sensitive. Make sure the email in the data is the same as the email being used in the domain. For example, some emails might be JSmith@email.com or Jsmith@email.com. If your data has emails with all lowercase (jsmith@email.com) it will not work.
@@smithviz Thanks, yes I found that it was written SR@.........
Does this work only on the paid version? I am using the open source google data studio and it did not work
No need for the paid version. It works with some domains and not others. I'm not sure why. If you are unable to get it to work on the account you are using, try another gmail account and it might work.
Thanks for sharing! Getting Invalid Formula in the calculated field: IF(CONTAINS_TEXT(Email, DS_USER_EMAIL()), col_name, "NotForYou") . Any ideas why?
Thanks for the question. I had a similar issue and I needed to a bit of a work around. I know not ideal, but something you can try is to share the dashboard with another gmail account that you have access for. For example, I shared my work account with my personal account. I then tried to do the same calculated field and it worked on the work account, but no the personal account. No idea why. I went through my account settings and everything, but couldn't figure it out. However, once I set it up on my work account, I was able to use it on my personal account for that report. Not ideal, but a bit of a work around.
@@smithviz My work account (where I need to run this filtering) does not allow me to share outside of our domain. The formula is erroring when I create this field. I just get Invalid Formula. Do I need to set @DS_USER_EMAIL as a parameter?
@@g4sacademyinternational I wish I had an answer for you. I have also had issues with the DS_USER_EMAIL on my private account, but not work account. I have raised a ticket on GDS about this. I'm still waiting to hear back. I will update more once I hear back.
@@smithviz Thank you. I can't get it to work on either my private or work accounts
Send me a DM on Twitter @smithrchris I'll see if I can help.
By the way, thank you for this solution!
You have grade column value as G1. All the row has G1. lets suppose i have G1 and G2. G2 doesn't have admin level view. how do i implement that.
The level of access would depend on the email addresses associated with that row. You could set up a system called an ACL (access control list). You can then use a checkbox system to decide which emails have access to certain groups (G1, G2, etc).
I am having following error
Data Studio encountered an error running this report and was unable to send scheduled email to recipients. View the report in your browser to troubleshoot the error.
Try viewing the report to see what it gives you. Also, you might want to check your emails to make sure it is consistent. Emails in data studio are case-sensitive. Check and make sure your capital and lower case letters match up.
thanks brow, your video help meee!!
This works for google e-mails only?
Thanks for your question. Based on the tests I have done, yes, it seems to work for gmail accounts or those accounts backed with a Google Workspace domain.
@@smithviz Is there any way to skip that google login or use it with non-google accounts
@@inwizyprivatelimited Unfortunately, it seems to work with only Google emails. One work around I have seen is to embed the dashboard into a password-protected site such as Word Press and then have users access the site. It doesn't limit the data in the dashboard to the user, but it does protect it and allow those without Google emails to access it.
@@smithviz Thanks Smith, that's the reason we decided to design our own API's since PBI is license is too much and not a viable solution for large number of users.
Not working. Pl help
Hey there. Sorry to hear that. Can you contact me on my website and I'll help you trouble shoot? smithvisualizations.com/contact-smith-visualizations/
when i try to create the CONTAINS_TEXT(email_field,DS_USER_EMAIL()) field, LookerStudio says it is not a valid formula. Anyone else had this problem?
Some domains don't work for this. I'm not sure why and I have been trying to figure it out. Google Developers have yet to answer as well. A work around is to share it with a different Google account and test. If it works on another account and you get the green check mark, save the calculated field and then you will be able to use it on the original account even if you have the red mark.