The error message says that the user doesn’t have ‘namespace’ permission when trying to access the Articles namespace. First, make sure the Articles namespace exists. (System -> Namespaces). While you’re there, check the paths for that namespace. They should be:
What I think is happening is that Articles needs to access the Articles Namespace to find out where the Articles language files are. At some point, the current user doesn’t have the namespace permission in the current context. You might have to create a Context Access ACL entry for another context (mgr, web, etc.).
But I dont get the right idea, what modx needs here. The namespace permission is checked in the policy and all contexts have assigned the usergroup with that policy (with authority 10). So, is there a need to grant access to articles namespace explicitly, and how to do it?
BTW, I’m sure you know this, but for others reading this, the most powerful authority level in terms of capabilities is 0. The higher the number the less authority you have.
Maybe this is what you mean, but I’d recommend creating a new user group for the user and giving them admin rights there, rather than making them a member of the Administrator group.
That will give you more flexibility in the future.