Assign the profile (in the console) to an SBMS Group (creating it if you have to). The profile will then be broadcast to any Users that are configured members of that Group (which might be 'only' or 'amongst others'). Whether they can run it (and how) is controlled by the Security profile assigned to the user in SBM (and what that Security Profile is configure to permit)
For example, I have an uploaded profile called TestDoNothing. That profile has been assigned to Group1
I have a user called Admin who has also been assigned as a member of Group1, so he will get that TestDoNothing profile in due course
User=Admin has been assigned the Security Profile 'Anything' (created with all available privileges), but you could also create others for different 'levels', call them what you like and cherry-pick the various available privileges)
Basically, Groups, Profiles, Security Profiles and Users are all inter-related in SBM, and you need to grasp the connections between them and create the relationships. Yes, it's complex, because it's very configurable/flexible - you cannot have one without the other, unfortunately
For example, I have an uploaded profile called TestDoNothing. That profile has been assigned to Group1
I have a user called Admin who has also been assigned as a member of Group1, so he will get that TestDoNothing profile in due course
User=Admin has been assigned the Security Profile 'Anything' (created with all available privileges), but you could also create others for different 'levels', call them what you like and cherry-pick the various available privileges)
Basically, Groups, Profiles, Security Profiles and Users are all inter-related in SBM, and you need to grasp the connections between them and create the relationships. Yes, it's complex, because it's very configurable/flexible - you cannot have one without the other, unfortunately