The Duty Status Report display is based on UICs with row-level security.

The Duty Status Report display is based on UICs with row-level security.

• A. True
• B. False
• C. Depends on user role
• D. Depends on date

Answer: (A)

Data visibility is controlled through row-level security tied to Unit Identification Codes. In the Duty Status Report, each row has a UIC, and the security policy maps the current user to one or more UICs. The report engine returns only rows whose UIC matches the user’s authorized set, so you see duty statuses for your unit(s) and not for others. A user’s role can influence which UICs are included in that authorized set, but the mechanism itself is UIC-based row-level security. Date filters inside the report simply narrow the already-authorized rows; they don’t change the underlying access boundary.

Data visibility is controlled through row-level security tied to Unit Identification Codes. In the Duty Status Report, each row has a UIC, and the security policy maps the current user to one or more UICs. The report engine returns only rows whose UIC matches the user’s authorized set, so you see duty statuses for your unit(s) and not for others. A user’s role can influence which UICs are included in that authorized set, but the mechanism itself is UIC-based row-level security. Date filters inside the report simply narrow the already-authorized rows; they don’t change the underlying access boundary.