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; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Collaborator role

simon

As seen in the 1.2RC2 release notes:

Added new "Collaborator" role. This role is just the combination of the "Editor" and "Contributor" roles.

and the permission node example in the WIKI:

<!– A contributor can create content and then they have full permission on what –>
        <!– they have created - via the permissions assigned to the owner.              –>

        <!– An editor can read and write to anything in a space; they can not create    –>
        <!– new nodes. They can check out content into a space to which they have       –>
        <!– create permission.                                                          –>

So a collaborator can create content and the have full permissions on this content. They can read and write to anything in a space, even if they didn't create. They can check out anything in a space.

A contributor can create new document nodes but no folders, an editor can not create any new nodes so a collaborator should be able to create document nodes but no folder nodes, exactly what I need.

I create a new space and added only one user, a collaborator, but he can create new folders… I don't think he should have these rights according to the explanation above. Is this still some bug?

A fast answer would be appreciated.

Find more posts tagged with

Comments

steve

Hello,

A Contributor can create new spaces.

Steve

simon

Steve, you are right. I should have checked this first, sorry.

I need someone who can add content (documents and such) but no sub spaces. This role should be able to read, checkout and remove all documents but can not change the folder structure.

I know how to add a role (can I extend permissionDefinitions XML file like the others?) but I can't find how to define "add content but no spaces".

<includePermissionGroup permissionGroup="AddChildren" type="sys:base"/>‍

Is the only line I can think of but it seems that spaces are children, just like documents.

simon

*bump*

I know how to add a role (can I extend permissionDefinitions XML file like the others?) but I can't find how to define 'add content but no spaces'.

Any answers on these 2 questions? Extending the permissionsDefinitition.XML + (and more important) define a rule with content adding like a collaborator but no spaces.

Thanks!

andy

Hi Simon

There is currently no way to allow create for documents but not folders in the permission layer.

If this is an application requirement, then this could be enforced by a custom evaluator on the menu item.

We are thinking of support in this area but there is interaction between files, folders, forums and discussions which make this more complicated.

Regards

Andy

simon

Thanks Andy.

This is a feature we would like to see. The folder structure is quite fixed and I prefer not to allow my editors to create spaces all over the structure but they should be able to add documents (wouldn't be much of a DMS if they couldn't).

I do understand that this is more complicated than it looks (the node ideas all over Alfresco is a good idea but makes it somewhat more complicated in this case).

We are thinking of support in this area.

Nice, just do it!

asoph

Hello

I have the same problem: I would like that the user can add content but no spaces.

Simon, did you find a solution to that problem?
Is it possible with Alfresco 1.4 to customize the role?

Thank you

as

simon

Asoph,

No, no solution for the problem yet and I don't know how 1.4 handles this. The delete permission I added works fine but indeed, I'm waiting for some permission settings that may differe from files and folders.