I'm developing a kind of standard web-application, to be hosted internally on few customer's servers (not a public service, startup or anything like that). A kind of CMS, e-learning platform or something close to that. Because this is an internal project, customer had given me quite a large decision field and did not specified problem in question.

My developed web-application is planned to have few admins and only one superuser per each installation. In this case, should application logs be available to admin-level users or strictly prohibited to be viewed by superuser only?

  • You might be mixing application logs and audit logs. Just a thought. AppLogs should be admins, audit is probably super user.
    – jrg
    Commented Jul 12, 2014 at 20:39

2 Answers 2


It will all depend on the classification of the data and the classification of the users. You can create different levels of logs for different classifications of users, if that's needed.

It's a balance of usability (what logs do they need in order to do their jobs) and security (what logs do they need to NOT see because it is above their classification).

Install logs tend to be of a general classification, but logs containing user data tend to be of a restricted classification depending on the data.

You need to map what the 'admin' and 'superuser' need for their functions, and map out what is in the logs that needs to be protected.


I see that it can be very useful for the administrator in case if the instalation could not be completed correctly (Just an exampl) so the logs will help to diagnose the problem, so you can have several types of log file depending on the design of your application and an allocation options clearances as every needs .

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .