What’s the order of precedence for channel invitation preference?

Can anyone explain how the channel invitation preference work?

I know there are user-level and application-level setting but what precedence does it have each other?

@postit Thanks for your question.

Order of precedence : Most Specific to least specific takes precedence

  1. Create channel invitation status
  2. User-level setting
  3. Application-level setting

channel creation endpoint allows for invitation_status
The application setting is passed to user setting when user is created. However, application and user level setting is about auto-join, on the contrary, you can directly set invitation status through API.
When you do that, the auto join setting is override by invitation_status