Hi there, @caseys… I’m not sure if I understand your post because it seems like if a user’s role is Finance, they will never see the Authorization document type, and that means they could never have selected it in the first place so it can’t be the default value for them.
The above being said, it sounds like you don’t want to remove Authorization from the dropdown when a user’s role is Finance, but you don’t want them to be able to select that type. Is that the case? If it is (and for what it’s worth, I don’t think that would be such a good UX), you could consider using the An input’s value is changed workflow event to show the user a message when they select the Authorization type saying they can’t select that type because of their role. Now, if I am the user and I see that message, I immediately think, “Okay, then why in the hell did you put the type in the dropdown if I am not allowed to select it?!?”, but maybe that’s just me.
So a finance user needs to be able to interact with a purchase order that has a “status” of authorization, and the dropdown would need to be able to display that status even though the finance user should not be allowed to ever select that option themselves. Is that correct?