Private Booking Fields for Team Events
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
- Domain
- authorization, backend-api-design
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
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
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from calcom/cal.diy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
README instructs `nvm use`, but the repo has no `.nvmrc` filePossibly taken @ravindrasinghshah claimed this 6 days ago. Open🐛 bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
calcom/cal.diy#30550 · 1 comment ·
Maintainers usually reply within 2 days
-
footer blends into the main section in dark mode on cal.com/talk-to-salesPossibly taken @An-Average-Student claimed this 4 days ago. Open✨ feature 🚨 needs approval
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
calcom/cal.diy#30548 · 3 comments ·
Maintainers usually reply within 2 days
-
Seated reschedule fails when deleting the original booking's calendar event or video meeting failsPossibly taken @Sanketmis208 claimed this 7 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
chore(i18n): remove unused Cal.ai voice agent and phone stringsPossibly taken @SachinyadavAug20 claimed this 11 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
Similar issues
-
Stop retrying permanent GitHub API failures in retry.shPossibly taken @muspi-merol-review claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
promplate/code-review#113 · 1 comment ·
Maintainers usually reply within 1 day
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
サムネイルの Storage のバケット(`thumbnails`)に、大きさの上限(1 MiB)と許可する種類(JPEG、PNG、WebP)を設定するPossibly taken @ykzts claimed this today. Opentech: supabase
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
inabagumi/shinju-date#7147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elecnix/your-attention#129 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
umami-software/umami#4780 ·
Maintainers usually reply within 3 days