You're lucky if you got an access to everything you need on day 1, not to mention setup the tooling.
You can't improve the product if you don't know it yet and that takes time.
I try to have folks delivering business value even if very small within a week or two. I find it reduces a lot of new hire anxiety around performance if they can ship _anything_ relatively quickly.
In a different sector, 20-30 people is the stage where you should be capitalizing on how much faster you can move than the large bureaucratic incumbent, and if there's red tape that takes weeks to navigate it means someone in the company put it there.
I am aware of that; I like it that way. I like long term stability and large bags of money without stress.
The capitalising and ‘faster’ and hurry and stress you speak off is nice if you want bankrupt-or-unicorn. We don’t need to be market leader or whatever; we need to have stability decade after decade and we do. I like profit of millions$/year and small teams, not some breakneck VC funded fast growing all-or-bust stuff. Each their own of course.
While I don't think as a blanket rule a new hire should push prod code on day or week one—they should be able to without being ham-stringed by needless bureaucracy that has nothing to do with security or engineering. (IMO)