Profile permission: Admin doesn't have permission by default ?

Permission to what? I use the standard user_access() function which does that check for super user. http://api.drupal.org/api/function/user_access/6

There seems to be a misunderstand as to what this module does, as I've gotten issue like this before. If you want to restrict who can edit/view a field user profile_permission.

This module is designed to "define a data-structure".

What that means is that say I have a teacher and student...a student has a GPA and a teacher has a salary....those fields should never be on the other role...not even for administrator viewing. It defines a data-structure without having to make separate tables or w/e.

If you have a common user field, but want to restrict who can see/edit it then use profile_permission.

I'm not sure if this is what was asked for but I am having similar issues. Let me explain.

I am an "admin" on a particular site. However I am an admin via a role and not the actual user #1 admin.

When a new module is installed on the site I can not access it until the user #1 admin enables the admin role (of which I am a part of ) for it.

I am thinking that the original poster of this message was asking if there is a way to enable a default behavior of enabling all new modules with admin role privileges.

Put another way Drupal always allows user #1 to edit new modules but does not allow "admin role" users to mess with new modules until user #1 has turned on editing for that "admin role" for that new module. It's hard to explain but I hope somebody understands this.

To put is a final third way, a person with the "admin role" is not truely an admin because they can't install and configure modules without the help of user #1.

Is there a module for telling drupal to enable all new modules with all permissions to the admin role?

Ha ha... Found it. http://drupal.org/project/adminrole