Prarie, isn't that what the Content Manager Role is for?

As for the other question - what would be the definition of an admin? It's the person who has complete control over the system and can do whatever needs to be done.

If you have a mainframe, there's an admin who can control everything on the mainframe. If you have a Novell network, there's an admin who can access and control anything on the network. Someone has to have that role, but as Waz says, that person or person(s) should be selected carefully.

Some functions like making shared reports into standard reports, creating domains, moving reports between users, have to be done by someone who can see everything (users, reports, domains, etc.) and has rights to do everything.
I wouldn't consider that a security problem unless the admin personally is a security risk - then that's an HR problem, not a system problem.

Well Darin...I'm not sure...can they change code? I'm just learning to be a MR adminstrator. I've been a Developer and Production Support role where I'm working now.

quote:

It's the person who has complete control over the system and can do whatever needs to be done.

That may be the case in some cases, but I would have thought a typical admin would have a role to administer the domains, i.e. create domains, create/change/delete users, deploying from "dev" to "Prod", etc.

As for access to reports, running, deleting, changing, I think would be on a site by site basis.

A more structured site would have specific roles, where a smaller or more general site would not.

I think there is no way to secure the code from the administrator but you can control access to the data through your database security. Add a login routine requiring a password to your programs for restricted database access. You have to remember that if you do this you probably won't be able to run jobs through report caster.