@Richard: thanks for the information. My objective is to segregate the project per Project Leader.
@babynus: My user 1 is project Leader and assigned as a Project Leader in my project.
Moreover in the rights access the profile Project leader is set to "manager" for the project.
(I tried to set "manager +" but I have access to all the project and I just want to have access to the project my user is assigned as a project Leader)
OK I found the issue.
It is not link to the star date because I didn't fill these attributes and it is working correctly (normal behavior?).
It is a problem I forget to raise, here is the scenario:
1- I create a project as admin
2- I affect my user 1 as a project Leader in the project panel or Planning panel
3- I connect as user 1, i am not able to see the project
4- I connect as admin, I go to User panel, I realized that my user has no affectations but if I go the project or planning panels I see my affectation
5- So I add the affectation in the user panel manually
6- I connect as user 1 and I can see my project.
Is it possible to synchronize the affectation in the project/planning panel Vs user panel?
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".
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.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Cookies settings
×
Functional Cookies
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Please login to see yours activities!
Other cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.
Support us on Capterra
