Jump to content

Control default update visibility per service/catalogue item


Recommended Posts


We operate in a shared instance where the two main areas have differing requirements for the default visibility of updates in the timeline.

One area needs to keep updates visible to the team only as the contents have data sensitivity concerns, other areas need to share updates with their users.

Given the importance of preventing unintentional breaches I can see why the switches that control updates are set to team - eg app.email.routing.rules.default.visibility.update

Would it be possible to give the option to control default update visibility to the services or even catalogue items?

Also, if there is something obvious I have missed please let me know.

  • Like 1
Link to comment
Share on other sites

  • AlexOnTheHill changed the title to Control default update visibility per service/catalogue item

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...