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.

Role for creating content only

sobotka

Hi,
is it possible to create a role which would allow only to create a content in a space and not to see other contents within the space which was created by other users ?

I tried this:
      <permissionGroup name="Proposer" allowFullControl="false" expose="true" >
          <includePermissionGroup type="sys:base" permissionGroup="CreateChildren"/>
      </permissionGroup>
But the user assigned to this role does not see the space at all !

So I tried:
      <permissionGroup name="Proposer" allowFullControl="false" expose="true" >
          <includePermissionGroup type="sys:base" permissionGroup="CreateChildren"/>
          <includePermissionGroup type="sys:base" permissionGroup="ReadChildren"/>
      </permissionGroup>
But the result was the same as above.

So I created this:
      <permissionGroup name="Proposer" allowFullControl="false" expose="true" >
          <includePermissionGroup type="sys:base" permissionGroup="CreateChildren"/>
          <includePermissionGroup type="sys:base" permissionGroup="ReadChildren"/>
          <includePermissionGroup type="sys:base" permissionGroup="ReadProperties"/>
      </permissionGroup>
But now the user can see items (its metadata) created by others which not desired.

Any idea ?
Petr

Find more posts tagged with

Comments

invictus9

The first idea I had for this situation is to use the standard permissions, and create essentially a drop folder. The content rule added to the drop folder moves the document to the actual working area where it can be reviewed. That way, Contributors can add new documents to the area without anyone else seeing them.

sobotka

The first idea I had for this situation is to use the standard permissions, and create essentially a drop folder. The content rule added to the drop folder moves the document to the actual working area where it can be reviewed. That way, Contributors can add new documents to the area without anyone else seeing them.

If I understand it correctly this would mean to create a special working folder for each contributor, right ? This is not possible as there are many potential contributors.

Petr

sobotka

Anyway, is this correct behavior not to see the space where I have the CreateChildren (and ReadChildren) permission as I described it in my original post ??

Petr

invictus9

The first idea I had for this situation is to use the standard permissions, and create essentially a drop folder. The content rule added to the drop folder moves the document to the actual working area where it can be reviewed. That way, Contributors can add new documents to the area without anyone else seeing them.

If I understand it correctly this would mean to create a special working folder for each contributor, right ? This is not possible as there are many potential contributors.

Petr

No. Just one drop folder, where any of your contributors would drop a file into. Once the file has been uploaded, the work flow that is triggered would move the file somewhere else. The drop folder remains empty, so nobody can see anybody else's files.