SAC Security
SAC Security covers how SAP Analytics Cloud governs who can log in, what they can see, and what they can do across stories, models, and data. It spans identity/authentication, role-based application authorizations, team-based content sharing, and data-level (row/column) security enforced through data access controls tied to models, dimensions, and connections such as SAP Datasphere or live HANA sources.
Overview
SAC Security covers how SAP Analytics Cloud governs who can log in, what they can see, and what they can do across stories, models, and data. It spans identity/authentication, role-based application authorizations, team-based content sharing, and data-level (row/column) security enforced through data access controls tied to models, dimensions, and connections such as SAP Datasphere or live HANA sources.
Lessons in this topic
- SAP SAC Security Tutorial (Part 1)Introduces the foundational SAC security model: users, roles, teams, and how application-level authorizations control access to features, folders, and content objects.
- Data-Level Security in SAC: Data Access Controls and Row-Level Restrictions (Part 2)Explains how SAC enforces data-level (row/dimension-based) security using Data Access Controls tied to teams or users, and how this interacts with underlying source systems like SAP Datasphere.
- Designing Row-Level Data Access Control in SAC Models (Part 3)Learn how to implement row-level (data-level) security in SAC using Data Access Control objects on planning and BI models, and how this interacts with role-based object security.
- Advanced SAC Security: Roles, Teams and Data Access Control (Part 4)Design SAC security across platform roles, teams, model permissions and data access so users see only the planning or analytical data required by their business responsibility.
Interview questions covered
- What are the core concepts of SAC Security, and how would you explain them clearly in an SAP interview?
- How would you apply SAC Security in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in SAC Security. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in SAC Security?
- Suppose you inherit an existing SAC Security solution. How would you review it before making a change?
- A senior architect is reviewing SAC Security. The project situation is: Regional planners shared one planning model. What design changes, validation evidence and production controls would you require before approving the solution?
- Using this SAP project situation — A finance transformation project onboarded 40 planning users across three regions — explain SAC Security Fundamentals: Users, Roles, and Application Authorizations. What should happen, which concepts or process steps matter, and what common mistake would you avoid?
- A project encounters this situation while working on Data-Level Security in SAC: Data Access Controls and Row-Level Restrictions: A retail client consolidated regional sales planning into one shared SAC model to reduce maintenance. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- A project encounters this situation while working on Designing Row-Level Data Access Control in SAC Models: A retail client rolled out a single SAC sales planning model to 40 regional managers plus a small central finance team. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.