Several types of RPI channel require to be authorized before being saved and used. Each channel’s authorization process is unique and is described individually. If you attempt to authorize a channel prior to the provision of its mandatory properties, a warning is thrown. Note that you can save a channel prior to its authorization, but if you attempt to utilize it in an interaction workflow, a runtime validation error will be thrown.