Organization and users management

An organization administrator can access different tracking and management features via left menu.

Tracking test times

  • The tab Test times shows the total time consumed for the license over the current month and the total time consumed over each month since the start of the license.

  • A click on a month display usage times consumed per application in the organization.

temps_application.png

 

  • In the bottom screen, a summary shows the usage times consumed per active user in the organization

License details

In the shared instance https://app.greenspector.com(https://app.greenspector.com), an administrator is only an administrator of his organization and the details are not useful. The feature to see license details of one organization is not implemented yet.

In dedicated instance, an administrator can see the details of his license (start time, end time, number of application and number of users)

Users management

Users tab displays the list of users.

An administrator can create a new user or modify user type or disable / enable a user.

User type

The administrator can choose a type for a user

  • Administrator : An administrator can create an application, view all applications of their organization, add members to an application but can only contribute to their applications.

  • User : A user can create an application, contribute to their applications or to the applications that are shared with them by an administrator.

  • Guest : A guest can only see applications that are shared with them.

  • Saas : This type is only available for new incoming Greenspector interface, the user will not be able to connect to the actual interface. This type should not be set manually by administrator.

Add a user

If the administrator create a user with ‘send an email’, the new user will received a mail to set his password.

If the administrator create a user with ‘Define the password’, the administrator must choose a password for the user. This is useful for example to create user which is not true person like a user used by continuous Integration. If there is no true person, the administrator can set false email, for example ci@myorganisation.local