Skip to content

Team owned calendar  #3044

Open

Description

@Gunnar-GO

A Calendar that is connected to a group would be nice. Like a group folder.

At the moment a calendar will be created by an user and shared. That would result in that the Calendar is always connected to this user. The construct breaks down if the person is not longer part and the account will be deleted. In this view the calendar-owners must/will live as zombies (undead accounts).

A Group-Calendar would avoid that.

Activity

  1. johnnyq commented on Jun 16, 2023

    @johnnyq
  2. KornKalle commented on May 3, 2024

    @KornKalle
  3. miaulalala commented on May 7, 2024

    @miaulalala
    Contributor

    We have some of what we would need for this already: oc_dav_shares works on a group basis with a group principal.

    The creation would have to be integrated somehow, maybe an occ command that allows creating of group calendars.

    Question 1 is what happens when there's something happening with the group - i. e., if the group gets deleted, does the calendar get transferred to each individual user or will it be gone? Admins might want to delete groups for any reason, or they might be coming from backends such as LDAP. The process of what happens with the data when a group is changed, renamed or deleted needs to be taken into account. Which is a point for also implementing #4594 so an admin can transfer any calendar before deleting the associated user / group.

    Question 2 is how this can work with scheduling. The RFC needs to be consulted on this.

    Question 3 is how we can keep track / update the users that have access to this calendar if group memberships change. So if Alice leaves the "Marketing" group, but is not deleted as a user (which would work fine), we would need to know about it and remove her share. Same goes the other direction - when Bob joins the "Marketing" team, he will need a share entry. This at the moment is not tracked for existing share calendars either if they're shared with a group.

    In essence, a lot of moving parts which will need many separate functionalities to get this to work smoothly, even though it's a fantastic idea.

  4. ghostmju commented on Sep 29, 2024

    @ghostmju

    This is a feature that would definitely help our small setup for our sports club to keep the calendar off a personal account (like Group Folders does with files).

    For question 1 this would be perfectly ok, that the calendar is gone when the group is deleted.
    The admin(s) should be aware which group is created for what usage.
    If it's coming from an integration similar things apply - an extended feature request could let the group calendars without a group go stale, to be assigned to a new group or manually deleted. this would be also useful on integration hick-ups.
    (sorry for my ignorance here, I'm quite new to Nextcloud, so I do not know how Group Folders deals with it:) Similar approach as implemented for group folders should be sufficient/expected?

    If q2 aims for users: Calendar gone, schedule gone :-)

    Q3 is an interesting hint for our usage, as we are starting right now, we have not experienced this behavior - from my perspective I'd call it a very unexpected behavior if the current group membership is not immediately reflected for the shared objects (let it be folders, calendars or other items).

  5. changed the title [-][Feature request] Group Calendar [/-] [+]Group Calendar [/+] on Apr 4, 2025
  6. alexanderdd commented on Jul 16, 2025

    @alexanderdd

    IMO Group calendars should work for both 'Groups' and 'Teams'.

    Maybe even rename this issue/feature to "Team Calendar" because that is the general direction the product is taking?

    IMO It should then also be shown in the Contacts App > Teams, so this would be related: nextcloud/contacts#4127

  7. changed the title [-]Group Calendar [/-] [+]Team/Group Calendar [/+] on Nov 25, 2025
  8. changed the title [-]Team/Group Calendar [/-] [+]Team owned calendar [/+] on Jul 17, 2026
  9. 2 remaining items

  10. moved this from To triage to Triaged in 🧑‍🤝‍🧑 Community triageon Jul 20, 2026
  11. added
    1. to developAccepted and waiting to be taken care of
    and removed
    0. to triagePending approval or rejection
    on Jul 20, 2026
  12. moved this to 👓 Design review in 🖍 Design teamon Jul 23, 2026
  13. jospoortvliet commented on Jul 29, 2026

    @jospoortvliet
    Member

    A few notes on implementation - this needs some research from someone deep into the caldav side of things like @SebastianKrupinski

    CALDAV is designed around an owner with a unique email address. A team is not a person and has no email address. Possible solutions from a discussion:

    • have one system-wide email address for all teams owning all Calendars. But might cause permission challenges.
    • create a email per team. But then needs Nextcloud/team creation/Calendar to provision email addresses.

    Background on how SharePoint does it, from @schiessle

    On the Sharepoint Sites, which is what we want to copy with Teams, it was interesting to see that the resources attached to Sharepoint sites are quite limited. For example the calendar is just that, a stand-alone calendar for the site where you can add the appointments for the team/project. For example it doesn't allow to invite people to meetings which solved all the question around "who sends the invitation and how to handle replies". Which means that the simple approach we discussed of a hidden shadow user who holds all the resources and shares them to the team should work just fine.

    Jos, who isn't so smart, did ask this follow-up:

    I don’t fully get the issue. If you have a shared calendar (like we do in comms) and book a meeting, you can then choose to put it in the shared calendar… the invite of course still comes from me, who owns the calendar doesn’t matter at that point. It just makes the meeting visible for everyone who it is shared too. Doesn’t even mean they are always invited…

    This seems a fine mechanism. Or am I missing something?

    Of course, him not being that clever means this might be exactly what SharePoint does - there is no calendar owner who can invite people, only those who have access to the calendar can put invites in it, on their own name.

  14. moved this from 👓 Design review to 🏗️ At engineering in 🖍 Design teamon Aug 20, 2026
  15. SebastianKrupinski commented on Oct 16, 2026

    @SebastianKrupinski
    Contributor

    CALDAV is designed around an owner with a unique email address. A team is not a person and has no email address. Possible solutions from a discussion:

    * have one system-wide email address for all teams owning all Calendars. But might cause permission challenges.\
    * create a email per team. But then needs Nextcloud/team creation/Calendar to provision email addresses.
    

    True, our system is designed on a per email basis but this is only for iMIP (sending invites and receiving replies) the calendar it self does not require a user or email address to function

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions