Modifying available user actions

[alloydog]

A regular user has the following options available to them:

Create folder
Delete
Move
Copy
Add document
Add bookmark
Set default home
Export to file

Is it possible to disable some of them, for example, Delete?

[jllort]

Grants on user actions depends on grants on documents.

For example if you\'ve not got write access you can not delete document. It\'s the same kind of privileges you can be found on a O.S.

Why you want to make it so more restrictive, in which cases ?

[alloydog]

Why you want to make it so more restrictive, in which cases ?

In previous systems we have used, the average writer could upload, modify and move files, but not delete them. If we still require that sort of settings, I was just wondering if it could be done. It helps stop accidental deletions.

[jllort]

It could be implemented some extra grants, but this it\'ll made more complex to set, that was one of our internal discussions not yet finished. For example seems interesting to implement \"modify grants\" as a separated grant from \"write access\".

Really it could be implemented, delete, and \"modify grants\", but meanwhile we\'re thinking the best way to do it to continue having a easy end user system, you\'ll must be patient. Since now we\'ve haven\'t founded and easy solution that increasing grants continues beeing easy for end user to undertand it, we\'re playing with several options, and we\'re not happy with any.

We know it\'s something to do since version 2.0. but we\'ve still not found - for us - the easy and correct way to do ( and the exact number of grants to increase, for us we\'ve accepted \"modify grants\" as a new, but \"delete\" is not so clear for default installation -> could be something to parametrize -> hope you understand it ).

[alloydog]

you\'ll must be patient

:) No worries - it\'s not a \"must have\".

[jllort]

We\'re insteresting on end user opinion and expertice. What do you think to increase complesity on grants, really adding \"change permission\" grant is ok, or is really needed to add more like delete. We\'re worried about increasing complexity to end user. We want UI and functions become so much easy to end user. We\'ll put \"change grant\", but you considerer delete is too needed ( mandatory ).

[alloydog]

As I said, it was a \'feature\' of a previous system we used (Trisoft\'s Infoshare). The average user could create, modify, copy and move, but not delete. If we needed to remove a file, we had to email the database admin. No questions were asked why the file was to be deleted, and no authority had to be given from say, a project manager, so it seemed pretty pointless to me. Maybe it was a quirk of the system, or someone somewhere wanted it for some reason...

The sort of permissions I knwo we do need, are that top level folders (one or two down from okm:root) can only be created and deleted by a special user, say a manager.

We need to explorer the system a bit more to get a better idea of things we need.

[jllort]

I think I understand your problem. You need more control about specific end user operations. I\'ll be thinking for next OpenKM how could it be and extra configuration parameter, because on default OpenKM configuration I think is not good idea for major users.