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.

The permissions of users

sroy

Hi,

I would like to know the permissions provided by Alfresco and what the users are allowed to do with
the permissions such as collaborator, consumer, contributor and manager. Is it possible to restrict view
access to a space to an existing user of the space?

Find more posts tagged with

Comments

newmember

The big thing that got me on the permissions for a few weeks was "Inherit Parent Space Permissions" I just didn't notice it.

For permissions I log in as admin and go to "Administration Console" there you can add groups and users.
I suggest adding a group then assigning a user to the group.

Open up any "Space" select "More Actions" then select "Manage Space Users"
OK here "EVERYONE GROUP_EVERYONE Consumer" is on the list because they are inherit permissions form the parent folder. You need to turn this off to start restricting access to Everyone.

Select "Invite" then search and highlight a "user" or "group" in the first box then select theie access rights for that space THEN click the "Add to List" now you see what you added at the bottom under "Name".
Do this more times if need to add more user or groups to this space.
Then select "Next"

Now you can choose to send the new users and/or groups an email telling them they have access.

Now go back to the that "Space" select "More Actions" then select "Manage Space Users"
Now you can delete the "Everyone" user from that folder and check that your new users and/or groups are there.

All done.

Use the "Inherit Parent Space Permissions" for any sub spaces you may create.

Cheers

jefrainmx

Were you able to hide information from other contributers? i want to do something similar, for example Contributer One create a document but Contributer Two cannot view it.

jefrainmx

Were you able to hide information from other contributers? i want to do something similar, for example Contributer One create a document but Contributer Two cannot view it.

The workaround i do is extend permissionDefinition.xml and create a new permission under:

   <permissionSet type="cm:folder" expose="selected">

      <!– Content folder specific roles.                                                       –>

      <permissionGroup name="Coordinator" extends="true" expose="true"/>
..

     <permissionGroup name="RecordAdministrator" extends="true" expose="false"/>
//Specific to my app,
      <permissionGroup name="Employee" allowFullContol="false" expose="true">
           <includePermissionGroup type="sys:base" permissionGroup="ReadProperties"/>
           <includePermissionGroup type="sys:base" permissionGroup="AddChildren"/>
      </permissionGroup>

   </permissionSet>

With this role the user can access and add files to the folder but cannot see documents not even his own documents.

- Make sure you uncheck the inheritance indicator on the folder you are testing
- Assign this role to a user or group and give him permission tot he folder to test