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.

Deny invite users

lars

Hi,

first of all: Thanks to the development team and to alfresco, it's a great alternative to other CMSs, great job, go ahead, thank you that you have made it open source!

My question:
I like to deny users to invite other users to a specific space. However this can obviously not be done via the predefined roles. Moreover I couldn't find a way to set it within configuration files like permissionDefinitions.xml.
Have searched the forum as well, but without result.
From my point of view this is a big security issue, so I would appreciate your help.
Thank you and with kind regards,
Lars

Find more posts tagged with

Comments

kevinr

"Deny" of users/groups is implemented in the repository but not yet exposed in the UI. It is accessable via the Alfresco Java API so custom code can set Deny.

However it sounds like you wish to change what the default ability of a new user is. The "owner" of a node has permissions by default, and that includes the ability to grant permissions to other users (the grant ability is itself a permission). So you want to change the list of permissions given to an OWNER of a node by default. This can be done by modifying permissionDefinitions.xml.

Thanks for your comments,

Kevin

lars

"…The "owner" of a node has permissions by default…

Kevin

Kevin, thanks for your feedback.

Yes, I'm aware of the things you mentioned. But the case was that while the user was not owner of the space, he was able to do everything, even as an editor, and even after I've definetly removed him and related groups from the list at all.
However I've figured out something, which might be the reason behind this strange behavior: The user was previously assigned to the space as owner, later on I decided to do some changes and assigned him to a different space as owner. It seems that in this case not all entries in the database are completely removed/changed (couldn't find out which ones)

With kind regards,

Lars

kevinr

However I've figured out something, which might be the reason behind this strange behavior: The user was previously assigned to the space as owner, later on I decided to do some changes and assigned him to a different space as owner. It seems that in this case not all entries in the database are completely removed/changed (couldn't find out which ones)

I think this is the problem - there is a known issue that if you reassign a user to a space, the system does not remove the old permissions from the previous home space. This is a tricky issue as the system does not know who assigned the permissions e.g. there is no different between admin or another user assigning permissions and the home space assigning permissions.

Thanks,

Kevin