Advanced User Privileges and Responsibilities

Modified on Sat, 04 Apr 2020 at 05:34 PM

Risk Assumed with Object Deletion Rights

Administrator-level access rights can be useful: They allow deletion of clutter data, modification of otherwise locked fields and access to scripts that make it easy to correct databases, like when Financial Distributions need to be recalculated.

However, advanced access rights, of course, come with responsibility. Admins have the ability to permanently delete some objects which cannot be recovered. Additionally, Admins can view and modify sensitive financial records.

Admin access is granted contingent upon an implicit release of FieldCLIX from liability in the unlikely event of data damage. Consult your executive management team and FieldCLIX Implementation Manager if you have additional questions on this subject.

Advanced Access Considerations

  • Admins can permanently delete some objects other users cannot: Most users can only delete links and not Objects themselves.
  • Users with advanced access should be extra careful with documents since, unlike Reference Records they do not have the web of connections which prevent accidental deletion.
  • When in doubt, it is better to just “close” an object, rather than delete it. Closed objects do not affect any system process (with few exceptions) so this is a safe option.
  • Authorized Users can move any Object to the “Closed” Lifecycle Stage by using the drop-down menu titled “Stage” or “State.”
  • With advanced access rights, a User will see buttons and options available in objects which are not visible to regular users. Keep this in mind when troubleshooting or answering User questions.
  • Authorized Users can override Lifecycle Stages in cards. For instance, with this access one could move a VPO from Approved back to Draft stage.
  • The ability to override Lifecycle Stages should be used with care as it can affect Financial Distributions!
  • In some cases, changing the Stage of an Object will not have all the effects one might expect. For instance, Moving a VPO to “Pending” does not automatically trigger the Approval process Task/Jobs.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article