Default visibility determines which projects a contact can consult in Aidi, based on the administrative unit.
As mentioned in the Suppliers and Contact article, a contact is associated with an administrative unit (AU). The contact can view all the projects in its AU. The AU determines which projects a contact can view.
✏️Note: In order to be able to collaborate on a project, i.e. to take action in relation to a project in addition to seeing it, despite the fact that the project is associated with his AU, the contact will have to be invited to the project by being added as a project contact.
Default visibility is based on the project's AU as well as the contact's AU. It's called "top-down default visibility" because a contact can only see the projects of its AU and those of the AUs below it, i.e. its child AUs.
Illustration of the top-down default visibility
What the contact sees
In the diagram above, if I'm Contact 1 associated with AU Direction A, I'll see projects from AU Division A and Division B and AU Section A and Section B.
I will not see any of the projects of the AUs that are in blue in this diagram, unless I am specifically invited to do so as a project contact.
Who sees the project ?
Project Z, whose main administrative unit is AU Division A in the diagram above, will be visible by default to users associated with AU Service, Direction A and Division A.
Users of other AUs (in blue) will have to be invited as contacts on the project to view it.
✏️Note : Default visibility apply to the following pages: