User Roles

Navigation:  IDIOM Basics > Starting IDIOM >

User Roles

Previous pageReturn to chapter overviewNext page

When a System Administrator creates a new repository, they can create one or more workgroups and assign users to each of these workgroups.

A System Administrator can access all of the workgroups, and can also assign the role of System Administrator, or Repository Administrator to another user.

They can also create Workgroup Administrators, Formula Experts and Testers, and then assign them to Workgroups. This will provide Users with varying levels of functionality and/or access to specific decision models within the repository. Provided they have been granted access, Users can now simultaneously log into the same repository/workgroup regardless of User Role.

Note: 'decision designer' is a generic term for people who design and build decision models. While a decision designer may be an administrator or subject matter expert, ‘Formula Expert’ is the IDIOM Decision Manager role most closely associated with building decision models. While these terms can sometimes be used interchangeably, Formula Expert will be used in those parts of this Manual that specifically describe features of the Formula Expert role as implemented in the IDIOM Decision Manager; and the term decision designer will be used to refer generically to people in the wider group who may be involved in decision model construction, including Formula Experts.

 

Table 2-1 outlines the functions and permissions of System and Workgroup Administrators as well as the Formula Experts:

User Role

Functions and Permissions

System Administrator

•The System Administrator has system-wide access and permissions. They can create:

▪Repositories.

▪Source schemas.

▪Workgroups.

▪Users (including other Administrators).

•Perform and administer Local and Production Releases

•The System Administrator can also log in to a repository as any other User Role, but will not retain their System Administrator privileges.

Repository Administrators

•Repository Administrators are able to do most things that a System Administrator is able to do at a repository level, except for deleting the repository.

•They have no jurisdiction on adding or maintaining Users or Workgroups.

•The Repository Administrator can also log in as a Workgroup Administrator, Formula Expert or Tester but will not retain their Repository Administrator privileges.

Workgroup Administrator

•Creates Decision Models

•Creates and assigns users to workgroups.

•Imports new source schemas.

•Customizes existing schemas.

•Adds customized schemas to a repository.

•Creates Table Definitions.

•Creates Default Table contents.

•Releases decision models they are authorised to, or that are marked as `global'. (See Creating a New Decision Model)

•The Workgroup Administrator can also log in as a Formula Expert or Tester but will not retain their Workgroup Administrator privileges.

Formula Expert

•Modifies and tests decision models authorised to their workgroup or to `global'.

▪Creates decisions/groups

▪Creates formulas.

▪Creates formula references.

▪Edits Associated Table Data (if not marked private)

•Can change their own user name and password.

•The Formula Expert can log in as a tester but will not retain their Formula Expert privileges.

Tester

•Testers are primarily able to use the inline-debugger and test executive.

•Testers should still be able to open most items, but are unable to make any changes.

Table 2-1: User roles and permissions

 

See User Workgroups and Managing Users for more information on setting up Users and maintaining User Roles.