1. Administration of Profiles

Portal Administration module provides access to the profiles administration under the NEXThink Portal Management section, menu Profiles.

1.1. Managing profiles

Select Administration module, NEXThink Portal Management, menu Profiles to open the roles administration

Profiles Management window allows administrators to create, edit or delete profiles. The "admin" profile can not be edited or deleted.

• If at least one hierarchy has been defined, administrators can also assign access rights on what the profile is allowed view or administrate. If no hierarchy has been defined then there is no references to domains or hierarchies.
• When many profiles are defined, the search tool permits to find quickly a profile using its name, account type, view domain or roles. On the top-right corner a filter allows to limit the view to profiles created by all administrators with same rights or to display all profiles that the administrator could view (i.e., also the ones created in domains lower than his)

• To Add profile, click the icon on toolbox.

• To Delete profile(s), select first the roles to delete (multiples choice allowed) and click the icon on the toolbox.

• To Edit profile, first select the role to edit and click the icon on the right of the name.

1.2. Profile creation

1.2.1. Step 1 - Profile type

In the first step, the type of profile is selected. There are two main types: Reader or Administrator. The third type Central administrator is a particular case of Administrator.

• Reader can only consult information he has access
• Administrator, in addition of reader rights, can create Gallery content (modules, widgets etc..) and manage Portal components
• A central administrator has access on all existing and future hierarchies and he has specials rights like management of profiles, engines and hierarchies.

  
  

Reader has an option which give access (or not) to the Gallery. With this option, the user can organize its content and create its own local modules or dashboards. These modules will be available only for the user and he can not share them. Without the option, the user is limited to the mandatory modules set in its roles.

Administrator has also an option which allow the user to create or not new accounts. If not, the user can only edit the additional content of user.

1.2.2. Step 2 - Administrator options

The second step is required only if "Administrator" has been selected in the first step. This second step permits to set the administration domain and, if the administrator has the right to create accounts, the list of profiles he can use.

The administration domain could be a defined node in the hierarchy or could use the special parameter option. This option permits to select on which level the user will be but it let to the creator to select the definitive node. For example to create one reader for each country, one single profile is needed and each reader account will define its node

The list of profiles depends on the domain set above. All available profiles should be usable by the administration domain associated to profile in creation, it means that these profiles are on same domains or below than the administration domain. So the administrator will have at least the same rights than user he will create.

Note that for central administrators, this step is by-passed since the administration domain is on all hierarchies and he will have access to all profiles.

1.2.3. Step 3 - Reader options

The third step permits to define the view domains and the roles.

View domains defines what the user is allowed to see on its Portal. Only one domain per hierarchy is authorized. For each hierarchy a level and a node must be selected. There are two special values in level which are any and none. any corresponds to the root node and means that the user will have access to the full hierarchy and none is the opposite and doesn't allow to see information related to this hierarchy. For the nodes, the special parameter option permits to select only the level and let the creator to select the node. Optionally a to limit could be defined. This limit defines the details you can see, by default it is on last level (entities) but it could be an upper level.

For administrators, view domains must be compatible with administrator domain set in previous step.

One or more roles could be selected in the list using left click on the mouse in combination with ctrl or shift key. A simple left click select a role and deselect other ones. In combination with ctrl key it permits to select multiple roles or to deselect one in the list.

1.2.4. Step 4 - Finder options

Finally the fourth step defines the Finder parameters. It means that the same username can be used both in Portal and in Finder and the accounts are synchronized with all connected Engines with their view limited by their view domains.