I'm just starting to familiarize myself with Bean. Thanks for all the hard work that's gone into making it what it is. So far as i can tell, the specific functionality i'm looking for doesn't seem to exist, so my request is this:

Would it be possible to create additional permissions which create more user-editing options, similar to the way content-type permissions work? For example, instead of simply:

  • MyBeanType: add Bean
  • MyBeanType: Edit Bean
  • MyBeanType: View Bean
  • MyBeanType: delete Bean

doing something more like:

  • MyBeanType: Add Bean
  • MyBeanType: Edit own Bean
  • MyBeanType: Edit any Bean
  • MyBeanType: Delete own Bean
  • MyBeanType: Delete any Bean

Thanks again for the great module!

Comments

indytechcook’s picture

indytechcook CreditAttribution: indytechcook commented
Status: Active » Postponed

The problem is that beans are not currently associated to users so it's not possible. I"m postponing this until I decide if I want to add the "author" to beans.

stephen Piscura’s picture

stephen Piscura CreditAttribution: stephen Piscura commented

Ah, makes sense. Well, in my case, i have specific fields added to a bean-type. I want to assign editing privileges to users with varying roles, but it would be kind of mess to give these users the ability to edit any beans of this type. In the meantime, what i'll have to do is create bean-types with identical fields, but different names in order to protect each user's content. Not ideal, but it can work.

It may be that my use-case is similar to others', for whatever it's worth. In any case, thanks again for this innovate, needed module.

indytechcook’s picture

indytechcook CreditAttribution: indytechcook commented
Status: Postponed » Active

So the author field has been added to bean as part of the bean revisions so this can move forward.

stephen Piscura’s picture

stephen Piscura CreditAttribution: stephen Piscura commented

Woo-hoo! Great news!