Topic: Granular Permissions (or) Account Auditing

I'd like one or both features as they are necessary for ensuring the integrity of an asset/inventory database.

  • The ability to scope permissions around functions in tracmor (ie: user can check-in/out an object, but NOT edit it).

  • The ability to audit user accounts is key to database integrity. (ie: additions/detentions/modifications).

Thanks - Jared

Last edited by jared (2010-12-28 09:19:02)

Re: Granular Permissions (or) Account Auditing

You can reference the current users Role (a.k.a "user group") like so:

$intRoleId = QApplication::$objUserAccount->RoleId; // This references the Role Id
$objRole = QApplication::$objUserAccount->Role; // This references the Role object itself

As for the feature requests, it definitely makes sense that you should be able to allow transactions while disallowing edits. We will look into this.

Could you elaborate on the user audit feature? How would you envision this working?

Justin Sinclair

Got Inventory? Get Tracmor.

Re: Granular Permissions (or) Account Auditing

Thanks for the feedback that's helpful.

In terms of account auditing it would be nice to know the following:

  • When a user logs-in/out, time stamp, and ip.

  • When a user adds, modifies, removes an item (asset, inventory, contact, etc).

  • When a user performs any transaction.

This information would be provided in a logfile type view, and  could possibly sorted/filtered based on criteria. Ideally for data integrity you want to know who made a modification, to what, and when. The other features are niceties.

Another thing to consider is that a more granular approach to permissions reduces the need for overally detailed logging. If you can prevent the majority of users from performing certain functions, you reduce overall risk, and in turn reduce your need to track finite details.

Last edited by jared (2010-12-28 10:21:28)