Which actions/operations reflect the permissions of an "Administrator"

Being a project administrator is the same as having the "Process" permission box checked in permissions section of the process configuration page/editor.

I think we had the discussion before (https://jazz.net/forum/questions/231048/what-capabilities-does-a-projectteam-area-administrator-have) . The users (with repository role JazzUser) that are maintained in the Administrators section of a process area don't automatically have a role other than the default role or any permission other than the permissions granted to everyone in that area.

What being added to the Administrators section however provides them with, is an administrative override that allows them to save all changes they do to that area especially (see here)

1. Define roles
2. Assign themselves roles
3. Assign permissions to roles

Only once they have permissions for roles they have in that area, they can perform these operations.

With respect to the other details, I don't know that by heart, but would assume that you are looking at the right stuff.

As far as I know a lot of the applications share the foundation mechanism, however I would be careful with making the assumption that this will always be the case. I think you have to check for each application if that is the case.

I think the summary here is, that the administrators ALWAYS have the permission to save the process configuration.

That means the members of the "Administrators" can create new roles and assign them permissions and give themselves these roles.

Users with no role that allows to save the process configuration can not do that.

So if you have a role admin that allows to save the process configuration, all users that have this role have effectively the permissions the members of "administators" have.