Ok the user I tried can't see table rows.
But ho can I add a permission role to the table? Which is the default one for lookup ( I think is
Everyone (Lookup)) but in the designer when i set edit permission for this table I can't add new role to the table.

I added in VI_Employee_voerview a collction to the node Collections objecttype my view, in the node initializer of the that collection i put a node loadcollection for the collection created.
I'm on version 7.1 new
No errors

When you are working with the ObjectBrowser and WebDesigner are you using the same authentication module?

For example, when you are using the "Active Directory" authentication module when you are working with the ObjectBrowser, but on the WebPortal you are using the "Active Directory (Role-based)" authentication module, you will not have the same access rights after a successful login. Because the first one uses the DialogUser and the second one uses the role-based permission Groups.

So, when you check the permissions you have to ensure that you are using the same authentication module for the ObjectBrowser and WebDesigner.

The next thing that you have to check is that you have read access for each column where you need access to, if one column is missing the complete load will fail without any exception.

And last but not least you have to ensure that your view have a primary key (UID column). I had the same problem and got this hint from a good old colleague.

Another difference between my loadtype and the other that works is that I added a collection to the "module" VI_Employee_overview instead in other exmplae I have in the webdesigner I have table added to table root node in "component" object

Debugging I notice that the load statment is not triggered, the execution stack goes to Initializer but doesn't go inside to execute the load statment both in the collection inizializer and the module initializer. Why?

Can you try loading a different collection, preferably one if the otb tables and see if that loads? Or maybe try loading the person collection which you already have. This will tell us if the issue is in the module somewhere or perhaps something wrong in the view.

Also, as Sven mentioned make sure your view has a primary key. This is done in the backend not in Web designer. If you can't take a pk from the tables then you should consider constructing your own pk in the view definition