Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Hyland Connect
- Platform
- Alfresco
- Alfresco Archive
- Re: Permissions needed for adding content via CIFS
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Permissions needed for adding content via CIFS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2010 08:28 PM
I'm forcing users to check out content before editing it by basically removing WriteContent from all roles except ROLE_LOCK_OWNER. This works well in the web client. Users are also able to add spaces and content as they wish.
Via CIFS however, users are not able to copy files into Alfresco; they get "Permission denied." Is AddChildren not enough to add content, at least for CIFS? Is WriteContent needed also? Is there something else I'm missing? Our users can't use Desktop Actions because they are on Linux.
I can post my configurations in a later post. Thanks in advance!
Via CIFS however, users are not able to copy files into Alfresco; they get "Permission denied." Is AddChildren not enough to add content, at least for CIFS? Is WriteContent needed also? Is there something else I'm missing? Our users can't use Desktop Actions because they are on Linux.
I can post my configurations in a later post. Thanks in advance!
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2010 11:14 PM
Here's my custom-permissionDefinitions.xml:
I defined CheckOutContributor in the config then gave all users only that role in the Company Home space.
I had trouble removing FullControl from the creator of a piece of content because of the globalPermission for ROLE_OWNER because if there is no owner property, the creator property is used. Restricting the ROLE_OWNER's permissions caused errors when adding content; I'll open a Jira ticket for it sometime. I got around this by adding a content rule that added the aspect ownable to everything, so all content would have a blank owner.
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE permissions >
<!–PUBLIC '-//ALFRECSO//DTD PERMISSIONS//EN' 'permissionSchema.dtd' –>
<!– Note: the above is commented out as spring does not seem to find the dtd –>
<!– ============================================ –>
<!– The base permission model for the repository –>
<!– ============================================ –>
<!– The parent permission checks were removed 20/1/2006 –>
<permissions>
<!– Namespaces used in type references –>
<namespaces>
<namespace uri="http://www.alfresco.org/model/system/1.0" prefix="sys"/>
<namespace uri="http://www.alfresco.org/model/content/1.0" prefix="cm"/>
<namespace uri="http://www.alfresco.org/model/wcmmodel/1.0" prefix="wcm"/>
<namespace uri="http://www.alfresco.org/model/wcmappmodel/1.0" prefix="wca"/>
</namespaces>
<!– –>
<!– Permission sets link permissions and groups of permissions to types and aspects –>
<!– defined in the model. Permissions defined against a type apply to all objects –>
<!– that inherit from that type. Permissions defined against aspects apply to all –>
<!– objects or only objects that have the aspect applied. For example, the permission –>
<!– to lock an object could apply to any object but the permission to unlock an –>
<!– object would only apply to objects that have the lockable aspect. –>
<!– –>
<!– =============================================== –>
<!– Base permissions available on all types of node –>
<!– =============================================== –>
<permissionSet type="sys:base" expose="all" >
<!– ================= –>
<!– Permission groups –>
<!– ================= –>
<!– –>
<!– Permission groups are convenient groups of permissions. They may be used in –>
<!– thier own right or as the effective set of permissions. If an authority has –>
<!– all the permissions that make up a permission group they also have that –>
<!– permission group even though it has not been explicitly granted. –>
<!– –>
<!– =========== –>
<!– Full access –>
<!– =========== –>
<!– –>
<!– By default this is exposed for all objects unless inherited objects choose to –>
<!– expose only selected objects at the object level. –>
<!– –>
<permissionGroup name="FullControl" expose="true" allowFullControl="true" />
<!– ============================================= –>
<!– Convenient groupings of low level permissions –>
<!– ============================================= –>
<permissionGroup name="Read" expose="true" allowFullControl="false">
<includePermissionGroup type="sys:base" permissionGroup="ReadProperties"/>
<includePermissionGroup type="sys:base" permissionGroup="ReadChildren"/>
<includePermissionGroup type="sys:base" permissionGroup="ReadContent"/>
</permissionGroup>
<permissionGroup name="Write" expose="true" allowFullControl="false">
<includePermissionGroup type="sys:base" permissionGroup="WriteProperties"/>
<includePermissionGroup type="sys:base" permissionGroup="WriteContent"/>
</permissionGroup>
<permissionGroup name="Delete" expose="true" allowFullControl="false">
<includePermissionGroup type="sys:base" permissionGroup="DeleteNode"/>
<includePermissionGroup type="sys:base" permissionGroup="DeleteChildren"/>
</permissionGroup>
<permissionGroup name="AddChildren" expose="true" allowFullControl="false">
<includePermissionGroup type="sys:base" permissionGroup="CreateChildren"/>
<includePermissionGroup type="sys:base" permissionGroup="LinkChildren"/>
</permissionGroup>
<permissionGroup name="Execute" allowFullControl="false" expose="false">
<includePermissionGroup type="sys:base" permissionGroup="ExecuteContent"/>
</permissionGroup>
<!– Groups for low level permissions –>
<permissionGroup name="ReadProperties" expose="true" allowFullControl="false" />
<permissionGroup name="ReadChildren" expose="true" allowFullControl="false" />
<permissionGroup name="WriteProperties" expose="true" allowFullControl="false" />
<permissionGroup name="ReadContent" expose="false" allowFullControl="false" />
<permissionGroup name="WriteContent" expose="false" allowFullControl="false" />
<permissionGroup name="ExecuteContent" expose="false" allowFullControl="false" />
<permissionGroup name="DeleteNode" expose="true" allowFullControl="false" />
<permissionGroup name="DeleteChildren" expose="true" allowFullControl="false" />
<permissionGroup name="CreateChildren" expose="true" allowFullControl="false" />
<permissionGroup name="LinkChildren" expose="true" allowFullControl="false" />
<permissionGroup name="DeleteAssociations" expose="true" allowFullControl="false" />
<permissionGroup name="ReadAssociations" expose="true" allowFullControl="false" />
<permissionGroup name="CreateAssociations" expose="true" allowFullControl="false" />
<permissionGroup name="ReadPermissions" expose="true" allowFullControl="false" />
<permissionGroup name="ChangePermissions" expose="true" allowFullControl="false" />
<permissionGroup name="Flatten" expose="true" allowFullControl="false" />
<!– =========== –>
<!– Permissions –>
<!– =========== –>
<!– The permission to read properties on a node –>
<!– –>
<!– The properties of a node may ony be read if there is read access to the parent –>
<!– node. ReadChildren access to the parent node is recursive for all nodes from –>
<!– which the node inherits permissions. Access is required down the permission –>
<!– tree at all points. –>
<!– –>
<permission name="_ReadProperties" expose="false" >
<grantedToGroup permissionGroup="ReadProperties" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to read the children of a node –>
<!– –>
<!– This permission is recursive. It requires the same permission is granted to –>
<!– all of the parent nodes from which this node inherits permissions –>
<!– –>
<permission name="_ReadChildren" expose="false" >
<grantedToGroup permissionGroup="ReadChildren" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to write to the properties of a node –>
<!– –>
<!– This permission includes adding aspects to a node as they are stored as –>
<!– a property. –>
<!– –>
<permission name="_WriteProperties" expose="false" >
<grantedToGroup permissionGroup="WriteProperties" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to delete a node –>
<!– –>
<!– A node can only be deleted if there is delete permission on the node, if the –>
<!– node is accesible via its parent, and if the node can be deleted from its –>
<!– parent. Currently, there is no check that all the children can be deleted. –>
<!– This check can be added but requires more work so the UI is not checking this –>
<!– permission just to show the delete icon. –>
<!– –>
<!– The permission to read content. –>
<permission name="_ReadContent" expose="false">
<grantedToGroup permissionGroup="ReadContent"/>
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to write content. –>
<permission name="_WriteContent" expose="false">
<grantedToGroup permissionGroup="WriteContent" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– Execute permission on content. –>
<permission name="_ExecuteContent" expose="false">
<grantedToGroup permissionGroup="ExecuteContent" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<permission name="_DeleteNode" expose="false" >
<grantedToGroup permissionGroup="DeleteNode" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
<requiredPermission on="parent" name="_DeleteChildren" implies="false"/>
<requiredPermission on="node" name="_DeleteChildren" implies="false"/>
–>
<!– Remove the recursive check for now for performance –>
<!– TODO: have one permission to check for delete on an item and one to check –>
<!– child permissions when delete is called on the node service –>
<!– <requiredPermission on="children" name="_DeleteNode" implies="false"/> –>
</permission>
<!– The permission to delete children of a node –>
<!– –>
<!– At the moment this includes both unlink and delete –>
<!– –>
<permission name="_DeleteChildren" expose="false" >
<grantedToGroup permissionGroup="DeleteChildren" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to create new nodes –>
<permission name="_CreateChildren" expose="false" >
<grantedToGroup permissionGroup="CreateChildren" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false" />
–>
</permission>
<!– The permission to link nodes –>
<permission name="_LinkChildren" expose="false" >
<grantedToGroup permissionGroup="LinkChildren" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to delte associations between nodes (not children) –>
<permission name="_DeleteAssociations" expose="false" >
<grantedToGroup permissionGroup="DeleteAssociations" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to read associations –>
<permission name="_ReadAssociations" expose="false" >
<grantedToGroup permissionGroup="ReadAssociations" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false" />
–>
</permission>
<!– The permission to create associations –>
<permission name="_CreateAssociations" expose="false" >
<grantedToGroup permissionGroup="CreateAssociations" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false" />
–>
</permission>
<!– ==================================================== –>
<!– Permissions related to the management of permissions –>
<!– ==================================================== –>
<!– The permission to read the permissions on a node –>
<permission name="_ReadPermissions" expose="false" >
<grantedToGroup permissionGroup="ReadPermissions" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– The permission to the change the permissions associated with a node –>
<permission name="_ChangePermissions" expose="false" >
<grantedToGroup permissionGroup="ChangePermissions" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
<!– AVM specific –>
<permission name="_Flatten" expose="false" >
<grantedToGroup permissionGroup="Flatten" />
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" implies="false"/>
–>
</permission>
</permissionSet>
<!– ================================================ –>
<!– Permissions available to all content and folders –>
<!– ================================================ –>
<permissionSet type="cm:cmobject" expose="selected">
<!– Kept for backward compatibility - the administrator permission has –>
<!– been removed to aviod confusion –>
<permissionGroup name="Administrator" allowFullControl="true" expose="false" />
<!– A coordinator can do anything to the object or its childeren unless the –>
<!– permissions are set not to inherit or permission is denied. –>
<permissionGroup name="Coordinator" allowFullControl="true" expose="true" />
<!– A collaborator can do anything that an editor and a contributor can do –>
<permissionGroup name="Collaborator" allowFullControl="false" expose="true">
<includePermissionGroup permissionGroup="Editor" type="cm:cmobject" />
<includePermissionGroup permissionGroup="Contributor" type="cm:cmobject" />
</permissionGroup>
<!– A contributor can create content and then they have full permission on what –>
<!– they have created - via the permissions assigned to the owner. –>
<permissionGroup name="Contributor" allowFullControl="false" expose="true" >
<!– Contributor is a consumer who can add content, and then can modify via the –>
<!– owner permissions. –>
<includePermissionGroup permissionGroup="Consumer" type="cm:cmobject"/>
<includePermissionGroup permissionGroup="AddChildren" type="sys:base"/>
<includePermissionGroup permissionGroup="ReadPermissions" type="sys:base" />
</permissionGroup>
<!– An editor can read and write to the object; they can not create –>
<!– new nodes. They can check out content into a space to which they have –>
<!– create permission. –>
<permissionGroup name="Editor" expose="true" allowFullControl="false" >
<includePermissionGroup type="cm:cmobject" permissionGroup="Consumer"/>
<includePermissionGroup type="sys:base" permissionGroup="Write"/>
<includePermissionGroup type="cm:lockable" permissionGroup="CheckOut"/>
<includePermissionGroup type="sys:base" permissionGroup="ReadPermissions"/>
</permissionGroup>
<!– The Consumer permission allows read to everything by default. –>
<permissionGroup name="Consumer" allowFullControl="false" expose="true" >
<includePermissionGroup permissionGroup="Read" type="sys:base" />
</permissionGroup>
<!– CUSTOM CONFIG: The CheckOutContributor permission allows check out, etc. –>
<permissionGroup name="CheckOutContributor" allowFullControl="false" expose="true" >
<includePermissionGroup permissionGroup="Read" type="sys:base" />
<includePermissionGroup type="sys:base" permissionGroup="WriteProperties"/>
<includePermissionGroup type="cm:lockable" permissionGroup="CheckOut"/>
<includePermissionGroup type="sys:base" permissionGroup="ReadPermissions"/>
<includePermissionGroup type="sys:base" permissionGroup="AddChildren" />
</permissionGroup>
<!– records permission –>
<!– Should be tied to the aspect –>
<!– onwership should be removed when using this permission –>
<permissionGroup name="RecordAdministrator" allowFullControl="false" expose="false">
<includePermissionGroup type="sys:base" permissionGroup="ReadProperties"/>
<includePermissionGroup type="sys:base" permissionGroup="ReadChildren"/>
<includePermissionGroup type="sys:base" permissionGroup="WriteProperties"/>
<includePermissionGroup type="sys:base" permissionGroup="ReadContent"/>
<includePermissionGroup type="sys:base" permissionGroup="DeleteChildren"/>
<includePermissionGroup type="sys:base" permissionGroup="CreateChildren"/>
<includePermissionGroup type="sys:base" permissionGroup="LinkChildren"/>
<includePermissionGroup type="sys:base" permissionGroup="DeleteAssociations"/>
<includePermissionGroup type="sys:base" permissionGroup="CreateAssociations"/>
</permissionGroup>
<!– avm related permissions –>
<!– AVM website specific roles. –>
<permissionGroup name="ContentManager" allowFullControl="true" expose="false" />
<permissionGroup name="ContentPublisher" allowFullControl="false" expose="false">
<includePermissionGroup permissionGroup="Collaborator" type="cm:cmobject" />
</permissionGroup>
<permissionGroup name="ContentContributor" allowFullControl="false" expose="false">
<includePermissionGroup permissionGroup="Contributor" type="cm:cmobject" />
</permissionGroup>
<permissionGroup name="ContentReviewer" allowFullControl="false" expose="false">
<includePermissionGroup permissionGroup="Editor" type="cm:cmobject" />
</permissionGroup>
</permissionSet>
<!– =============================== –>
<!– Permissions specific to content –>
<!– =============================== –>
<permissionSet type="cm:content" expose="selected">
<!– Content specific roles. –>
<permissionGroup name="Coordinator" extends="true" expose="true"/>
<permissionGroup name="Collaborator" extends="true" expose="true"/>
<permissionGroup name="Contributor" extends="true" expose="true"/>
<permissionGroup name="Editor" extends="true" expose="true"/>
<permissionGroup name="Consumer" extends="true" expose="true"/>
<permissionGroup name="RecordAdministrator" extends="true" expose="false"/>
<!– CUSTOM CONFIG: The CheckOutContributor permission allows check out, etc. –>
<permissionGroup name="CheckOutContributor" allowFullControl="false" expose="true" />
</permissionSet>
<permissionSet type="cm:folder" expose="selected">
<!– Content folder specific roles. –>
<permissionGroup name="Coordinator" extends="true" expose="true"/>
<permissionGroup name="Collaborator" extends="true" expose="true"/>
<permissionGroup name="Contributor" extends="true" expose="true"/>
<permissionGroup name="Editor" extends="true" expose="true"/>
<permissionGroup name="Consumer" extends="true" expose="true"/>
<permissionGroup name="RecordAdministrator" extends="true" expose="false"/>
<!– CUSTOM CONFIG: The CheckOutContributor permission allows check out, etc. –>
<permissionGroup name="CheckOutContributor" allowFullControl="false" expose="true" />
</permissionSet>
<!– ========================================== –>
<!– Permissions specific to avm website folder –>
<!– ========================================== –>
<permissionSet type="wcm:avmfolder" expose="selected"> –>
<permissionGroup name="ContentManager" extends="true" expose="true" />
<permissionGroup name="ContentPublisher" extends="true" expose="true" />
<permissionGroup name="ContentContributor" extends="true" expose="true" />
<permissionGroup name="ContentReviewer" extends="true" expose="true" />
</permissionSet>
<permissionSet type="wcm:avmplainfolder" expose="selected"> –>
<permissionGroup name="ContentManager" extends="true" expose="true" />
<permissionGroup name="ContentPublisher" extends="true" expose="true" />
<permissionGroup name="ContentContributor" extends="true" expose="true" />
<permissionGroup name="ContentReviewer" extends="true" expose="true" />
</permissionSet>
<permissionSet type="wcm:avmlayeredfolder" expose="selected"> –>
<permissionGroup name="ContentManager" extends="true" expose="true" />
<permissionGroup name="ContentPublisher" extends="true" expose="true" />
<permissionGroup name="ContentContributor" extends="true" expose="true" />
<permissionGroup name="ContentReviewer" extends="true" expose="true" />
</permissionSet>
<permissionSet type="wcm:avmcontent" expose="selected"> –>
<permissionGroup name="ContentManager" extends="true" expose="true" />
<permissionGroup name="ContentPublisher" extends="true" expose="true" />
<permissionGroup name="ContentContributor" extends="true" expose="true" />
<permissionGroup name="ContentReviewer" extends="true" expose="true" />
</permissionSet>
<permissionSet type="wcm:avmplaincontent" expose="selected"> –>
<permissionGroup name="ContentManager" extends="true" expose="true" />
<permissionGroup name="ContentPublisher" extends="true" expose="true" />
<permissionGroup name="ContentContributor" extends="true" expose="true" />
<permissionGroup name="ContentReviewer" extends="true" expose="true" />
</permissionSet>
<permissionSet type="wcm:avmlayeredcontent" expose="selected"> –>
<permissionGroup name="ContentManager" extends="true" expose="true" />
<permissionGroup name="ContentPublisher" extends="true" expose="true" />
<permissionGroup name="ContentContributor" extends="true" expose="true" />
<permissionGroup name="ContentReviewer" extends="true" expose="true" />
</permissionSet>
<permissionSet type="wca:webfolder" expose="selected"> –>
<permissionGroup name="ContentManager" extends="true" expose="true" />
<permissionGroup name="ContentPublisher" extends="true" expose="true" />
<permissionGroup name="ContentContributor" extends="true" expose="true" />
<permissionGroup name="ContentReviewer" extends="true" expose="true" />
</permissionSet>
<!– ============================================== –>
<!– Permissions associated with the Ownable aspect –>
<!– ============================================== –>
<permissionSet type="cm:ownable" expose="selected">
<!– Permission control to allow ownership of the node to be taken from others –>
<permissionGroup name="TakeOwnership" requiresType="false" expose="false">
<includePermissionGroup permissionGroup="SetOwner" type="cm:ownable" />
</permissionGroup>
<permissionGroup name="SetOwner" requiresType="false" expose="false"/>
<!– The low level permission to control setting the owner of a node –>
<permission name="_SetOwner" expose="false" requiresType="false">
<grantedToGroup permissionGroup="SetOwner" />
<!– require to be able to reach the node and set properties in the node –>
<!– Commented out parent permission check …
<requiredPermission on="parent" name="_ReadChildren" />
–>
<requiredPermission on="node" type="sys:base" name="_WriteProperties" />
</permission>
</permissionSet>
<!– =================================================== –>
<!– Permission related to lock, check out and check in. –>
<!– =================================================== –>
<permissionSet type="cm:lockable" expose="selected">
<!– At the moment these permissions are hidden so they do not appear in the list –>
<!– of permissions. –>
<!– Check Out permission - exposed for all object types –>
<permissionGroup name="CheckOut" requiresType="false" expose="false">
<includePermissionGroup permissionGroup="Lock" type="cm:lockable" />
</permissionGroup>
<!– Check In permission - only exposed when the lockable aspect is present –>
<permissionGroup name="CheckIn" requiresType="true" expose="false">
<includePermissionGroup permissionGroup="Unlock" type="cm:lockable" />
</permissionGroup>
<!– Cancel Check Out permission - only exposed for the lockable aspect is present –>
<permissionGroup name="CancelCheckOut" requiresType="true" expose="false">
<includePermissionGroup permissionGroup="Unlock" type="cm:lockable" />
</permissionGroup>
<permissionGroup name="Lock" requiresType="false" expose="false"/>
<permissionGroup name="Unlock" requiresType="true" expose="false"/>
<!– Low level lock permission –>
<permission name="_Lock" requiresType="false" expose="false">
<grantedToGroup permissionGroup="Lock" />
<requiredPermission on="node" type="sys:base" name="WriteProperties"/>
</permission>
<!– Low level unlock permission –>
<permission name="_Unlock" requiresType="true" expose="false">
<grantedToGroup permissionGroup="Unlock" />
</permission>
</permissionSet>
<!– ================== –>
<!– Global permissions –>
<!– ================== –>
<!– –>
<!– Global permissions apply regardless of any particular node context. –>
<!– They can not be denied by the permissions set on any node. –>
<!– –>
<!– Admin can do anything to any ndoe –>
<globalPermission permission="FullControl" authority="ROLE_ADMINISTRATOR"/>
<!– For now, owners can always see, find and manipulate their stuff –>
<globalPermission permission="FullControl" authority="ROLE_OWNER"/>
<!– Unlock is granted to the lock owner –>
<globalPermission permission="Unlock" authority="ROLE_LOCK_OWNER"/>
<!– Check in is granted to the lock owner –>
<globalPermission permission="CheckIn" authority="ROLE_LOCK_OWNER"/>
<!– Cancel check out is granted to lock owner –>
<globalPermission permission="CancelCheckOut" authority="ROLE_LOCK_OWNER"/>
<!– CUSTOM CONFIG: WriteContent granted to lock owner –>
<globalPermission permission="WriteContent" authority="ROLE_LOCK_OWNER"/>
<!– Users need to be able to remove stuff from their own sandbox –>
<globalPermission permission="Flatten" authority="ROLE_WCM_STORE_OWNER" />
</permissions>
I defined CheckOutContributor in the config then gave all users only that role in the Company Home space.
I had trouble removing FullControl from the creator of a piece of content because of the globalPermission for ROLE_OWNER because if there is no owner property, the creator property is used. Restricting the ROLE_OWNER's permissions caused errors when adding content; I'll open a Jira ticket for it sometime. I got around this by adding a content rule that added the aspect ownable to everything, so all content would have a blank owner.
Related Content
- Share ignores custom form extensions and replace="true" for cm:person layouts (userid & profile form in Alfresco Forum
- Building Permission-Aware Semantic Search on Alfresco with hxpr and Content Lake in Alfresco Blog
- 15 Extra Transform Engines for Alfresco: OCR, AI, Whisper, PII Redaction and More in Alfresco Blog
- A practical walkthrough of the Alfresco Model Context Protocol in Alfresco Blog
- OpenSearchCon Europe 2026 for Alfresco Developers in Alfresco Blog
Getting started
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.
