Security for Inbox Layout Changes

[Landry, Marcel]

Thanks Dave !  Good suggestion.
 
I did find the authorization object for changes to the layouts using TX
STO1. The Auth object is S_ALV_LAYO.
There is only one activity on this object, it is Activity 23 - Maintain.
 
I since found out that all users on our development system had this
authorizatin object, and could therefore overwrite globally defined layouts.
 
By removing this Authorization object, the users can still change layouts,
but can only save them as 'user-specific' layouts, thus preserving the
production layouts.
 
Thanks for the suggestion.
 
 
Marcel
NB Power.
 
 
 
-----Original Message-----
From: David Weston [mailto:weston at clockwork.ca]
Sent: September 25, 2001 11:39 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Security for Inbox Layout Changes
 
 
Hi Marcel,
 
Have you tried running the authorization trace from ST01 to see if any auth
objects
are actually called ?
 
Cheers
Dave
 
----- Original Message -----
From: "Landry, Marcel" <MLandry at nbpower.com>
To: <SAP-WUG at MITVMA.MIT.EDU>
Sent: Tuesday, September 25, 2001 10:10 PM
Subject: Security for Inbox Layout Changes
 
 
> Hello folks, we are in the process of upgrading to 4.6C and I have the
> following question regarding user changes to the WF inbox layouts in the
> workplace.
>
>
> Currently, when a user is in the WF inbox,  it is possible to change a
> layout and save this layout as the default for all users...  or worst yet,
> modify a production layout and save changes over the original copy.   We
are
> attempting to lock-down the ability to save layouts as "default" global
> layouts and to save over an existing layout.
>
> Does someone know of any security authorization objects that may be of
some
> use to our security department to better control these functions ?
>
>
> Thanks in advance.
>
>
> Marcel Landry
> NB Power.
>