Access to the document by id

Hello. I need to block access to the document by id (www.sitename.com/123). How can I do this?

If you’re posting about a bug, please state all of your Environment information in your post: Version of MODx, Traditional or Advanced distribution (for Revo), Server OS, Server Version, PHP Version, MySQL Version (client and server), is pdo_mysql installed, your Browser type and version, if you are using any opcode caching such as eAccelerator, APC, winCache, xCache, etc; any relevant errors in core/cache/logs/error.log, and any other environment data we should know. We can’t help you without that information.

In order to help you, we also need to know *who* you want to block access to and whether you want to block access in the front end or the Manager (or both).

I need to block access to all on the front end

We’ll help you after you mention at least your modx version.
Evo and Revo have different permission systems.
Quote from: goldsky at Aug 01, 2011, 02:51 AM

If you’re posting about a bug, please state all of your Environment information in your post: Version of MODx, Traditional or Advanced distribution (for Revo), Server OS, Server Version, PHP Version, MySQL Version (client and server), is pdo_mysql installed, your Browser type and version, if you are using any opcode caching such as eAccelerator, APC, winCache, xCache, etc; any relevant errors in core/cache/logs/error.log, and any other environment data we should know. We can’t help you without that information.

MODx Revolution 2.0.8-pl (traditional)

Put the resource in a resource group and then right-click on the Administrators user group and select "Update User Group"

On the Resource Group Access tab, create an ACL entry for that user group with a Minimum Role of admin Super User, a Context of ’web’ and a Policy of "resource."

If you have other front-end contexts, create more entries (one for each front-end context) just like that one except for the Context field.

That will protect that document in the front end.

If you want to hide it in the Manager, create another entry just like it, but with a context of ’mgr’.

whether the decision easier? if only to close the user access to front end pages that are open by id?

The bottom line is that you should create a specific group of the restricted ’documents’ (or ’resources’ in MODX term) and the group of the limited access users.

From there, you start specify the limitation of the user group to the resource group.

It doesn’t matter about ID or FURL.
The group does.