Unable to Add Document without resource_tree permission

[GarretOverstreet]

The tree is hidden for some users, though I am unable to use the "Add New Resource" button on GCK containers without having the resource_tree permission selected.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/10014923-unable-to-add-document-without-resource_tree-permission?utm_campaign=plugin&utm_content=tracker%2F570466&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F570466&utm_medium=issues&utm_source=github).

[goldsky]

GridClassKey doesn't use tree, maybe you're confusing this with Collections?
The "Add New Resource" button requires "new_document" permission to the usergroup.

[GarretOverstreet]

Definitely not Collections, I'm a big fan of GCK and use it for several sites.

"new_document" is applied to the user group. The only change I make in my ACL Policy is "resource_tree" (as to hide the tree completely) and it seems to toggle off and on whether the "Add" button works.

I tested it on a clean install, along with two other sites, and receive the same results. Unselecting the "resource_tree" permission, oddly enough, makes the "add new document" button go nowhere. Give it a test on a sub-admin account (I'm on 2.3.3 just for a heads up.)

[goldsky]

Hmm... ok, I'll investigate this. Thanks for reporting.

[goldsky]

Have you checked this? https://rtfm.modx.com/extras/revo/gridclasskey#GridClassKey-Permissions

[neehad]

Hi goldsky, is there any trick to avoid this issue?