In what scenarios or usecases , does this apply of usage labels can be implemented at connection level in contrast to dataset and schema level usage labels.
Solved! Go to Solution.
Views
Replies
Total Likes
@kishoremittapalli Great Question, think of this as a granular level access control ( this is equivalent to Object level access control of AJO)
Situations this might become handy.
1) Shared sandbox at enterprise level for multiple Lines of business and fine tuning access to LOB specific flows.
2) Client/vendor access control to set of objects.
3) Developer/Engineers/Tech groups managing important flow(s).
Let me know if you need more details on this.
~cheers,
NN.
@kishoremittapalli Great Question, think of this as a granular level access control ( this is equivalent to Object level access control of AJO)
Situations this might become handy.
1) Shared sandbox at enterprise level for multiple Lines of business and fine tuning access to LOB specific flows.
2) Client/vendor access control to set of objects.
3) Developer/Engineers/Tech groups managing important flow(s).
Let me know if you need more details on this.
~cheers,
NN.
@nnakirikanti Thanks for your reply. To understand better , it means we control at the specific flow for a business or important flows rather than field level.
Thats correct to manage object level access restrictions, We have similar functionality with AJO named "Object Level Access control"
Check this: https://experienceleague.adobe.com/en/docs/journey-optimizer/using/access-control/object-based-acces....
~cheers,
NN.
Views
Likes
Replies