1. Row & Column-Level Security advanced

    A data platform must enforce that analysts see only permitted rows and columns across thousands of tables and hundreds of users. How should this be designed so it is enforceable and auditable?

    2 min answer access-controlabacmaskinggovernance
  2. Row & Column-Level Security advanced

    A financial platform must restrict which rows and columns each analyst can see. Where should that be enforced?

    2 min answer razorpayrlsaccess-controlenforcement
  3. Row & Column-Level Security advanced

    Design field-level and record-level access controls for a business application where each customer configures their own rules.

    1 min answer rlscolumn-securitypolicymulti-tenancy
  4. Row & Column-Level Security advanced

    Row-level security on the orders table restricts each regional analyst to their own region. An audit shows a Berlin analyst's dashboard returning French rows. The policy is present and correct on the table, the analyst's attributes are right, and the query in the dashboard selects from `orders_summary`. What happened?

    3 min answer rlsmaterialised-viewspolicy-bypassaudit
  5. Row & Column-Level Security advanced

    Salesforce's published Force.com design keeps many customers' records in shared tables described by metadata, rather than giving each tenant its own schema. Weissman and Bobrowski's SIGMOD 2009 paper describes the platform supporting tens of thousands of organisations this way. What does that choice force about access control, and where would copying it be a mistake?

    2 min answer salesforcemulti-tenancyrow-level securitymetadata