Hi Justin,

Right now it inherits the permissions from service center that's right. There are actions like dropping tables or entities attributes which requires the user to have full admin permissions over the environment.

But for logs, there's no control. One developer should be responsible for its actions.

Of course this can be changed, if we find that's a concern of multiple people.

Thanks,
Miguel

Thanks Miguel,  yea the fact that we have no control over security makes us hesitant to install this in our Production environment.  We want the functionality the tool offers but don't want to risk a developer to go in and delete things.  Would you be able to tell us which tables the DB Cleaner purges if we wanted to write a script to run manually in Production for the Email cleanup?

Hi  Miguel,

Same as Justin I am looking as well to use this but to restrict it for Admin only for all actions.

Is there an option available in any version ?

Thanks,

Anil.

Hi all, I have the same need to be able to limit access to the application. Is there any development planned in this sense? Thanks

Agreed the ScreenView should have a specific DBCleaner Role then we can assign the role to specific users.