From what I've read and learned about scrum from my recent reading, as well as years reading the great questions and answers on this site, a scrum team is a team of equals, where there's no hierarchy, and knowledge is shared vigorously.
Is it still possible that some members of the team may have specific access to a set of resources which others do not? For instance, a database expert on the team may have the ability to run SQL queries against the live, production database, but one might not want everyone on the team to be able to do this who isn't trained in SQL. Is this a correct way of thinking, or would we give unrestricted access to all on the team and warn them not to break stuff?
What about simpler things, like the team's Slack instant messaging system? It's arguably much harder to break Slack (or Sqwiggle, gitter.im, or any other instant messaging system). Would it be expected that everyone be an admin to this system, or would a specific individual serve as the admin?
I am concerned about things like this because they could inadvertently preserve some of the pre-scrum hierarchy that exists prior to moving to the scrum framework. What is the best way to approach these things on a new scrum team which was previously non-scrum?