I think if you look at the way you've created the user stories, you should also fall into natural groupings / categories based on the user's goals, at least if you're writing them from a user-centric perspective. Therefore, depending on these groupings, you may need to "prepare" them so that business analysts and developers can translate them into technical and commercial requirements (or you may need to adapt user requirements).
Typically, user stories help bridge the gap between the user's perspective and existing business rules / requirements, as well as technical limitations, but business analysts and programmers do not see things from a user's point of view. . Instead, they usually align the documentation 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 of the people who need this information and structure the stories of the users so that they adapt to the way they are going to break down the work. Of course, you will have your reference point from the user's perspective, but you will need a systematic way of assigning them to business or technical requirements.
Given some of the categories you mentioned, this sounds like a business system and for me the categories reflect some of the users and use cases that make up the main functionality of the system. So, by all means, try to work with analysts or business developers to categorize and develop user stories so they can go back to working on functional specifications.
For example, the development of user types and the functions they perform inform developers of the access rights and permissions that must be implemented (in accordance with commercial rules). Another example could be to determine if a particular characteristic that will be implemented is fundamental for the system (that is, that all users must perform) or specific for a type of user. These are all logical classifications that can help developers estimate the effort required and project managers to create a project timeline / schedule.