10BC0 docs: clarify global event types vs team event types by ascender1729 · Pull Request #24334 · calcom/cal.com · GitHub
[go: up one dir, main page]
Skip to content

docs: clarify global event types vs team event types #24334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

docs: clarify global event types vs team event types #24334

wants to merge 1 commit into from
+35 −0

Conversation

ascender1729
Copy link

Summary

Addresses confusion between global event types and traditional team event types by adding comprehensive clarification to the platform documentation.

Changes Made

  1. Added "Important" note section at the beginning of the guide explaining:

    • What global event types DO (create individual event types per user)
    • What global event types DON'T DO (they're not for round-robin/collective scheduling)
    • Clear examples of use cases they support vs don't support

  2. Added "Terminology Clarification" section at the end to distinguish:

    • Platform teams (grouping mechanism for managed users)
    • Team event types (round-robin/collective scheduling feature)
    • How the term "team" serves different purposes in different contexts

Problem Solved

The issue reporter (#23399) mentioned spending a week attempting to use global event types for a use case they don't support (custom app allowing users to book a specific team member). This documentation improvement will help other developers:

  • Avoid wasting time on wrong approaches
  • Understand the difference between Platform teams and team event types
  • Choose the correct feature for their use case

Testing

  • Reviewed documentation changes for clarity and accuracy
  • Ensured MDX syntax is correct
  • Cross-referenced with existing team event types documentation

Fixes

Closes #23399

@CLAassistant
Copy link
CLAassistant commented Oct 7, 2025 •
edited
Loading

CLA assistant check
All committers have signed the CLA.

@graphite-app graphite-app bot added the community Created by Linear-GitHub Sync label Oct 7, 2025
@github-actions github-actions bot added the docs area: docs, documentation, cal.com/docs label Oct 7, 2025
@graphite-app graphite-app bot requested a review from a team October 7, 2025 18:12
@github-actions github-actions bot added Low priority Created by Linear-GitHub Sync platform Anything related to our platform plan labels Oct 7, 2025
@vercel Vercel
Copy link
vercel bot commented Oct 7, 2025

@ascender1729 is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

@graphite-app graphite-app bot requested a review from a team October 7, 2025 18:12
@coderabbitai coderabbitai
Copy link
Contributor
coderabbitai bot commented Oct 7, 2025 •
edited
Loading

Walkthrough

Adds two documentation updates to docs/platform/guides/global-event-types.mdx: (1) a Note at the top clarifying what Global Event Types are, their scope, and advising use of team event types for team-wide scheduling; (2) a Terminology Clarification Tip distinguishing Platform teams, Team Event Types, and their contextual meanings, and separating platform-managed user teams from traditional team scheduling features. No code or API changes; purely content updates addressing terminology and capability distinctions.

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)
Check name Status Explanation
Title Check ✅ Passed The title clearly and concisely summarizes the primary change by indicating that the documentation clarifies the differences between global event types and team event types, which aligns perfectly with the content of the changeset.
Linked Issues Check ✅ Passed The documentation additions explicitly address each objective from issue #23399 by clarifying what global event types do and do not support, distinguishing platform teams from traditional team event types, and warning against the unsupported approach of using team event types for per-user booking URLs.
Out of Scope Changes Check ✅ Passed All modifications are contained within a single documentation file and solely add explanatory content relevant to the objectives, with no unrelated or out-of-scope changes introduced.
Description Check ✅ Passed The pull request description directly outlines the added documentation sections, the problems addressed, and the testing performed, all of which correspond to the changes in the MDX file and provide relevant context for the update.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9acd27f and bd8da91.

📒 Files selected for processing (1)
  • docs/platform/guides/global-event-types.mdx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/platform/guides/global-event-types.mdx

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ascender1729
docs: clarify global event types vs team event types (calcom#23399)
bd8da91 
Added comprehensive clarification to address confusion between:
- Global event types (managed team event types with assignAllTeamMembers)
- Traditional team event types (round-robin/collective scheduling)
- Platform teams vs regular Cal.com teams terminology

Changes:
- Added Important note at the beginning explaining what global event types DO and DON'T do
- Added Terminology Clarification section to distinguish Platform teams from team event types
- Clarified that global event types create individual booking URLs for each managed user
- Explained that traditional team event types should be used for round-robin/collective scheduling

This helps developers avoid spending time trying to use global event types for use cases they don't support.

Fixes calcom#23399
@ascender1729 ascender1729 force-pushed the docs/improve-global-event-types-clarity-23399 branch from 9acd27f to bd8da91 Compare October 7, 2025 18:20
@supalarry
Copy link
Contributor

Thank you for the contribution. Could you please explain where does the confusion between global event types that are created using managed event type vs team event types com from? The global event type guide does not mention other team event types and clearly states

Event types that every managed user or a subset of managed users will have automatically. If you want all of your managed users or a subset of managed users to have the same event type set up automatically, then follow along.

Closing this issue until then

@supalarry supalarry closed this Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
community Created by Linear-GitHub Sync docs area: docs, documentation, cal.com/docs Low priority Created by Linear-GitHub Sync platform Anything related to our platform plan size/M
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Issue on docs
3 participants
@ascender1729 @CLAassistant @supalarry
0