Workaround transaction authorizations
Some projects have security policies that are so tightened, so the developers’ hands are tied and even the simplest tasks can’t be completed. One of the typical approaches is to restrict the transactions that the developers are allowed to execute.
I had such a situation in one of my projects – transaction SOST was restricted and it was challenging to see if the emails are being sent to the right people and if the email body looks as expected. A nice workaround I learned about this situation is to just execute transaction SE37 and start FM RS_HDSYS_CALL_TC_VARIANT with the TCODE parameter set to the transaction I want to execute and the AUTHORITY_CHECK attribute set to false.