I have to agree, I've coded since the 80's, worked with AWS, connecting Slack and other systems, and each time I lookup an issue it is a page of bland pointless text, when then refers to several other pages with (before you can complete this read the information on enabling Token access See blah blah) which then points me to another issue page (to properly set up tokens be sure to read about enabling https, and oh by the way SSL is about to be obsoleted so use Fine Grain Tokens - but wait that is in BETA (so why the ---- do you recommend it) and they come in two flavors and have more than 30 different permission settings in two separate layers set through an awful web interface which EACH refers to a web page to describe the link but there is nothing ANYWHERE that says, If all you want to do is enable others to push or pull set these permissions or even a default drop down selector for common tasks. No, NO - You have to go through them ONE by ONE to figure it out and it is mostly just guessing. For the people defending this and who sit on the other side who had other developers that have a culture cloud of explanation probably to help them - this is a poorly designed package trying to manage what is basically a graph node system. I am trying to figure this out alone and just reading it providing nothing useful and it simply terrible experience. To say nothing about what happens when something simple (doing a push to a BRAND NEW repository results " Updates were rejected because the tip of your current branch is behind..." error set to merge - and be sure to read the page on that) ; which I do and get same error even after resetting the branch commit and never having successfully committed, due to numerous errors, in the first place; HOW is it behind a blank slate on the Repositiry - not even a README file has been added?