Skip to main content
ServiceManagement
Availability2021.2 or later

Session Replay Security

Restrict replay by context

Fact-Level Security

Rules per data point

Example: Financial Organization

Separate access by product

Implementation Summary

Test before production deploy
GermainUX provides dynamic, context-aware access controls that determine which users and teams can view specific collected data points—called facts—and Session Replay recordings. Unlike Data Privacy controls, which determine whether sensitive information is collected, masked, or anonymized, Data Security controls who can access the data after it is collected. This enables organizations to restrict visibility according to application context, transaction type, user role, team membership, or other business-specific criteria.

​
Key Capabilities

​
Session Replay Security

Session Replay access can be restricted according to the context of the recorded activity. For example, a financial organization may permit different teams to view sessions involving different financial products or transactions. Custom access logic can be added through the RUM JS initialization script. Use:
The metadata provider assigns the appropriate access information to the recorded session. GermainUX then uses that information to determine which authorized teams can view the replay.

​
Fact-Level Security

Fact-level security applies visibility rules to individual data points, such as:
Custom logic can be added through:
The processor evaluates each applicable fact and assigns its visibility expression before the data becomes available to GermainUX users.

​
Access Expressions

Visibility is defined through team-based access expressions. Team identifiers and expressions should be configured according to the organization’s GermainUX team and authorization model.

​
Example: Financial Organization

Consider an organization in which access to recorded activity must be separated by financial product. The custom security logic evaluates the monitored application context and assigns visibility based on criteria such as:
  • Financial product
  • Transaction type
  • Business function
  • User role
  • Organizational team
As a result, each team can access only the sessions and facts it is authorized to review.

​
Implementation Summary

Test all custom security logic before deploying it to production. Confirm that unauthorized users cannot retrieve protected data through dashboards, searches, reports, exports, Session Replay, or other supported interfaces. This page focuses on access to collected facts and Session Replay recordings. Related capabilities are documented separately:

Compliance, Data Privacy and Security Overview

Compliance, Data Privacy and Security Overview

Data Privacy

Data Privacy

Cookie Consent and User Privacy

Cookie Consent and User Privacy

Certifications and Policies

Certifications and Policies

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.