Skip to main content

How to Exclude Specific Users From Being Recorded in Fullview

A
Written by Alex
Updated this week

In some cases, you may want to prevent Fullview from recording session replays for certain users. Common examples include internal team members, QA testers, or specific user roles. Fullview supports this through the disableReplaysForUser field, which you can set dynamically when sending Fullview the user's properties.

This article explains how to use that setting in your implementation.

Overview

Fullview captures session replays after a user is identified through the window.$fvIdentity object. By adding the optional disableReplaysForUser flag, you can instruct Fullview to skip recording for any user that matches your conditions.

You control the logic. Fullview simply respects the value you provide.

How It Works

Before you call window.$fvIdentity, run whatever logic you need to determine whether a session should be recorded. Then set:

  • disableReplaysForUser: true → Fullview will not record this user

  • disableReplaysForUser: false → Fullview will record this user

If the field is omitted, the default behavior is to record sessions normally.


Example: Only Record Admin Users

In the example below, only users with the admin role are recorded. Everyone else is excluded.

if (userRole !== 'admin') 
{
window.$fvIdentity = {
id: 'USER_ID',
name: 'USER_NAME',
email: 'USER@EMAIL.COM',
disableReplaysForUser: true
};
}

else
{
window.$fvIdentity = {
id: 'USER_ID',
name: 'USER_NAME',
email: 'USER@EMAIL.COM',
disableReplaysForUser: false
};
}

This same pattern works for any type of filtering: roles, email domains, environments, feature flags, or any custom logic you maintain.

When to Use This

Customers typically use disableReplaysForUser to:

Exclude internal users from recordings

  • Prevent session capture in staging or development environments

  • Avoid recording high-privacy user segments

  • Ensure compliance with internal or external data policies

  • Avoid excessive recording volumes

You can freely extend the example above to support multiple conditions.

Important Notes

  • The filtering logic must run on your side, before you call the Fullview identification snippet

  • If disableReplaysForUser is set to true, Fullview will completely skip session replay recording for that user

  • Users with disableReplaysForUser: true will still appear in Fullview, and you can still cobrowse with them, but no session replays will be captured for those users

Summary

By controlling disableReplaysForUser in your identity snippet, you can precisely decide which users Fullview should and should not record. This gives you flexibility to comply with internal workflows, legal requirements, or privacy needs—without changing anything in your Fullview dashboard.

Did this answer your question?