Security Groups

The Security Groups screen allows you to view and manage Security Groups. See Adding Security Groups.

NOTE: Only a user with administration permissions can access this page.

How to get there

In the Navigation Bar, click User Securityunder settings, then click Security Groups.

Options

Click to add a security group.
Click Show Actions next to any user and click Edit User to edit an existing Security Group.
Check box next to user and click Delete to delete a Security Group.

Ways to Use Security Groups

There are a couple of ways you can use security groups.

As a way to organize your users

Security groups can be used as organizational tools. You can add users and roles, and any changes made to the groups or roles attached to them will trickle down to the users. This ensures that the work you do with individual users (after they are created or pre-registered, see Adding a User) is minimal.

EXAMPLE: You create an ACCOUNTING security group and add fifteen users to it (if you have LDAP authentication set up, users in the Accounting department could even be automatically assigned to this group when they first log on to HelpSystems One). Then, you add an Accounting Users role to the security group so that every user in ACCOUNTING is given basic HelpSystems One permissions.

As a way to give a user extra permissions

You can also use security groups to give a user permissions to an area of HelpSystems One they generally do not have access to. This may be pertinent if you have a Powertech engineer who needs temporary access to an Automate Enterprise server or a Dashboards supervisor who needs to look at a Robot test system.

Users can easily be added to or removed from security groups, which makes it simple to give a user permissions that are outside their normal role functions.

EXAMPLE: A Powertech Network Security engineer needs to collaborate with an Automate Ops Console engineer on a three week project. However, he is currently only added to the PTNS ENGINEERS security group and cannot access Automate Ops Console in the HelpSystems One Navigation Panel. To allow him temporary access to the Automate Enterprise production system, you either a) add him to the AUTOMATE OPS CONSOLE security group or b) create an AUTOMATE PROJECT security group that has the permissions he needs and add an Automate Ops Console Users role to it. When the project completes, you simply remove him from the security group (or delete it all together).

The Default Security Group

HelpSystems One comes with a default security group that users are assigned to if they are not automatically assigned to a group or role. The Default security group cannot be deleted and has no basic authorities out of the box. If you want to add authorities to the default security group, you can do so by adding roles.

The Default security group should only be used to catch users who are not given a group or role when they first log on to HelpSystems One. We do not recommend using it to give users authorities long term. Please note, too, that if you assign another security group or role to the user, the default security group will be automatically removed next time they log on.

The All Users Security Group

HelpSystems One comes with an All Users security group that all users are assigned to automatically. The All Users security group cannot be deleted and has no basic authorities out of the box. If you want to add authorities to the All Users security group, you can do so by adding roles.

The All Users security group can be used to set permissions and share objects throughout HelpSystems One and HelpSystems One modules. For example, it can be used to share Dashboards and Dashboards Queries among all users.