I think if you look at the way that you have created the user stories, they should also fall into natural groupings/categories based on the user's goals already, at least if you are writing them from a user-centric perspective. So based on those groupings, you may need to 'prepare' them in a way that the business analysts and developers are able to translate them into business and technical requirements (or maybe you are needing to fit the user requirements into them).
Typically users stories help to bridge the gap between the user's perspective to the existing business rules/requirements as well as the technical constraints, but business analysts and programmers don't see things from a user's point. Instead they normally align the documentations and specifications from the system's point of view, and that is possibly the purpose of the categorization exercise for you.
Without having the exact context, my advice is to consider the needs for the people who need this information and structure the user stories so that it fits into the way they are going to break down the work. Of course, you'll have your point of reference from the user's perspective, but you'll need a systematic way of mapping them back to business or technical requirements.
Given some of the categories you have mentioned, this sounds like an enterprise system and to me the categories reflect some of the users and use cases that form the main functionality of the system. So by all means try to work with the business analysts or developers to categorize and flesh out the user stories so that they can be reworked into functional specifications.
For example, fleshing out the user types and the functions they perform informs the developers of the access rights and permissions that may need to be implemented (according to business rules). Another example might be working out whether a particular feature to be implemented is core to the system (i.e. all users need to perform) or specific to a user type. These are all logical cateorization that can help developers to estimate the effort required and project managers to create a project timeline/schedule.