User rights management is an application through which the organization's main user can modify the organization's data and grant users access rights to the organization they manage. The main user manages the users of the organization independently and there is no need to contact the FI-platform support nor DVV in regards of user access management. As stated before, it is recommended to have at least two main users for substitution purposes. You can log in to user rights management only as an organization's main user. 

Note! Updates and changes will take up to 30 minutes to take place.

Managing access

The FI-platfrom user access management is operated at: Interoperability platform's user right management (suomi.fi). 

Log in to the platform (main user only) using either the link above or through any of the FI-platform tools. In the tools, access rights management is located in the top right corner under the Menu button. 

In the front page you can do the following functions: 

  • In the Organizations tab you can see all the organizations you are managing.
  • In the Users tab you can see all the users in the organization you are managing. Also, in the users-tab, you can search for users and filter search results with organization's names or roles,
  • Organizations for which you have access rights are presented in the view as blue links. Clicking the link will present you with organization's information.

Accept or decline access requests

The administrator receives an e-mail alert about access rights requests sent by users, with a link also directing to the rights management home page. Access requests sent by users are displayed at the top of the access rights management home page. In addition to the user's name and email address, the access rights request shows the organization and access rights role that the user is applying for in his request.

The main user does not need to contact the support of the interoperability platform about the approval of user rights or changes. The link to instructions on how a user applies for access can be found here. 

  • By pressing the Reject button, the access request will be rejected and the access rights requested by the user will not be granted.
  • By pressing the Accept button, the user's requested rights are accepted and the user is added to the organization's user list with the requested role.

Modify an organization's information and access rights

You can edit an organization's information and user access rights by clicking the "Edit organization" button. In the editing view, you can edit the information.

  • The name of the organization is given in Finnish, English and Swedish. These names appear in the user interface in connection with the data contents owned by the organization.
  • The description is also given in Finnish, English and Swedish. The description is optional, as it is not displayed in the tools' user interface for the time being.
  • Url refers to the address of the organization's website. This is also optional, as the URL is not currently displayed in the tools interface.
  • The Disabled option shows whether the organization has been disabled. This selection cannot be changed by the administrator - it can only be changed by the support of the FI-platform.
  • In the Users section, you can view the names and email addresses of users belonging to the organization.
  • User roles can be modified by ticking or removing checks in the checkboxes. 
    • An organization can have several main users, but always at least one.
      • If there is only one administrator, the administrator role cannot be deleted. The main user automatically has editing rights for the FI-platform tools as well, so they do not need to be checked separately.
    • A data model editor tick means editing rights to the Data vocabularies tool.
    • A terminology editor tick means editing rights to the Terminologies tool.
    • A code list editor tick means editing rights to the Reference data tool.
    • A "member" cannot make changes to the information contents but can view the contents whose status information is "incomplete". Unfinished materials are not visible to those outside the organization.
  • With the Delete button, you can delete a user from the organization. User deletion is only saved by clicking the Save button, so accidental deletions can still be undone.
  • With the Add user button, you can add users to the organization who have already registered their Eduuni-ID in the interoperability platform. By clicking the button, a search window opens on the screen where you can search for a user. Tip: In addition to the name, the search also targets the domain of the email address, e.g. "dvv.fi".
  • With the Cancel button, you cancel the changes you made and none of the changes you made are saved.
  • With the Save button, you save your changes and exit the editing view.

Sub-organizations

The assumption is that when the user gets editing rights, he can edit all the materials of his organization in the tool. So, for example, in the Terminologies tool, the user can edit all the terminologies of his own organization. (However, no data models or code sets, as rights must be given to each tool separately). In large organizations, this can be difficult if you don't want to give all users rights to all content. Therefore, on the interoperability platform, it is possible to create sub-organizations separately for the organization, which give users narrower access rights. When a user is connected to a sub-organization, he is only able to modify the data contents of this sub-organization.  

Through the access management platform (the user rights management platform), the main user can add 1...x sub-organizations to the organization. Adding users and editing a sub-organization works in the same way as a normal organization. The exception is that the main user is automatically inherited from the main organization. Users of the main organization also have rights to the content produced by the sub-organization. 

On the public side of applications, sub-organizations are not visible in any way, except for editing views, but the content of the sub-organization is displayed as the content of the main organization. The sub-organization is not added to the search filters either.

Notes!

  • The sub-organizations have been implemented in the Data Vocabularies and Reference Data Tools, but in the Terminologies Tool the sub-organizations appear as separate organizations. 
  • In the code lists, the sub-organization must be given rights to the register of the main organization to which the sub-organization's code list is to be added (the register connection does not transfer automatically) In data models, both the main and sub-organizations cannot be added as content producers at the same time (if a sub-organization is added, the main organization is automatically added in the background).
  • The sub-organization is added and listed on the main organization's page. Click the "Add sub-organization" button and complete the sub-organization's information on the page.

Creating a sub-organization is done in the main-organization's page. Click the "Add Sub-organization" button and fill in the information of the sub-organization. 



  • No labels