Community Permissions

As a CoTech member, I want to be able to create circles/projects/job offers which are accessible only to a subset of communities (e.g. CoTech + Happy Dev + FACCTIC)

Actually Circles/Projects/Job offers link to a community is not implemented on Hubl side.

When it'll be live on Hubl, we'll rework the permission definition of Communities to allow admins of them to handle that however they want.

You might be interested by applications/hubl#853 (comment 41893)

thanks!

@jbpasquier where is the discussion on this at the moment?

I started a crusade to refactor the way that LDPPermissions works (djangoldp#305 (closed)), so I think it will need to be tied into that?

The applications/hubl#853 (comment 41893) is in the oven.

Permission definition of Communities is on a more general roadmap, not funded/not specified atm.

I was thinking of basing this all on django-guardians, with agents/actors/signals/call-them-maybe adding/removing/updating permissions for each objects of the communities.

djangoldp#197 (closed) is related to that

However I think it might not be fit for purpose (see the second half of djangoldp#244 (comment 28382) - at least some of these points are addressed in the refactor)

I think we should resolve djangoldp#305 (closed) first because we're in danger of ending up with multiple permissions systems

We should measure the performance of using only object-level permissions as well - it was terrible, it's a lot better now with the FilterBackend, but the 197 system would hit the superclass ObjectPermissionsBackend every time and we haven't tested that scenario

closed