Skip to main content

What Does an End-User See on Another End-User’s Teamflect Profile?

Learn what information regular users can view on others’ profiles to ensure privacy and clarity.

Written by Denzel
Updated over 3 weeks ago

Overview

In Teamflect, data visibility is carefully designed to protect employee privacy while still promoting collaboration and transparency where appropriate.
Regular end-users (non-managers and non-admins) have restricted access to others’ profiles.

They can only view public or interaction-based information — never private performance data or feedback from others. This article outlines exactly what a regular end-user can and cannot see on another end-user’s Teamflect profile.

What Data Can a Regular End-User See?

Regular end-users can only see specific data types, which are generally public or related to their direct interactions with the other user.

Summary of Access Rights:

  • Public Information: Basic user details like Job Title, Email, and Public Goals are visible to all users.

  • Private Data: Private Goals, Recognitions, Feedback, and Notes taken by others are not accessible.

  • Interaction-Specific Data: Users can view 1-on-1 Meetings, shared tasks, and feedback they've given to others.

Here's a breakdown of each module or functionality and the data visibility:

Item / Module

Visible to Regular End-User?

Notes

Job Title & Email

✅ Yes

Basic information visible to all users

Public Goals

✅ Yes

Only goals marked as “public” are viewable

Private Goals

❌ No

Hidden from everyone except the creator, manager, and admins

1-on-1 Meetings (with the user)

✅ Yes

Only meetings involving both users

Tasks (shared between users)

✅ Yes

Shared or co-assigned tasks are visible

Tasks Assigned to the User Individually

❌ No

Hidden unless assigned jointly

Reviews

❌ No

Confidential and only visible to review participants

Surveys

❌ No

Survey responses are always private

Feedback (you gave to them)

✅ Yes

Only feedback you personally submitted

Feedback from Others

❌ No

Hidden to maintain privacy

Recognitions (Public)

✅ Yes

Company-wide recognitions are visible

Recognitions (Private)

❌ No

Visible only to sender, receiver, and admins

Notes (you took about them)

✅ Yes

Visible to you within the Notes module

Notes by Others (about the same user)

❌ No

Private to the note-taker

Shared Notes (from Meetings)

✅ Yes

Visible to meeting participants only

Private Notes (from Meetings)

❌ No

Visible only to the note-taker

User & Role Info (set visible by admins)

✅ Yes

Controlled by admin configuration

User & Role Info (set hidden by admins)

❌ No

Not accessible

9-Box Evaluations

❌ No

Reserved for admin and leadership use

Notes vs. Meetings — Visibility Clarification

  • Notes Module:

    • Notes between two users (User A and User B) are visible to both parties.

    • Notes created by a third user (User C) about another person remain private to the creator.

  • Meetings Module:

    • Shared Notes: visible to all meeting participants.

    • Private Notes: visible only to the person who wrote them.

🔐 Privacy Principle: Teamflect follows a least-privilege access model — employees only see what they need to collaborate effectively.

HR Use Cases

  1. Maintaining Confidentiality in Reviews & Feedback
    HR teams can reassure employees that feedback and performance reviews remain private, encouraging honest and constructive input.

  2. Transparency Without Overexposure
    End-users can still view public recognitions, goals, and shared tasks — fostering collaboration while safeguarding sensitive information.

  3. Privacy-Compliant Audits
    HR administrators can reference this structure when explaining or auditing visibility settings for compliance or data-protection purposes.

Final Thoughts

Understanding end-user visibility in Teamflect helps create a trust-based environment where data is protected, and collaboration remains efficient.
By defining clear privacy boundaries, Teamflect ensures every employee can engage confidently — knowing their personal information and performance data are always secure.

Did this answer your question?