sabre-io / Baikal

Baïkal is a Calendar+Contacts server
https://sabre.io/baikal/
GNU General Public License v3.0
2.52k stars 291 forks source link

share a carddav/caldav with multiple users? #73

Closed Ohax closed 9 years ago

Ohax commented 11 years ago

Is it possible to share a carddav/caldav with multiple users? If so is it possible to assign rights to read / write function of the user?

simonszu commented 11 years ago

I think, currently it's not possible. But i'd love that feature, too.

Svish commented 11 years ago

Yes, I could really need this too. That is, to have a certain calendar where one or two people are allowed to update it, and other people are allowed to read it.

Would also be good if there was a way to publicly share a read-only version that you subscribe to through google calendar, outlook/hotmail, iPhone, etc.

(Or is this already possible somehow?)

brendon-codes commented 11 years ago

Yes, I would love this ability as well to share calendar as readonly.

ryanmitchell commented 11 years ago

+1

ryanmitchell commented 11 years ago

I've written a change to the PDO backend that turns a addressbook or calendar into a shared one, however it forces all users subscribed to it to only have that addressbook/calendar (which is my needs).

Happy to share the code if that helps anyone else get started on this feature.

Svish commented 11 years ago

@ryanmitchell What do you mean? That if I subscribed to that calendar/addressbook on my iPhone for instance, I could not subscribe to any others?

ryanmitchell commented 11 years ago

Yeah (on that DAV server). It only shows 1 calendar/addressbook for the group you belong to.

i.e.

I'm a user I'm subscribed to group x I can see the calendar/addressbook associated with group x

On 15 May 2013, at 14:44, Torleif Berger notifications@github.com wrote:

@ryanmitchell What do you mean? That if I subscribed to that calendar/addressbook on my iPhone for instance, I could not subscribe to any others?

— Reply to this email directly or view it on GitHub.

cr4shydlo commented 11 years ago

First. I love your Baikal!. Good Job. When i compare baikal admin and davical admin... ;) I'm shocked. But multiple user to calendar and adressbook is a must ;/ if we want to use it in corporation (roundcube, iphones, androids) etc... Can you try to add this ? Big thanks!

Programie commented 11 years ago

I would also love to see that feature. Baikal really rocks. ;-)

lexusburn commented 11 years ago

+1

it can be done with this, i think: http://code.google.com/p/sabredav/wiki/CalDAVSharing

irrtum commented 11 years ago

+1!

irrtum commented 11 years ago

@ryanmitchell Hey Ryan, could you share the changes you made?

ryanmitchell commented 11 years ago

Sure - drop me an email and i'll send you the file. ryan@rt.to

plushcthulhu commented 11 years ago

+1!

ghost commented 11 years ago

+1

ghost commented 11 years ago

We're currently looking in our University to implement a new CalDAV/CardDAV solution to replace the unreliable ownCloud service. If Baikal could do sharing it would be perfect, as we need users to be able to share particular calendars with particular user(s) and groups. Thus a group concept wouldn't be bad either.

Great job guys! +1

xcdr commented 11 years ago

+1, I need group calendars and address books.

mikael35 commented 10 years ago

Thank you for this work. Baikal run nice on synology NAS and iphone. For the familly, I just need this extra feature: setting up some right to read or write to users. IE: Mrs can see Mister calendar, but cannot modify it, like mister see but cannot modify (erase) events on Mrs calendar, but they can both modify a common calendar. That would be perfect.

Svish commented 10 years ago

@mikael35 That is exactly what I need as well!

renne commented 10 years ago

+1

It would be great if one can assign carddav records to multiple groups by multiple tags and each group can be shared with other users (configurable insert, update and delete rights per group/user).

Database tables:

group (primary key ID, name, owner) record n <-> m group (record ID, group ID, insert, update, delete) group n <-> m user (user ID, group ID, insert, update, delete)

That way a user can decide if a group is allowed to change a record and/or a user can change all records of a group.

netgusto commented 9 years ago

This will be supported in Baïkal 2. See #303

soluxima-erik commented 9 years ago

Wonderful project..

+1 for shared calendars and address books (would pay for that ;) )