Are they asking about Unified Logon?
If so, should work just bye enabling that in System Configuration and making sure that the user's login to Sage matches their login to their network.
Important Aside: If the customer uses Beanworks / Sage AP Automation - then you won't be able to use unified login for Sage since Beanworks doesn't support unified login. This can create a set of issues if the customer's IT is very formalized with password rules ( which Sage basically has very few regarding the strength of the password when not using unified ).
Here are more gritty details from one of my customers who is presently researching the impact of turning OFF their unified login for Sage:
Sage100 security ( aka with Unified Login DISABLED ) will not be able to;
1) Meet the minimum password age
2) Change password on initial login
3) Keep password history
4) Meet complexity
When I turned off Unified security, every user will need to have a temp password set and provided to them. When the user logs on with that temp password they will not be prompted to change their password. Even with the "Force Password Change After a Set Number of Days" option set to 1 day. What I also determined is that the 1 day setting is not really 1 day. The 1 day settings actually rolls forward at 12 PM midnight, not after 24 hours. For example, I created a temporary password for myself at 11:45 PM, with the Change password option set to 1 day. I logged on at 11:50 PM, and was not prompted to change my password. I logged on at 12:05 AM and was prompted to change my password.
This means that until each user logs in, after having their temp password given to them, and has the chance to change their passwords, which will not happen until after midnight, I will know what those passwords are. This becomes an issue once we turn off Unified Security and assign temp passwords, when any new users are added to Sage 100, and when users forget their unique passwords. This will be the case in Sage 100 DEV and Sage 100 PROD. The passwords do not sync between the environments.
Second the issue of setting up the SageAPA user for Beanworks. The SageAPA user will be bound by the same password parameters as all other users. I unaware of any way to have unique separate password parameters for a specific user. That means the SageAPA password will need to be changed every 90 days like all other users.
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------