How to accomodate

I have a user (also my boss) who wants the system to work a specific way
which amounts to this:
1) ability to create an application as a developer
2) ability to deploy that application anywhere on any server in the network
3) ability to not need to worry about user permissions
I don't know how to explain how Windows Authentication works well enough -
in other words, in a syllable or so, that explains why this may not be
possible given the state of the various user groups and the concept of least
permission across a network.
We use groups and give read/write access to groups. When groups access
procedures, occasionally there are problems, particularly if the newly
created procedure is used by a group user and the procedure has not been
added to the role that allows access to the procedure.
Is there a command that will easily place all new procedures into the user
procedure role that doesn't involve putting every procedure into the role
(there are some we don't want the users to run)?
Regards,
Jamie
Actually, posting in the wrong group here. This is a question for VS 2005
Net Framework deployment.
Regards,
Jamie
"thejamie" wrote:

> I have a user (also my boss) who wants the system to work a specific way
> which amounts to this:
> 1) ability to create an application as a developer
> 2) ability to deploy that application anywhere on any server in the network
> 3) ability to not need to worry about user permissions
> I don't know how to explain how Windows Authentication works well enough -
> in other words, in a syllable or so, that explains why this may not be
> possible given the state of the various user groups and the concept of least
> permission across a network.
> We use groups and give read/write access to groups. When groups access
> procedures, occasionally there are problems, particularly if the newly
> created procedure is used by a group user and the procedure has not been
> added to the role that allows access to the procedure.
> Is there a command that will easily place all new procedures into the user
> procedure role that doesn't involve putting every procedure into the role
> (there are some we don't want the users to run)?
> --
> Regards,
> Jamie