• Hello Fabrik Community

    Fabrik is now in the hands of the development team that brought you Fabrik for Joomla 4. We have recently transitioned the Fabrik site over to a new server and are busy trying to clean it up. We have upgraded the site to Joomla 4 and are running the latest version of Fabrik 4. We have also upgraded the Xenforo forum software to the latest version. Many of the widgets you might have been used to on the forum are no longer operational, many abandoned by the developers. We hope to bring back some of the important ones as we have time.

    Exciting times to be sure.

    The Fabrik 4.0 Official release is now available. In addition, the Fabrik codebase is now available in a public repository. See the notices about these in the announcements section

    We wish to shout out a very big Thank You to all of you who have made donations. They have really helped. But we can always use more...wink..wink..

    Also a big Thank You to those of you who have been assisting others in the forum. This takes a very big burden off of us as we work on bugs, the website and the future of Fabrik.

Found! A method for anaging CRUD rights in the Fabrik Context

After several months of grappling with the Joomla ACL structure, and a careful study of the features of the FB model, I have finally found a method for managing and allocating the CRUD rights in the Fabrik Context to different User Groups (and of course, by implication - users) (CRUD standing for: Create, Read, Update, Delete).

The problem is that the usual Joomla Access Control (ACL) structure to manage CRUD rights does support access to the FB object feature level, because the standard J! CRUD operates at the FB higher object level.

I needed to find a way to closely control the allocation of the CRUD rights at the FB object feature level.

I studied all the user posts on the subject in the FB forum, but did not find a succinct solution to my problem.

I am providing this post as one way of acknowledging all the value that I have derived from access to this marvellous component.

Here is a simple statement of the problem I faced:

I need to support three classes of users.

The first group that is able to view only the list, and records.

A second group that inherits the first group rights, and additionally can add, edit, and delete records.

A third group that inherits the access rights of first and second groups, and also has the right to empty records.

SO - here is my receipe to achieve the above:

To achieve CRUD management at the J! object feature level - set up the following:

(Using the Joomla User Manager component, do the following):

Under Users:

(Do this simply for test and verification purposes)

Create three users:

user_a
user_b
user_c


Under User Groups:

a) Create Novice Group (i.e. bottom level - least rights)

Allocate Registered as Parent.

b) Create Practitioner Group (i.e. middle level - create and manage records)

Allocate Novice as Parent.

c) Create Master Group (able to trash data sets)

Allocate Practitioner as Parent.


Now under Users:

Allocate user_a to Registered, Novice.
Allocate user_b to Registered, Practitioner.
Allocate user_c to Registered, Master.


Under Access Levels:

Create Novice.
Allocate the access level to the Novice User Group.

Create Practitioner.
Allocate the access level to Practitioner User Group.

Create Master.
Allocate the access level to Master User Group.

(Using Fabrik):

(For example: List -> Access)

In Fabrik (Lists, Forms, Elements, as required) allocate as follows:

View List: Novice
View Records: Novice
Edit Records: Practitioner
Add Records: Practitioner
Delete Records: Practitioner
Empty Records: Master

This completes all the ncessary steps.

You will now find that user_a,b,c now have closely controlled CRUD rights.

Enjoy!

Alastair Walker
 
Yes sure. It has helped me solving a part of my issue and also understanding that Fabrik uses the Joomla access level more than the group.
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top