Hello,

Can anyone give me a brief overview of the relationship between trustees and their information in the various applications? We're relatively new to Laserfiche, and while we've been able to setup a basic user management process in this somewhat complicated application, I'm sure there are many nuances or tricks that could help us streamline the process.

In our client's application, most of the users of the system will be from the public, assigned Community Named User Licenses upon submission of their project for review by our client. As such we will be creating them as users and assigning their licenses in LFDS, i.e. they will not be coming from our AD.

To start, some clarification on how or if the trustee information is shared between the Laserfiche applications would be a big help. For example, when I create a user in LFDS, I can create a profile with their display name, first/last name, email, department, etc. It looks like this profile can be used by Forms, but what about the repository? 

We will most likely need to lookup users in Workflow by email, so at the very least, this will be an attribute that we need in the repository user account. If there is a way to link the repository account with the LFDS account, that would be ideal, as we would be entering the email account anyway, but from what I'm gathering, this is not so straightforward, even after adding the account under the Laserfiche Directory Accounts node. 

What is our best bet for an efficient process of user profile creation and management between LFDS and the repository? And in general, we would appreciate advice on how to to approach user management, password recovery, self profile management, etc., with potentially hundreds of users, many of whom will stay in the system for repeat projects, many others whose accounts will be recycled after a period of disuse?

Any thoughts, advice, etc. will be greatly appreciated.

Jesse