The Account Editor section of the Administration Client supports viewing and modifying the details of the users, groups, domains, and other authentication settings for the current instance.

• Internal Roles - The internal groups managed by DataSplice are called Roles, and are used to define sets of functionality that can be made available to users.
• Internal Users - DataSplice can be used to manage accounts that can log into the system using the DataSplice domain.
  
• External Domains - Any external authentication domains that have been mapped will also show up in the list. This will display a read only list of the users and groups available in that domain.

Role Based Permissions

In general, one role should be created for each distinct set of functionality that needs to be available to DataSplice users. This allows you to add users and groups from external domains to these roles. Those accounts will then have access to the views and settings they need. If needed, roles can be hierarchical (members of other roles) so base settings can be defined at one level and more specific options in the child roles.

Note that permissions and settings can only be defined for roles, not for users or groups. This keeps configuration settings separate from authentication and is easier for administrators to maintain. Also keep in mind that role settings are additive - if a user is a member of multiple roles they will have access the settings and permissions from each role. Adding users to multiple roles that have conflicting settings will have unpredictable results, and should be avoided.

Selecting a role in the Account Editor displays various options that can be edited. The following sections are available:

Edit Role Settings

The main role settings screen supports adding users and external groups to the role, as well as defining attribute settings that will be available to all members.

Edit Role Events

Certain events (such as keypresses, offline synchronization, and custom plug-in events) maybe available regardless of the view selected by the user. Event handling is discussed in more detail in the view configuration section.

Edit Role Styles

This allows commonly-used styles to be defined at the role level, and re-used in multiple views. Defining field styles is discussed in more detail in the view configuration section.

Edit View Permissions

All views needed to support the role's functionality should be checked in this section. A user will have access to the combination of views available to each member role.

Built-in Roles

Two roles are available by default:

Default

All users are automatically members of this role, so it can be used to define system-wide settings and permissions.

Administrators

Any user that is a member of this role is permitted to connect with the Administration Client.

Plug-in Roles

Many plug-ins will ship with roles that define particular sets or functionality. For instance, the Maximo Integration Plug-in defines the following roles:

• MAXIMO - Provides common attributes used throughout the Maximo configuration

• MAXIMO Inventory - Provides access to views that support basic inventory functionality, such as Physical Counts, Issues and Returns, and Purchase Order Receiving.
  
• MAXIMO Work Order - Provides access to views that support work order functionality, such as Work Order Tracking, Labor Reporting, Failure Reporting, and others.

Custom Roles