CA Not Respecting Drupal's Built-in Permissions?

According to the project homepage, it looks like CA should respect Drupal's built-in permissions for Drupal 6. I understand this to mean that when I set (or don't set) permissions for a role (admin/user/permissions), those permissions (or lack thereof) should still apply even when I give the role "Edit any content" access on the Content Access tab for a particular node. (I do have Per Node access control enabled for this content type). For instance, if a role does not have permission to create URL aliases but does have access to edit page content via CA, I would expect that users in this role would be able to edit the content but that they would not see the URL aliases options on the node edit screen.

What I'm trying to do is allow users in a particular role to edit page content, but I don't want them to be able to see or edit things like the URL path settings, Menu settings, Vocabularies, Input format, etc. At present, I have a user in a role that has almost no permissions (and what they do have is mostly cascading down from the authenticated user role). This user has access to edit any content on one page node, but they can see and administer all sorts of things they shouldn't have access to.

I do have Organic Groups Access Control 6.x-2.1 installed and in use on the site for a different set of content types. Not sure if this could be part of the problem? OGAC seemed to be working properly for OG content types after I lowered the Give content node grants priority: setting to -10 for those OG content types. I've considered turning OGAC off temporarily and rebuilding permissions to see if that may be the problem, but I'm hesitant to potentially "break" that working part of the site without being sure it's the root of the issue.

I have tried rebuilding permissions, resaving the node in question, and bumping the Give content node grants priority: up and down for the content type in question.

Any thoughts on why the permissions don't seem to be pulling through for CA editors? Not sure if this is just something in need of documentation, a support request, a conflict with another module, or a bug!

New for the Drupal 6 version:

* it respects and makes use of drupal's built in permissions as far as possible. Which means the access control settings provided by this module takes them into account and provides you a good overview about the really applied access control settings for a content type or content node - on just one screen! Read more about the drupal 6 version here.