Hi Ruxandra,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

Thank you for showing interest in our Plugin.

The use case you described is not possible by just using one Table with our current built-in options,

we are not able to set a specific Column to be Editable for example by User 1,  and not editable by User 2,

or based on User Roles,

and we are also not able to hide/or show any Columns depending on user ID or User Role.

We have "Editor Roles" , but this reflects all the editable columns in a table.

This is an interesting idea for a future built-in feature, though, so you can add a development suggestion.

Please feel free to search on our suggestions page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

Right now, we have the native feature to limit the rows a user can see and edit based on user ID,

and there is a custom workaround to limit rows based on User Role.

-

To achieve your use-case, you can only try a workaround by using two  Tables,

one "main table" for Admins, and additional table for the "members of a jury",

and set up a different Page for different User Roles to see a 'different version of the table'.

You can use any Membership Plugin to restrict Access to a specific Page,

such as Page 1 can be only for custom User Role of  'member of a jury',

and there you can make an SQL Query version of this Table where you will disable editing for Columns that have "candidates information",

and just enable selectbox of "yes/no or maybe" for the Columns they are allowed to Edit.

Also you can set the "Editor Role" only for "member of a jury" , and "Admins".

And for this Table, you can set "Editor Type" to "none" for any Candidate Info Columns they should not be able to edit.

-

And for Admins you can have the 'main Table' which holds all data, and for them you can make all Columns Editable.

-

For example, you can have one main/master Manual table which will store all the data in the database.

Then, you can check this table's MySQL Table name from the Editing tab in the back-end table settings,

and you will be able to make an additional ( one or more) SQL table that pulls data from the same "master table",

and any editing you do on all these other SQL tables are going to be stored in the same table in the database,

This will be my example table :

Now, to make a new SQL Table from it,

first, check in Editing Tab/MySQL table name for editing:

in my example, the Manual table name is wp_wpdatatable_39,

so i make a new SQL table that will pull data from it;

and we can choose all columns like :

SELECT * FROM Table_Name

or just specific columns;

we can also have completely different settings/filtering/sorting and limitations for front-end users on each table;

and you can make multiple SQL Query tables that pull the same data from the "main table".

SELECT  column_name1,
        column_name2,
        column_name3
FROM table_name

-

And i just wanted to point out that you can try wpDataTables before purchasing

 on our sandbox Demo sites ( you can find links for the main plugin Demo,  

as well as add-on Demos, in my signature),

and there is a 15-day money-back guarantee period, 

so if you purchase the plugin, you can safely fully test it out, and if it doesn't fit your needs you can request and receive a refund in that period. ( same goes for all plugins and add-ons)

Let me know if that helps, and if you have any additional questions. 

Hi damonhedgspeth  and Ruxandra,

Should you be interested in exploring a collaborative effort focused on a particular use-case, we recommend initiating communication through email for a more streamlined exchange of information.

Currently, the most pertinent custom idea/example that aligns with your inquiry has been conveyed in our prior responses within the ticket. 

We believe this serves as a comprehensive reference for your consideration.

In order to maintain clarity and conciseness for other users who may access this public ticket, we encourage minimizing the addition of new replies within the thread, if feasible.

We appreciate your understanding and cooperation in this matter.

Thank you.