<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[FrontAccounting forum — Audit Trail Module]]></title>
		<link>https://frontaccounting.com/punbb/viewtopic.php?id=14</link>
		<atom:link href="https://frontaccounting.com/punbb/extern.php?action=feed&amp;tid=14&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Audit Trail Module.]]></description>
		<lastBuildDate>Mon, 28 Apr 2008 10:20:09 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Audit Trail Module]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=608#p608</link>
			<description><![CDATA[<p>Hello there,</p><p>Sorry for the very late response.&nbsp; Lost my account details and hence became inactive.</p><p>Actually what I have in mind is much more comprehensive based on my experience with Quickbooks online edition which I have been using for nearly two years now. Based on that even the minutest change like adding a comma or a period will be recorded and the change highlighted in red text to make it easier to spot.&nbsp; All records for an individual user are laid out in a tree form to start with. Admin User can then select whichever raises concern.</p><p>Another area which could be improved is access control list.&nbsp; Applications like sql-ledger do present a table for all the modules showing the various rights to assgn to user.&nbsp; This provides a more granular security control.&nbsp; I would go a step further to include ability to create a security template to be applied to staffs.</p><p>Lastly, again an idea borrowed from Nola Pro: IP security.&nbsp; This allows the admin to specify specific IP addresses from which users can access the application or from which they are prohibited from accessing the application.&nbsp; I do appreciate it may pose a challenge for companies not using static IP but hei! you are the IT guys, you are solution finders!</p><p>You can call me paranoid about security but dont call me ordinary <img src="https://frontaccounting.com/punbb/img/smilies/big_smile.png" width="15" height="15" alt="big_smile" /> lol</p>]]></description>
			<author><![CDATA[null@example.com (lurdsammie)]]></author>
			<pubDate>Mon, 28 Apr 2008 10:20:09 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=608#p608</guid>
		</item>
		<item>
			<title><![CDATA[Re: Audit Trail Module]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=24#p24</link>
			<description><![CDATA[<p>Hi Sammie,<br />We understand what you mean and one way to do this is to stamp the memo_ field with the user_id when creating General Ledger transactions. It might be sufficient enough. All transactions from the sub-systems will create General Ledger transactions, at least the critical ones.<br />A slightly similar method is to add a new field in the GL_trans table called user_id.<br />What do you think? Will eather approach be ok?</p><p>Admin</p>]]></description>
			<author><![CDATA[null@example.com (admin)]]></author>
			<pubDate>Sun, 22 Apr 2007 21:29:39 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=24#p24</guid>
		</item>
		<item>
			<title><![CDATA[Audit Trail Module]]></title>
			<link>https://frontaccounting.com/punbb/viewtopic.php?pid=23#p23</link>
			<description><![CDATA[<p>hello guys,</p><p>You have already done a great job. However there is one feature, Full Audit Trail, that seems to be missing from frontaccounting. I think it will be most helpful if you could consider it for future realease since being a web based software unscrupulus staff can mess about with things especially when not on duty and there will be no way of telling who made what changes.</p><p>Thanks</p><p>Sammie</p>]]></description>
			<author><![CDATA[null@example.com (lurdsammie)]]></author>
			<pubDate>Sun, 22 Apr 2007 17:01:48 +0000</pubDate>
			<guid>https://frontaccounting.com/punbb/viewtopic.php?pid=23#p23</guid>
		</item>
	</channel>
</rss>
