Good morning,

I am trying to remove a user from our enterprise, and received the following message:

"User cannot be removed from the Enterprise as they are part of an Approval Policy. Have the Member approve any items pending approval and remove them from any Published Approval Policy."

We have a very basic approval policy in place. We just started using timesheets in December, but have been using daptiv for our projects since August.  We do have some timesheets that are pending during the time we were not using timesheets.  What should I do with the outstanding timesheets, and how do I find out what approval policy the user I am trying to remove is a part of?

Thanks.

I've run into this a few times as well, and unfortunately it can be a little tricky to track down.  Check the user's project memberships and make sure there are no documents or dynamic application records for which the user is designated an approver.  Also check the Project Requests if you are using that feature.

If you can't locate the offending approval policy, please contact our customer support team for further assistance.

Does this mean you have to go through each and every document for the projects that the user is a member of?

Not necessarily.  If you log in as the user (an administrator can reset their password) and look at the Approvals tab, you will see all items pending their approval.  The only time this won't work is if they are an approver for an item that has routing enabled and the item hasn't yet reached them in the sequence of approvers.  However, if the user has been inactive for some time, hopefully everything has gotten to their approval plate by now.

Thanks, Erik.

A couple of product enhancement thoughts....

1. Allow the Administrator to see all pending approvals for existing users.  This would make it a lot easier (at least in an environment that uses single-sign-on) for the Administrator to address this issue.
2. When using the routing feature for approvals, either do not send the approval request to a user until it is his/her turn to approve, or build an error handling routine that clearly identifies the fact that the approval cannot be done out of sequence.  (Currently, if someone attempts to approve an item out of sequence, the generic "pardon our dust" page is displayed.  This page does not give clear indication of why the error is occuring.)

- Brian

Your first point is a good enhancement suggestion, and falls under a general enhancement area of greater visilibility and control of enterprise data for Administrators.

You second point actually sounds like a bug.  Certainly the "pardon our dust" exception is a defect, and the approval routing scenario you describe here sounds like something isn't working right.  If you haven't please contact our support team and open a case so we can diagnose, manage, and fix (if needed) the problem.