It would appear that they do.
I first made a form and used 'special' on the menu item and module that led to it and those who were 'manager' tested it O.K. and were able to submit forms from the front end.
Later I made a publicly viewable CC connection to show the data, also fine -- the public could see it. However, I was a bit confused for 15 minutes or so when a manager complained they could no longer submit the form.
It turned out that the edit perms in the CC connection to that table governed the chronoform submission to that table as well. I did not expect that behaviour myself. I thought I was simply opting to not show the edit/delete buttons on the CC display for certain user levels.
Just something to be aware of.
Also, this could be used to leaverage CC's permissions to control form entry, but it's a little coarse as it just throws a joomla "private area" (or some such) error to the user when they hit submit in chronoforms.
I didn't see an added column on the table for permissions, so if there isn't a separate junction table somewhere, then perhaps CC uses an existing joomla mechanism for permissions which chronoforms also has to access through? If so, there could/should be some indication of that in chronoforms that I just didn't see. I suppose this whole ACL question will become moot in J1.6 anyhow.
I first made a form and used 'special' on the menu item and module that led to it and those who were 'manager' tested it O.K. and were able to submit forms from the front end.
Later I made a publicly viewable CC connection to show the data, also fine -- the public could see it. However, I was a bit confused for 15 minutes or so when a manager complained they could no longer submit the form.
It turned out that the edit perms in the CC connection to that table governed the chronoform submission to that table as well. I did not expect that behaviour myself. I thought I was simply opting to not show the edit/delete buttons on the CC display for certain user levels.
Just something to be aware of.
Also, this could be used to leaverage CC's permissions to control form entry, but it's a little coarse as it just throws a joomla "private area" (or some such) error to the user when they hit submit in chronoforms.
I didn't see an added column on the table for permissions, so if there isn't a separate junction table somewhere, then perhaps CC uses an existing joomla mechanism for permissions which chronoforms also has to access through? If so, there could/should be some indication of that in chronoforms that I just didn't see. I suppose this whole ACL question will become moot in J1.6 anyhow.
