Security Implementation in Dashboards

In analytics dashboards, applying security ensures users only access data they are authorized to view. However, enabling security for all datasets and dashboards can affect overall performance. To improve performance, security is removed from most datasets and dashboards. Applying security across all dashboards and datasets can negatively affect performance.

This topic explains the steps to implement security for dashboards where it is required. When duplicating or creating a custom dashboard, you can apply row-level security by using the appropriate security datasets.

When to Apply Security

• Apply security only to dashboards that require restricted access to sensitive data.
• Use security datasets to enforce row-level security for specific asset types or business needs.

How to Implement Security

To implement row-level security in your dashboards:

1. Identify which datasets in your dashboard require security.
2. Add the relevant security dataset(s) to your dashboard.
3. Blend or join the security dataset with your target dataset using the appropriate attributes.
4. Add the security flag as a global filter and set its value to 'Y'.
5. Test your dashboard to ensure users see only the data they are authorized to access.

Security Datasets

Use the following topics for detailed, step-by-step instructions and example use cases:

• Agility security dataset
• CT security dataset
• Release security dataset
• Deploy security dataset
• TeamForge security dataset

Refer to these topics whenever you apply security to duplicated or custom dashboards. Each topic provides guidance tailored to the specific dataset and includes example scenarios to help you implement security effectively.