What approach is recommended to ensure that reports are accessible only to the intended users who own them?

What approach is recommended to ensure that reports are accessible only to the intended users who own them?

• A. Use custom properties and account limitations to control report access
• B. Create separate reports for each user
• C. Share all reports with everyone
• D. Use a single login for all users

Answer: (A)

Controlling who can see each report by tying ownership to the report and enforcing access at the user account level keeps access precise and auditable. Using custom properties to store who owns a report lets you label each report with its owner, while account limitations (such as role-based or group-based permissions) ensure that only that owner or authorized users can view or run it. This approach scales well: you don’t create a new report for every user, and you don’t expose sensitive data to everyone. It also preserves accountability because every access is tied to a authenticated user. In contrast, making separate reports for each user, sharing all reports broadly, or using a single shared login would undermine security and make tracking who accessed what impossible.

Controlling who can see each report by tying ownership to the report and enforcing access at the user account level keeps access precise and auditable. Using custom properties to store who owns a report lets you label each report with its owner, while account limitations (such as role-based or group-based permissions) ensure that only that owner or authorized users can view or run it. This approach scales well: you don’t create a new report for every user, and you don’t expose sensitive data to everyone. It also preserves accountability because every access is tied to a authenticated user. In contrast, making separate reports for each user, sharing all reports broadly, or using a single shared login would undermine security and make tracking who accessed what impossible.