SAP Solution Manager 7.2 · Managing Security

How are SolMan roles structured, and why does copying SAP roles into your namespace add upgrade work?

Single + composite roles by functional area and access level (read-only/execute/admin). Three user types: administrator (mandatory config), configurator (tool-specific config — a ChaRM-config person can't touch application operations), user (end-user role templates).

Copying SAP roles into your namespace adds upgrade work because composite roles are continuously updated each SP stack → every upgrade requires planning remediation effort.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app. We’re in private beta now; iOS & Android are coming soon.

Join the private beta

Already a tester? Sign in →

More in Managing Security

How is the SAP Web Dispatcher configured for SolMan, and how does one support multiple backends?
How do you securely expose Fiori apps externally, and why never connect directly to SolMan?
What does the User administration tool do, and what are its three tabs?
What's a common SolMan security pain point, and who should own SolMan authorizations after configuration?
What are the two options for creating SolMan roles, and which has the least maintenance?
How is Fiori security structured, and what's special about the SAP_SMWORK* roles?