Feature Request P2
Status Update
No update yet.
Comments
jg...@fmlogistic.com
sono totalmente d'accordo con voi
rb...@fmlogistic.com
I agree.
es...@fmlogistic.com
yes
ll...@fmlogistic.com
Agree, a vote from me as well.
ol...@fmlogistic.com
definitely needed
ak...@google.com
Unfortunately labels are not designed to store sensitive information.
But we do understand the spirit of this request - it would be nice to track cost associated with different users, even when they used owner's credentials. We will see what can be done here.
Current recommendation is to not use owner's credentials. That way you can use user_email field in information_schema.JOBS view. See schema:
Description
(Owner's Credentials,Viewer's Credentials, Service Account),
can store the viewer's email in the labels (as already happens for the LookerStudio asset_id).
In this way it would be possible to have the information for the breakdown of costs even in cases where the user does not has direct access to data on bigquery