This was my assumption coming into the manager role: Whoever ends up becoming the Rust manager would be allowed to manage every aspect of the Rust ecosystem, with the possible exception of actual server access (though that was a whole other conversation that needs to be had).
My assumptions were eventually proven to be wildly inaccurate, and that's mostly a failure on my part for not communicating effectively with Garnet.
While I was manager, here were my access levels:
Forums - I could lock/move posts, nothing else. I couldn't edit existing posts to fix errors with things like server rules, chat rules, group/roaming sizes. etc. The only thing I could do was accept or deny applications.
Discord - I could kick users. Nothing else. I couldn't create staff channels in Discord (which I wanted to do), or fix existing channels (when bots broke, for example), or ban people spamming chat with racial slurs/@ing every role possible. I couldn't assign roles to existing or new moderators. I couldn't even edit the post in the #-reports-and-appeals channel to fix the link so users could actually report someone.
In-game - I had moderator access on 1 out of 5 servers. On the other servers, I had 0 permissions (in-game) and didn't even have the moderator title.
BattleMetrics - this is server-side access to ban/mute. I could ban for various time frames and specific servers and give reasons, or I could permanently mute someone (no option to give a reason or time frame). I had no access to any other admin commands or permissions inside or outside the game.
I couldn't assign roles to new moderators in Discord, or give them permissions myself in Rust, so every person I hired had absolutely no power to do anything except take screenshots, send them to me, and hope I was online. Of my 4 pre-existing moderators, 3 of them had moderator access on the 1000x . Of those 3, only 1 had access on any other server (Sierra 2x and the 5x).
Again, these were all things I assumed I would be able to fix fairly quick, based off of what I thought my role should have been able to do - not what Garnet had in mind when he hired me. Another point of failure on my part with the communication between myself and Garnet.
Garnet has his reasons for wanting to keep permissions the way they were, but as you can see - I had no power to make any changes for the actual community. Only Garnet has that power, and he's incredibly busy both in the real world and with GMod. I tried my best to keep communication open with him, I filled our Steam chat with permission fix requests, forum suggestions, discord requests and more before I finally created a shared doc, but by the time Garnet posted his thoughts here it was obvious to me (at the time) that I had failed to communicate everything effectively and that it didn't seem to have improved at all over the last month.
My inability to communicate well with Garnet was a barrier that I didn't see being overcome quickly, so instead of continuing down that path and possibly holding back the community and the mod team, I stepped down.
I have all the respect possible for Garnet and the work he has to do (and all the work he doesn't have to do, but does because of the community). I enjoyed the times we were able to chat and work together. I still play almost exclusively on Garnet servers, I still try to contribute to the community, and I still make sure I'm available to the mod team for any questions they may have or as a sounding board for ideas and suggestions they have. I enjoy this community and hope to be around to see it grow.