Tealium Learning Center

@mike_andersonThe problem with resource lock is that it is just for tat particular tag, I can simply deploy another tag. Example: Marketing can come and deploy Google Analytics tag in their library, there is nothing to stop them from doing so. yes they cannot modify a tag that we might have created for Google Analytics, but because company policy allows Google Analytics they can use it. We want to be able to limit what vendors are different people allowed to deploy. This can be handled either through user level permissions or based on a library permissions. The need to deploy a whole profile is the reason we are separating different teams within different libraries which all link to a main profile.   It seems like this was not linked ot what I was replying.. and i did not see away tolink to your reply.. so it was to your reply to my question here: Features we would like to see: Ability to specify environment permissions on per user and profile level Right now vendors are assigned on account level. We would like to be able to assign vendors on profile level, while still abiding by the account level functionality Why: We want to limit certain users to only have access to deploy certain tags. And no, tags do not work, because tags are on an individual tag level which means that as a marketer I can still deploy an analytics tag because the account provides it.We should not allow a marketer to deploy analytics tags and this is currently possible in the platform ... View more

We just started with Tealium and we are finding that current permissions and locking capabilities are not enough for our use cases. As GDPR is coming in fast, we are trying to ensure that the platform is setup with more controls around who can do certain things in the platform. Are there plans on enhancing capabilities so companies with more users and complex permissions have better control over the platform?   Features we would like to see: Ability to specify environment permissions on per user and profile level Right now vendors are assigned on account level. We would like to be able to assign vendors on profile level, while still abiding by the account level functionality Why: We want to limit certain users to only have access to deploy certain tags. And no, tags do not work, because tags are on an individual tag level which means that as a marketer I can still deploy an analytics tag because the account provides it.We should not allow a marketer to deploy analytics tags and this is currently possible in the platform Vendor permission on profile/user/user group level Right now if a person has permissions to deploy to one profile to prod they can deploy any profile they have access to , which does not work for a couple of reasons: We have PCI compliant profiles that need to go through special review with our PCI compliance team. Only approved individuals should be able to deploy to prod for this profile We do not want to centralize deployment as we will have too many stakeholders and systems, and we want to enable marketers to deploy their own tags Limit what data layer elements are used on user/user group level We need to ensure that personal data is not sent to vendors outside of the ones allowed. To ensure this we need to be able to limit which elements are used by users. Right now you can only limit editing the data layer with labels but that does not prevent people from sending data to vendors Limit extensions that can be used on user/user group level And yes I just copied and pasted what I sent to Tealium as a question as well, but would love to hear feedback from Mike. I would also love to hear feedback from other platform users and understand if we are the only ones struggling with this   Thanks, Prolet ... View more