Roles can be defined to specify user permissions and access rights

In Iguana 4.5, you can create roles that specify the Iguana server access rights that are to be provided to members of the role.

	In previous versions of Iguana, user groups were defined instead of roles. Roles provide considerably more flexibility.

By default, the following roles exist:

• Administrators, who have full access to the Iguana server. (The default user, admin, is a member of the Administrators role.)
• Users, who initially have view permissions on all channels. This role can be removed if it is not needed.

You can define additional roles that enable you to:

• Specify which channel groups can be accessed by members of the role;
• For each channel group that can be accessed, specify whether users can edit, start and stop, or export log information from channels belonging to that channel group, or whether permissions are to be restricted to view-only.

Roles enable you to ensure that a particular user can see only the channels that he or she is supposed to see, which can help you to achieve patient confidentiality or ensure that sensitive information, such as financial data, cannot be viewed by unauthorized users.

For more information on how roles are created and used in Iguana 4.5, see Roles & Users. For an example of how you can use channel groups and roles to limit channel access in Iguana, see the Restricting Channel Access tutorial.

Users can now be disabled

In Iguana 4.5, you can now disable a user. When a user is disabled, the user remains defined in the Iguana server, but the user cannot log into Iguana using this user.

Users that have been disabled do not receive email messages or SMS messages sent by email notification rules. This is useful if a user has gone on vacation and does not want to receive messages while away.

Users that have been disabled can be re-enabled.

For more information on disabling a user, see Disabling or Enabling a User.