We programmatically create role permissions within a Autodesk Construction Cloud (ACC) Docs environment with a structure (folders, roles and permissions) directly following ISO 19650 standards. This poses a problem with the Autodesk Desktop Connector (ADC, v15+, used by many within the company) with equally named folders. Given the structure:
- Project Files
-- 01 WIP (users with role A have no permissions here, according to ISO 19650)
--- Discipline A (where users with role "roleA" have "PUBLISH,VIEW,DOWNLOAD,COLLABORATE,PUBLISH_MARKUP,EDIT" permissions)
-- 02 Published (where users with role "roleA" have "VIEW,DOWNLOAD,COLLABORATE" permissions)
--- Discipline A (where users with role "roleA" have "PUBLISH,VIEW,DOWNLOAD,COLLABORATE,PUBLISH_MARKUP,EDIT" permissions)
The ADC presents the folders as such:
with the discipline folder receiving the "(2)" suffix (this is the one in "01 WIP"), as this folder name is also present "02 Shared".
Dropping the permissions from users with "roleA" from "02 Pubished" altogether results in this ADC view:
Questions:
- Is this the intended behaviour or a bug? (If this is intended behaviour, please move this threat to "Ideas".)
- What would be a way to resolve the (n) suffix, as roles could be prohibited from knowing the (full) path to a folder? Present an option to opt for that (so we could choose if users see the path or not)? Or would we need to change the foldername to make sure it's unique?
Hi @JvBMov ,
I am sorry but I am not understanding what it is your are asking here?
In the ISO 19650 standard it does not state anything about folders, roles or permissions. Are you applying the naming standard function within Autodesk Docs? The are three states noted but that is it.
What is ADC, v15+ mean?
You can switch off the full folder path in the settings if you don't wish for users to see it.
Sorry I think you need to explain this in more detail.
Yes, to clarify: "ADC, v15+" is the Autodesk Desktop Connector (ADC), version v15 (and minor versions)
The folder access structure is based on the ISO 19650 which states that different task teams cannot acces other task teams' WIP storage:
So when we specify this WIP per task team as a folder in ACC Docs, and have a folder with the same name in 02 SHARED, the above situation with "Folder A (1)" and "Folder A (2)" occurs in the ADC windows explorer view.
Can't find what you're looking for? Ask the community or share your knowledge.