SAP Solution Manager 7.2 · Solution Documentation: Architecture & Config

What does an authorization group control in Solution Documentation, and what are its rules?

It pushes permission checks down to the object/attribute-type level, differentiated by solution — checked via the SM_SDOC object's SMUDAUTHGR field.

Rules: the default group (*) holds everything not assigned to a named group; an object/attribute belongs to only one group (groups are mutually exclusive); the technical name is 30 chars and can be hierarchical (e.g. OBJ_LIB_TECH_*) for bulk authorization.

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 Solution Documentation: Architecture & Config

How can you extend Solution Documentation for better governance reporting?
How do digital signatures work for Solution Documentation documents, and what must be active first?
Attribute-level authorization in Solution Documentation only checks one action — which, and what can't you do with it?
What three template users does SAP preset for Solution Documentation, and what can the admin one do?
What does 'Generate Library' do in Solution Documentation, and what does it distinguish between?
What does an authorization area protect, and how is its assignment determined?