Visibilities on the folder structure
The following article describes how the visibility of folders in the document structure can be adjusted and checked in order to control the visibility of documents, files and folders.
Directly to the following sections:
Customize visibility
Inheritance of visibility
Visibility / authorization check
In the folder structure of buildagil, the visibility of folders and the files and documents they contain is controlled by the team membership and the defined read and write permissions.
Please note that if the visibility of a folder is changed, the visibility of the subfolders also changes. Detailed information on this can be found in the following section: Inheritance of visibility
The authorizations can only be adjusted by an administrator, as described in the following article: Authorizations
To check or adjust the visibility on a folder, click on the shield icon on the desired folder.
The detailed view opens, where the desired visibility of the individual teams can be adjusted.
The visibility can be changed by clicking on the teams and must then be saved via Adjust visibility.
The folder is visible and editable for the people in this team
The folder is visible to the people in this team
The folder is not visible to the people in this team
The visibility of a folder is inherited by all subfolders by default. This inheritance remains in place until different visibility rules are made for a subfolder.
If the visibility of a parent folder is adjusted, the visibility of all subfolders is updated, provided that these subfolders do not have individual visibility rules. Such specific settings in a subfolder remain unaffected by changes in the parent folder.
Once the visibility inheritance has been disconnected, it can no longer be restored.
A special case occurs when a subfolder has a higher visibility than its parent folder. In such cases, the subfolder cannot be accessed via the normal folder structure. As a solution, a link can be created to this subfolder, which enables direct access even if the parent folder is not visible. The creation of such shortcuts is described in the following article: Links in the folder structure. The folder can also be linked directly in a task or topic.
To control which teams have access to which elements, there is a filter by visibility.
This filter is available under documents, tasks, topics and in the journal.
The filter by visibility is only available for project administrators.
If the filter is activated, only the folders, documents, tasks and topics to which the selected teams have access are displayed. The folders and files that are not visible are grayed out.
Via Display visibility by person you can see which users have which visibility on the folder.
Further information on authorizations and visibility: Authorizations & Visibilities
Check visibility, control authorizations, control visibilities
Directly to the following sections:
Customize visibility
Inheritance of visibility
Visibility / authorization check
Customize visibility
In the folder structure of buildagil, the visibility of folders and the files and documents they contain is controlled by the team membership and the defined read and write permissions.
Please note that if the visibility of a folder is changed, the visibility of the subfolders also changes. Detailed information on this can be found in the following section: Inheritance of visibility
The authorizations can only be adjusted by an administrator, as described in the following article: Authorizations
To check or adjust the visibility on a folder, click on the shield icon on the desired folder.
The detailed view opens, where the desired visibility of the individual teams can be adjusted.
The visibility can be changed by clicking on the teams and must then be saved via Adjust visibility.
The folder is visible and editable for the people in this team
The folder is visible to the people in this team
The folder is not visible to the people in this team
Inheritance of visibility
The visibility of a folder is inherited by all subfolders by default. This inheritance remains in place until different visibility rules are made for a subfolder.
If the visibility of a parent folder is adjusted, the visibility of all subfolders is updated, provided that these subfolders do not have individual visibility rules. Such specific settings in a subfolder remain unaffected by changes in the parent folder.
Once the visibility inheritance has been disconnected, it can no longer be restored.
A special case occurs when a subfolder has a higher visibility than its parent folder. In such cases, the subfolder cannot be accessed via the normal folder structure. As a solution, a link can be created to this subfolder, which enables direct access even if the parent folder is not visible. The creation of such shortcuts is described in the following article: Links in the folder structure. The folder can also be linked directly in a task or topic.
Visibility / authorization check
To control which teams have access to which elements, there is a filter by visibility.
This filter is available under documents, tasks, topics and in the journal.
The filter by visibility is only available for project administrators.
If the filter is activated, only the folders, documents, tasks and topics to which the selected teams have access are displayed. The folders and files that are not visible are grayed out.
Via Display visibility by person you can see which users have which visibility on the folder.
Further information on authorizations and visibility: Authorizations & Visibilities
Check visibility, control authorizations, control visibilities
Updated on: 15/11/2024