Answered Create resource groups, now site can't be viewd unless you are logged in.

I needed to give a user access to only one page of a website. A post on these boards suggested that I would need to create two resource groups. One would contain all the pages of the site, the other just the single page. I did that and assigned my standard logins to the "all" resource group and then the restricted user to the resource group with the single page. This seemed to work fine until I got a call from the client saying their website was down. Doing what I did made the site unavailable unless you were logged in. What settings do I need to ensure the resource groups do not affect the actual site, but only the manager?

Lastly, I assume that if users in the "all" resource group add a new page, it will automatically be included in their resource group without the new page having to be manually added into that group?

Thank you for your help!

-Steve

sounds like you've only allowed mgr access to the resource group where you're trying to give access for the one page. If you drag that single resource into their allowed group then they will have access to it, but only in the manager. You need to ensure they also have web access if you want them to access that page on the web.

Bob has a great article on his website about making member only pages
https://bobsguides.com/user-specific-pages.html

As you're only looking to restrict/give access to just one resource though depending on your use purpose you may want to look at the pagelocker extra which will just allow you to set a password on the page that the user has to enter to view the page - again depends on your use purposes though but if it's just to demonstrate a preview of a page to a client then its usually a quicker method than going through ACLs

Sorry for the confusion, I am referring only to the manager and not the site itself. There are no restricted pages on the site. I am simply trying to limit a user to only have the ability to update a single page. As stated before, dragging the single resource into the group does not allow them to see it. The parent has to be drug in for them to see it, but that results in them having access to several other pages that I don't want.

In order for the user to update that page, they will have to have access to all pages above it in the tree. The usual method is to give them access to the page itself with a Policy that allows editing (e.g., ContentEditor), and give them access to the pages above it with a policy of Load, List, and View. Load only might work but I don't think so.

You might also consider NewsPublisher. That would let the user log in in the front end and edit pages. Keeping them out of the Manager makes things a lot simpler.

If the user is the original author of the page, or could be set as the author, it would be even easier. This tag on the page itself (or in its template), would show the user an "Edit" button on that page alone that would launch NewsPublisher and let them edit the page: