Forums (Obsolete)

Member

ta5ae - 7/7/2005 11:26:27 AM

User - Starting Alias Path - Not restricting edit capability when browsing site

I was hoping to use the starting path of a user account to limit the scope of the user's permissions.

When I log on as a user where the starting alias path is say; /support, the contents is restricted to this sub folder. However, when browsing the Site in edit mode, areas not under this sub folder are available to be edited.

Is there something else I should be setting or is this a bug in the expected behavior?

Extract from User Guide:

Starting Alias Path

Alias path of the root document displayed in the Content module. It can be used either with multilingual support or for restricting user's access for editing only particular part of the Web site.

Guest

admin - 7/7/2005 6:34:10 PM

Re: User - Starting Alias Path - Not restricting edit capability when browsing site

I'm sorry for the delay in answering your question.

Unfortunately, the starting path restricts only the access in the Content section. If you need to restrict permissions for documents in both Content and Site sections, you can use document-level permissions instead. You can set up document-level permissions in the Content section, by clicking the "Permissions" button.

Member

ta5ae - 7/8/2005 9:22:32 AM

Re: User - Starting Alias Path - Not restricting edit capability when browsing site

Thank you so much for your feedback. I have now created a specific role for this user type and done the following to ensure users can only add to the given sub folder.

Permission settings I used

Modules

Role A - CMS Content - unfold tree

Files

Role A - Root Folder - deny all
Role A - Sub Folder - allow read, write, etc

Member

ta5ae - 11/10/2005 10:33:25 AM

Re: Restricting user permissions to a particular folder and document type

Hi, back again. Does anyone know how to restrict a role to only one document type and only one folder/ page item.

I created a role to add say just articles, from the global permissions tab. Then tried to implement the above to restrict the folder access, see below. However, this gives rights over all document types not just Articles in that sub folder.

Modules

Role A - CMS Content - unfold tree, read
Role A - Articles - create, read, modify, read

Files

Role A - Root Folder - deny all
Role A - Sub Folder/Page Item - allow read, write, etc

Guest

admin - 11/10/2005 10:52:37 AM

Re: Restricting user permissions to a particular folder and document type

Hello,

the only solution for this kind of permission settings is to place the articles into some special "article container" and grant user with permissions for creating/modifying documents in that "article container". The "article container" will be created as a new document type without custom fields and it will allow only articles as child documents.

Best Regards,


Member	elizabethm - 2/3/2009 9:19:03 AM RE:Re: Restricting user permissions to a particular folder and document type I want to do something similar - I'm looking at Kentico to create a simple site and I don't want the end user to be overwhelmed by all the options, in reality they'll only need a few document types. Can you give me more details about creating an "article container"?

Kentico Support

kentico_jurajo - 2/4/2009 2:41:41 AM

RE:Re: Restricting user permissions to a particular folder and document type

Hi,

First of all I would like to notice you that this thread is pretty old and in section for version 1.x which is no longer supported. Could you please post your questions into appropriate section? It can help us to give you more accurate answer because we will know approximately which version you are using.

So, I assume that you are no longer using 1.x version but newer. Here you can find more information about the permissions that could be set for the users and their roles.

Best Regards,
Juraj Ondrus