Tracking schedule changes

• Forever chasing for unauthorized changes is nuts!
• That anyone can mess your schedule is scary.
• The problem is with giving to everyone editing rights to all projects.
• Better issue a good access control system, free-for-all is not a good idea.
• It is a no-brainer, if every user is to have his own particular access rights, then an individual access profile shall be issued for each user.

to see who logged in when you can go into the database and run a query depending on what databse that you are running

  Oracle:

SQL Server:                                

Select login_date,user_name from usessaud as U where login_date =(Select MAX(login_date) from usessaud where user_name= U.user_name);

you can also see what chnages were made buy running a query using an audit trail

To access the database auditing application settings:

1. Login to P6
2. Browse to Administer, Application Settings
3. Select the Auditing tab

you set the level of the audit from leve 0 to level 3

the level is set in the query liste dbelow

• auditing_enable(<table_name>,<level>)
• auditing_disable(<table_name>)

Maybe you are looking at the wrong table. If you do not have such table then I do not expect you to be able to reconstruct it after the facts. 

In Spider Project we have an audit table called Logbook.  You can set up the maximum number of entries to be up to 10,000; it should be good enough to make any corrections in time.  If after 10,000 entries you might still need to look at previos entries then you sholud periodically backup the table as a separate document for future view, say backup the table once a week.  Auditing schedule entries for corrections after a week can be too late.

- One of the users claims that "someone" has been in and changed one of his schedules.

I would recommend allowing full access to a single person per job in addition to the system administrator and grant others acess rights to only view some WBS sections with access to view a limited number of cost codes.

Chasing for unauthorized changes is nuts!

Phil,

I don't think that level of auditting is easily available from the P6 front end. Perhaps someone who can access the datatables may be able to.

There is something you can do, in the activity columns, you can include these two columns to be displayed:

•  Last Modified By - this will give you the users name, note that this may not be 100% accurate if say, the entire project has been copied
• Last Modified Date, this will also tell you when it was last modified, but same caveat as above.

Having multuple users in a the same project is a tricky balance, especially if they end up working in the same sections of the project.

Remember that when a user makes a change, it may not be committed to the database until they take an action to commit the change, such as pressing F9. Pressing F10 forces data to be committed to the database. And then sometimes you will need to press F5 to refresh from the database. 

There could be a scenario that the changes one user makes are overridden by another users actions because the other users data was committed to the database, and the first user has not refreshed those changes yet.