Highlighted

How could I prevent a user publishing his own change?

Bronze Contributor
Bronze Contributor

We have a case where we a small team want to be able to manage their changes and updates to Tealium but interal rules state that an individual can not publish their own changes.

 

Is it posisble, or could it be made possible, to give two users publish to 'prod' but, like workflow, it needs approval (a second user) to publish the first users change?

3 REPLIES 3
Highlighted

How could I prevent a user publishing his own change?

Employee Emeritus

@alex_sandrey

What you are asking for is not 100% possible with Tealium.  However we have many clients with governance requirements that are similar to yours.  Might I suggest that you pick 1 or 2 people that can publish to Production.  All other people can only publish to DEV/QA.  Then have your internal review process and only one of these two people can check the final box and push the changes to Production.

 

Thoughts?

 

Brian 

Highlighted

How could I prevent a user publishing his own change?

Bronze Contributor
Bronze Contributor

@brian_kranson

Thank you for the reply. That is the process we are currently taking with limited 'publish to live' user access and an internal tool being used to provide that review details.

 

How would it be possible to start talking about this as a customer feature request?

Highlighted

How could I prevent a user publishing his own change?

Employee Emeritus

@alex_sandrey

New feature requests need to go through your Tealium Account Manager.  Please reach out to them via phone/email to discuss the details.