Secure the Data Access

public with sharing class AccountHealthService {
    // ...
}

1. public with sharing class AccountHealthService { — with sharing added explicitly, not left to the default.
2. // ... — the methods from the previous lesson, unchanged.
3. } — closes the class.

Applying Module 30's "Secure Data Access" question directly: does this dashboard need to see Cases or Contacts the running user couldn't normally access? No — a support manager viewing a dashboard should only ever see health data for Accounts they already have access to. with sharing is the clear, deliberate choice.

public Integer getOpenCaseCount(Id accountId) {
    if (! Schema.sObjectType.Case.isAccessible()) {
        return 0;
    }
    return [SELECT COUNT() FROM Case WHERE AccountId = :accountId AND IsClosed = false];
}

1. public Integer getOpenCaseCount(Id accountId) { — the method from Lesson 2.
2. if (! Schema.sObjectType.Case.isAccessible()) { — Module 28's CRUD-check pattern, asked before touching the object at all.
3. return 0; — a graceful fallback, not an error, when the running user lacks Case read access.
4. } — closes the if.
5. return [SELECT COUNT() FROM Case WHERE AccountId = :accountId AND IsClosed = false]; — unchanged from Lesson 2, now only reached once access is confirmed.
6. } — closes the method.

This is Module 28's CRUD-check pattern, applied to a genuinely realistic scenario: a user with dashboard access but no Case object permission shouldn't see a broken component — returning 0 gracefully (rather than a permissions error) keeps the dashboard usable even for a user with narrower access.

public Decimal getTotalWonRevenue(Id accountId) {
    List<Account> accounts = [
        SELECT Total_Won_Revenue__c FROM Account WHERE Id = :accountId WITH USER_MODE
    ];
    if (accounts.isEmpty()) {
        return 0;
    }
    return accounts[0].Total_Won_Revenue__c == null ? 0 : accounts[0].Total_Won_Revenue__c;
}

1. public Decimal getTotalWonRevenue(Id accountId) { — the method signature.
2. List<Account> accounts = [ — a List, not a single Account, deliberately.
3. SELECT Total_Won_Revenue__c FROM Account WHERE Id = :accountId WITH USER_MODE — Module 28's WITH USER_MODE clause, enforcing field- and object-level security automatically for this query.
4. ]; — closes the query.
5. if (accounts.isEmpty()) { — covers both "no such Account" and "Account exists but the field/object isn't accessible to this user" — WITH USER_MODE simply omits inaccessible results rather than throwing.
6. return 0; — the same graceful zero used throughout this service.
7. } — closes the if.
8. return accounts[0].Total_Won_Revenue__c == null ? 0 : accounts[0].Total_Won_Revenue__c; — the field itself can still be blank on an existing Account, so null is handled separately from "no access."
9. } — closes the method.

Module 28's WITH USER_MODE handles field-level security automatically for this query, rather than manually checking Total_Won_Revenue__c.isAccessible() — and switching to a List query (instead of assuming exactly one record) means a user without access to any matching Account, or the field itself, simply gets an empty result instead of a runtime error.