From an Identity Governance and Security Posture point of view, having BrightGauge Viewer access tied to the client's own IAM platform, which follows their joiner, mover, and leaver process, is a significant win.
It directly reduces the administrative overhead of answering "what are my potential data leakage areas?"
If a client employee leaves and their account is deprovisioned in their own IdP, that access is automatically revoked.
Without SSO enforcement, you're relying on manual processes, or worse, hoping someone remembers to remove a viewer who no longer should have eyes on that data.
The friction of onboarding clients as guest users is a one-time cost.
The risk of ungoverned external access to client-facing dashboards.
From an Identity Governance and Security Posture point of view, having BrightGauge Viewer access tied to the client's own IAM platform, which follows their joiner, mover, and leaver process, is a significant win.
It directly reduces the administrative overhead of answering "what are my potential data leakage areas?"
If a client employee leaves and their account is deprovisioned in their own IdP, that access is automatically revoked.
Without SSO enforcement, you're relying on manual processes, or worse, hoping someone remembers to remove a viewer who no longer should have eyes on that data.
The friction of onboarding clients as guest users is a one-time cost.
The risk of ungoverned external access to client-facing dashboards.