I recently realized that it wasn't necessary to add individual users to the repository 'Windows Accounts' node in order for them to login, as long as they belonged to a trusted AD group. However, at some point after a user logs in their individual user account also shows up in the 'Windows Account' node. Is that just what naturally happens? Is there a way to configure this not to happen? I'm just curious - it's not a huge problem for me.
Question
Question
Answer
This also happens because once they log in the Client applications need to user account to be explicitly defined in order to store personal settings.
This is not correct, as the Laserfiche server is capable of storing user attributes without assigning any other information about the user. Furthermore, it can successfully answer queries for user attributes for users with no attributes or other information assigned (it will return an empty list of attributes, of course).
However, if the user didn't appear in the list, then there wouldn't be a way in the current administration UI to access those attributes.
The benefit I was hoping for was that by not adding each user I could import the column settings for the group and not have to do it for each user. But I'm gather it doesn't work that way because each user gets created eventually, with default settings?
Well, that wouldn't actually be possible regardless of if they get created or not. Client-side settings such as columns can be set on individual users or on the Everyone account, but not on individual groups. You can set them, but the Client applications don't make use of them.