Private Booking Fields for Team Events

Open
#29,985 7 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@ArjunCodess is already working on this.

Since Sep 19, 2026.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

No files, tests, or entry points are identified. Start by locating the booking-question configuration and the views that expose answers to assigned team members, then trace calendar events, notifications, workflows, webhooks, and API responses. Done would require an agreed visibility model that hides admin-only fields from team members while preserving the explicitly requested access paths.

Written by the indexing model from the issue text.

Description

✨ feature 🚨 needs approval

Hi Cal.com Team,

I would like to suggest a feature that I believe would be very useful for businesses using Cal.com with multiple team members.

Currently, when creating booking questions or custom fields within a team event, the information submitted by the client can be visible to the team member assigned to the booking.

It would be very helpful to have an option to mark specific fields as Private / Admin Only.

For example, our booking form may collect:

• Property address
• Client contact details
• Site visit information
• Project reference
• Project price or other commercial information

Our engineers need access to the property address and site visit information, but they do not necessarily need access to the project price or other confidential commercial information.

Ideally, when configuring each booking question, there could be an option such as:

Field Visibility:
Everyone
Assigned Team Member
Team Admins / Owners Only

A field marked as Admin Only could still be available through workflows, integrations, webhooks and the API, while being hidden from the assigned team member in the Cal.com interface and, ideally, from their calendar event and notification emails.

This would allow businesses to use a single booking form while maintaining proper separation between operational information and private commercial information.

I believe this would be particularly valuable for engineering firms, consultancies, agencies and other businesses where different team members deliver the service but should not necessarily have access to pricing or other confidential client information.

I hope you can consider adding this functionality to new future update.

Dominant language
TypeScript
Stars
50k
Forks
15.6k
Avg merge
5d 1h
Merged PRs (30d)
15

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from calcom/cal.diy

All issues in calcom/cal.diy

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.