nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Folders - Controlling Access

System

When creating a Workspace, and adding folders - is there anyway you can create a folder on a Workspace, and set the security to allow the user to import documents into the folder, and stop them from creating a sub-folder?

According to the documentation I can find, giving a user or group Read/Write access on a folder, allows them to add a subfolder - but they must have Read/Write to be able to import a document into that folder?

There must be a way to do this - or what is the point of coming up with a wonderful enterprise wide set of workspace templates, if your users can add private folders all over the place?

Cheers

Find more posts tagged with

Comments

jny

This can be accomplished through client-side customization; that is, you may implement a customized command in the desktop client to disallow the specified user from adding child folders.

Migrateduser

Thanks,

I can see how that would work, although I've not used customised commands yet - but I presume that that would make it an 'all or nothing' option - if you stopped it - they wouldn't be able to add a sub folder to any folder. Do you think it is possible to do it so that you can dissallow it in some workspaces/folders and allow it on others - dependent on the type of workspace?

Cheers

Daz

jny

Could you give me an example of the different types of workspace you've mentioned?

Migrateduser

Yes, Certainly.

For instance one type of Workspace will be the users own personal workspace - we are happy for them to create their own folders/subfolders in those.

Another type will be for a Matter - which will be of a defined template - we don't want users to be able to add subfolders to that structure - and more specifically to be able to add private or secured folders - there is no requirement in our business to do this.

cheers

Darryl

jny

There isn't a way to differentiate these two scenarios of workspace creation through the API's; that is, there is no way of knowing how the finished workspace was created -- through template or manual operation.

Do you have a way of distinquishing these two different ways of workspace creation: a workspace created by the end-user vs. a workspace created by a workspace template for the end-user? If so, then in code, you may verify this before enabling/disabling the new folder command (in Desktop WorkSite Clients).

Migrateduser

Wouldn't you be able to work out which is which using the Workspace Category? Would that be sufficient?

jny

Category is Client-defined; there is no such server API call to remember how the workspace was created. This Client-defined mechanism also does not remember how the workspace was created. Category is merely a set of options for the end-user to choose from in creating a new workspace.

What you could do is use one of the custom fields of the workspace profile to note how the workspace was created.