The affectations ARE synchronized beetween Project view, User view and also Affectation view.

What I guess is that you have "unsynchronized" Resource and User for same person.
Got to User, look for your user 1 and check ID
Got to Resource, look for user 1 and check ID
I guess they are different !

What you need is to have only one object for same person, so you have to create user and check "is resource" or create resource and check "is user".
Now create both.
This may be confusing if you use LDAP connection : if you create resource User1, and afterwards person with account User1 connects, ProjeQtOr creates new user for User1.
So when you create Resource that is a user, you should check "is user" directly on creation (or request it to the administrator), and if you use LDAP also check "frm LDAP".

One more time you are perfectly right :cheer:
I didn't create my user like that. I tested and it is working correctly now :blush:
Thanks for your patience.

First, you must understand the concept of data visibility.
Profile defined in user level allows to grant, if user has access to all projects or only projects affected to resource (user).
So, if you specify user can see all projects, you cannot reduce visibility of projects in project affectation.

Only a resource can be affected to a project with a specific profile.
So, it normal you cannot see project affectation on User screen.
A resource can be a machine or a human.
You must create a user for the resource, if you want that this "human resource" will be connected on ProjeQtOr.
The selected profile defined access rights granted to the user (resource) to the project.

Since version 5.1, the user guide explains this in the concept section.

Ok thanks a lot for these explanations