<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p> </p>
<div>
<p><span>We used to have exactly all the problems you described. We looked for various solutions and some of them failed or were insufficient in some specific cases. In our system these mechanisms work in a different way, but they have some common elements.</span></p>
<ol>
<li>
<p><span><span><span>We have a new sharing field which allows for assigning records to several people and/or groups.</span></span></span></p>
</li>
<li>
<p><span><span><span><span>We added a few new mechanisms in roles [you can check them out in here: </span><a href="https://gitdeveloper.yetiforce.com/index.php?module=Roles&parent=Settings&view=Edit&record=H2]," target="_blank" rel="noreferrer"><span><span>https://gitdeveloper.yetiforce.com/index.php?module=Roles&parent=Settings&view=Edit&record=H2],</span></span></a><span> the most essential features are:</span></span></span></span></p>
</li>
</ol>
<ul>
<li>
<p><span><span><span>Should the list of records (that we do not own) related to our records be shared:<br />Inactive</span></span></span></p>
</li>
<li>
<p><span><span><span>Should the preview of records (that we do not own) related to our records be shared:<br />Inactive</span></span></span></p>
</li>
<li>
<p><span><span><span>Should the edition of of records (that we do not own) related to our records be enabled:</span></span></span></p>
</li>
</ul>
<p lang="pl-PL"><span><span>These options work based on relations by arranging the relations with respect to the main modules, namely Accounts and Leads. In short – When you are in a specific record, the system checks what you should be able to see. When you are in the client, it enlists all the projects [even though you are not their owner, but you are the client's owner; when you go to the project the system will enlist the project's tasks, when you go to the task you will see the comments], which means that the permissions are given additionally on the basis of the users chosen in Account.</span></span></p>
<span style="font-size: 10pt;">When it comes to reassigning records to a new employee you have to remember that the reassigning should only concern the open records [which means matters that weren't created by this user] because the entire history should remain intact, and it should be visible in the history that some time ago another user changed, modified, or added something in the system.</span><br /><span style="font-size: 10pt;"></span></div>
<div> </div>
<div><span style="font-size: 10pt;">Have you tried this trick – if employee A was supposed to take over employee B's records, you move him in roles under that employee [then, according to the permissions, he should be able to see all the records of that employee]</span></div>
<div>--<br />
<div>Z poważaniem / Regards</div>
<div> </div>
<div><strong>Błażej Pabiszczak</strong></div>
<div><em>Chief Executive Officer</em></div>
<div>M: +48.884999123<br />E: <a title="Mail do Błażej Pabiszczak" href="mailto:b.pabiszczak@yetiforce.com">b.pabiszczak@yetiforce.com</a></div>
<hr />
<p> </p>
</div>
<p>W dniu 2015-09-16 13:24, Stacey Johnson napisał(a):</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div dir="ltr">
<div>Deleting user can not allow for deleting evidence. This is still bug.<br /><br /></div>
Stacey</div>
<div class="gmail_extra"><br />
<div class="gmail_quote">On Wed, Sep 16, 2015 at 6:15 PM, Sreenivas Kanumuru <span><<a href="mailto:svk@vtiger.com">svk@vtiger.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
<div dir="ltr">Alan, This is already addressed in 6.3. Deleted User will be marked as inactive, if the 'Delete User Permanently' option is not selected. All the updates and comments will remain associated with the deleted user.
<div><br />
<div> </div>
<div><img src="cid:144240683855f961b60cf4f950294449@yetiforce.com" alt="" width="472" height="228" /><br /><br /></div>
</div>
<div class="gmail_extra"><br clear="all" />
<div>
<div>
<div dir="ltr">
<div>
<div> </div>
<div>thank you,</div>
<div>Sreenivas</div>
</div>
</div>
</div>
</div>
<div>
<div class="h5"><br />
<div class="gmail_quote">On Wed, Sep 16, 2015 at 2:30 PM, Alan Lord <span><<a href="mailto:alanslists@gmail.com">alanslists@gmail.com</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">I think this is a fairly big bug but it needs some discussion...<br /><br /> Our customer has just asked about their process when they have churn with employees in their business (churn in this case means multiple people leaving and joining their business, e.g. staff turnover).<br /><br />
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">We've had a bit of staff churn recently and I've struggled to keep up with the data re-assigning. We used to delete a user when they left and re-assign everything to admin. This was really straightforward as the system did all the hard work for you in the background. However, we soon realised that this messed with the audit trail in the "View history" and it changed the owner of the comment to admin so you couldn't tell who had made the notes. We changed our process to making the user inactive and then manually re-assigning the records. This take a while and there is a lot of room for human error. Is there a quicker way of doing this that I'm missing or something at point of deleting a user that maintains the audit trail?</blockquote>
<br /> It seems to me that when you delete a user from vtiger somehow the data in ModTracker needs to retain the fact that that earlier changes were made by that user (a new field to hold the User's name rather than their ID?), and *not* the user you have just re-assigned everything too. The same goes for comments too.<br /><br /> Secondly, he makes a valid point about making a user Inactive instead... There should probably be an option to re-assign related records when making a user Inactive...<br /><br /> This customer is using 5.4.0 but I suspect the same issues apply with 6.3.0.<br /><br /> Discuss.<br /><br /> Al<br /><br /> _______________________________________________<br /><a href="http://www.vtiger.com/">http://www.vtiger.com/</a></blockquote>
</div>
</div>
</div>
</div>
</div>
<br />_______________________________________________<br /><a href="http://www.vtiger.com/">http://www.vtiger.com/</a></blockquote>
</div>
</div>
<br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br /><a href="http://www.vtiger.com/">http://www.vtiger.com/</a></div>
</blockquote>
</body></html>