restricting write permissions

[brad1]

Hi,

I have been having a look at this CRM, but I have a slight issue I cannot yet resolve.

Due to the need for 'accountability' I do not want a user to be able to edit or delete "existing'" notes or comments.

I know I can restrict permissions for a user, but this does not seem to address the issue.

for example

A user enters a note, or creates a case etc.

they can continue adding comments to this. However, they can go back and delete, or edit these comments.

Our requirement is that if a comment is made against an account, no one (bar admin or some fancy back end editing) can delete or remove this comment/note. If an amendment is needed a new note needs to be made.

If I restrict the user by removing write access, then they cannot create a case to start with.

Is there a way to accomplish the above? ie: write permissions to create a case/note, but the inability to remove or edit this once it has been committed to the database.

Cheers

Brad

[Angel]

Two options come to mind:

1. The workflow automation engine in the Pro and Enterprise versions would allow you to modify the "Assigned To" value of the entry automatically after it is saved/entered into the database. Using this tool, you would then be able to automatically assign the entries to an admin user or the like. If you combine this with the roles functionality, you could then restrict who can edit the entries afterwards.

The only problem with this is that Notes do not have an "Assigned To" value, thus, you would be able to apply this solution to Cases and other areas, but not Notes.

2. The second option would be to use some custom code in conjunction with the logic hooks in Sugar and mimic the same behavior of the workflow automation engine.

Again, you wouldn't be able to apply it to Notes, but it would work in other areas.