A user is an individual to whom you provide resources. You provide access to users for specific iWorkflow™ system functionality through authentication. You can associate a user with a specific role, or associate a user with a user group, and then associate the group with a role.
A role is defined by its specific privileges. A user group is a group of individuals that have access to the same resources. When you associate a role with a user or user group, that user or user group is granted all of the role's corresponding privileges.
The iWorkflow™ system creates two default users as part of the initial setup and licensing process. These user accounts cannot be revised (except for their passwords) or duplicated. After setup is complete, you can create additional user types and roles to meet your business needs.
|Default user type||Default password||Access rights|
|admin||admin||This user type can access all aspects of the iWorkflow system from the system's user interface.|
|root||default||This user has access to all aspects of the iWorkflow system from the system's console command line.|
User types persist and are available after an iWorkflow system failover. You can authenticate users locally on the iWorkflow system or remotely through LDAP or RADIUS.
As a system manager, you need a way to differentiate between users and to limit user privileges based on their responsibilities. The iWorkflow™ system has a default set of roles you can assign to a user. Roles persist and are available after an iWorkflow system failover.
iWorkflow™ ships with several standard roles, which you can assign to individual users.
|Administrator||Responsible for overall administration of all licensed aspects of the iWorkflow
system. These responsibilities include:
|Tenant||A tenant is an entity that can consist of one or more users accessing resources
provided by an administrator. : These responsibilities include:
Note: The iWorkflow system creates a new role when an administrator creates a new tenant. When you create a tenant, you specify the connectors that tenant can access. The name of the new role is based on the tenant name. For example, creating a new tenant named headquarters-user, produces a new role named headquarters-user (Cloud Tenant).