User and Employee Groups
First, our groups are are customizable, editable, and can be used to contain any category of data. In other words, they belong to you and can be customized to suit the needs of your organization. Part of that customization includes naming your groups, in that you can select just about any name you wish.
Many times, organizations find that it's helpful to have a People category within a group. Let's put it this way...in Asset Panda, groups do not have access to your data- they are the data! So, a group that is titled, Employees, Personnel, or Address Book won’t have the ability to log in.
Unlike a user profile, the fields in a group can be edited. This means that if you decide to have a group that houses personnel information, you can add as many fields as you need.
If having a group named Employees is causing confusion, it can be renamed Directory or Company Address Book, depending on the needs of your company.
Basically, groups can be named whatever you wish or need them to be. Typically, the category of data in a group is People.
Difference between a User and an Employee Group
Users are people who can log in to your account. Employees (or any other group) do not have access to log in. Groups like Employees are just a list of information that happens to be a directory of people.
Users
Users have access to log into your account. They need to be entered by an administrator and can be given varying levels of permissions so that they access only the appropriate content.
Users are not a group, but rather a feature that is hard-coded into your account. This means that unlike groups, the fields for users cannot be added, removed or edited.
Users can be managed in the Configuration menu, under User Configuration. Only company administrators will have access to manage the people who can log in and see your data.
Groups
Why would anyone need a group for their employee data?
Not everyone needs employees in a separate group. Some clients offer log-in information to each employee, so they are able to use their User list rather than using one of their groups to house this information.
Some clients offer user log-in to every employee, but they still need to house additional information about their employees that can’t be added to the user settings. Fields like certification dates, associations with projects or departments, and additional contact information can only be added to information in a group.
Some clients have a workflow where both users and personnel lists need to exist. For example, they may have a few users who can actually log-in but will need to choose from a list of their entire employee base in order to complete transactions within the account. Actions like checking out a laptop to someone that does not have the access to do this themselves is a great example.