To ensure that each NPM user has exclusive access to the reports they are responsible for, which approach should you use?

To ensure that each NPM user has exclusive access to the reports they are responsible for, which approach should you use?

• A. Use custom properties and account limitations to control report access
• B. Create separate folders with full rights for each user
• C. Allow all users to view all reports
• D. Use a single shared login for all users

Answer: (A)

Controlling who can see which reports is about tying visibility to the user’s identity and responsibilities. Using custom properties to tag each report with the person or group responsible (for example, an Owner property) and then applying account limitations (RBAC) to enforce those permissions is the scalable, secure way to ensure exclusivity. With this approach, you configure the report to respect the custom property and map users to the appropriate role or access rule, so when they log in, they only see the reports assigned to them. Separating folders for each user becomes hard to maintain as the number of users and reports grows, and it risks misconfigurations. Letting everyone view all reports breaks the exclusivity requirement, and using a single shared login is insecure and Cannot be audited to show who accessed what.

Controlling who can see which reports is about tying visibility to the user’s identity and responsibilities. Using custom properties to tag each report with the person or group responsible (for example, an Owner property) and then applying account limitations (RBAC) to enforce those permissions is the scalable, secure way to ensure exclusivity. With this approach, you configure the report to respect the custom property and map users to the appropriate role or access rule, so when they log in, they only see the reports assigned to them.

Separating folders for each user becomes hard to maintain as the number of users and reports grows, and it risks misconfigurations. Letting everyone view all reports breaks the exclusivity requirement, and using a single shared login is insecure and Cannot be audited to show who accessed what.