Language: Suomi | Svenska | English
← Back to Port user guide table of contents
1.3 Organisation maintenance
1.3 Organisation maintenance
The maintenance of the organisation is a centralised view of the browser interface, managing organisational information, users, rights; and technical and operational contacts with other actors; and systems.
The main user (admin) can view and update the following information and settings:
| Tab | Activities |
| Organisation | Update basic information: name, contact details and identifiers |
| Users | Invite new users and manage access rights. |
| Access Groups | Create and manage rights by group. |
| National Port API | Configure and manage interface between systems. |
Conditions of use
Maintenance of the organisation is available when you are logged into NEMO and selected an organisational account (if multiple) and you have an organization access rights to the main user (admin).
The main users of the organisation shall be responsible for the organisation's information: and access rights are always up to date. NEMO not automatically identify incorrect or outdated information and do not report it; user.
Organisational information included in port call notifications (MAI) title information. Incorrect or incomplete information may cause: problems in receiving or processing notifications from authorities action.
This is how you move maintenance of the organisation;
opens from the main menuMenu menu (in desktops) upper right corner, lower right angle on mobile) ja Select Organisation maintenance
see as defaultOrganisation- The view. Go to Different between maintenance scenarios to review the organisation's data, users, access groups and interfaces;
Edit Organisation information
Data support user identification and rights management, contacts and communication between authorities and organisations; reporting and monitoring.
Organisation contact person
A contact person has been selected for the organisation, acting on an official basis: As contact with the authorities. Contact:
receive NEMO e-mails, for example, when: the ship's certificate has expired or Port call; the notice indicates a deviation requiring action;
the contact person's records are recorded on the transmitted notification; header data (MAI)
This is how you edit the organization information
opens from the main menuMenu menuand select Business Maintenance
review and edit the required information in the Organisation tab
press Save when the changes have been made
see that the organisation's data have been recorded
Maintenance of users
Main user can add and remove users, change their roles and its categories of access and determine who acts in the organisation as a liaison. Contact person information is automatically stored the heading of the port call declarations (MAI) sent as part of the operation. Keep user and contact details always up-to-date before notifications This is the case.
Type of user
Each operator of an organisation shall be selected from one of two: type of user:
Main user (admin)- maintain an organisation information, users, access groups and interface links. Yeah. add, edit and delete information in accordance with its access group. It is recommended that the organisation has at least two main users ensure continuity of operations.
Member (basic)- see, add, edit and remove information in accordance with its access group.
User information
The following information is recorded for each user:
| Information | Description |
| Name | Automatically comes from the Suomi.fi authentication service of the user accession. The name cannot be modified in NEMO. |
| Corresponding to the email address given by the user at the time of accession. Used to send invitations and notifications. | |
| Type of user | Admin = Main user with rights management of the organisation. You can be chosen as the contact person. Basic = Normal user who can view and process the data in accordance with its access group. |
| Access Group | ReadWriteAll = Full reading and editing rights any information managed by the organisation. PUBLIC = Only public information is visible, no editing rights. Own groups = Organisational teams which: the operator can determine as appropriate. Recommended for each the organisation creates its own user-specific access groups; in accordance with the rights of access. |
| Waiting for processing | User has been invited to the organization but has not yet approved invite or finalized accession. |
Invitation of a user organisation
The main user may invite a new user to the organisation by giving: the type of user, e-mail address and access group. Call After posting the user receives an email link for membership of the organisation.
The user has access only to organisations for which: He's been invited separately even if he's already a user in NEMO.
This is how you invite a user organisation
selectCall User
fill in the type of user, access group and email address (or addresses)
pressInvitation
you receive a notice confirming that the invitation has been sent
Change of type of user
The main user can change your own or other user type. The type of user cannot be changed in the case of the organisation's sole main user.
When the user type changes, access rights also change. If you move as a member of your type, you can no longer maintain an organisation.
This is how you change the user type
select user and other type of user from the bottom pull menu
receive a notification confirming the type of user update
Access group Amendment
Main user can change your own or other users access group. The Access Group shall determine which information: the user has access.
This will change the user Access group
select user and other access group from the bottom pull menu
receive a message confirming user information update
Removal of the user organisation
The main user can remove the user from the organisation. Deleted the user's access to the account of the organisation ends immediately.
This will remove the user
select the user and press the removal button
confirm the deletion
receive a message confirming the removal of the user
Exclusion
The main user can remove himself from the organisation. This removes all rights to that organisation, including maintenance rights. You can't leave if you're the only one in the organization. main user.
Removal takes place in the same way as other users deletion: select your name from the user list and follow instructions under Removal of the user from the organisation.
Maintenance of access teams
The Access Group determines what information and activities the user can use use in NEMO and to what extent. For each user select a right of use group when invited to an organisation.
There are two types of access groups:
Own access groups- organisation the main user can create, edit and remove these groups necessary with.
General Access Groups- predefined Groups that are immediately available and can be connected directly users. Cannot be removed.
Go to Access Groups tab Company maintenance.
General Access Groups
| Name | Contains |
|---|---|
| Public port information | The user may apply for and view vessels for their arrival and Based on departure times, the public port call information view. |
| Read notifications, send delegated notifications | The user may:
|
| Read notifications | The user may:
|
This is how you create your own access group
pressCreate Access Group
fill in the group name and select access rights
pressSave
You can see the created access group
This is how you edit your own Access group
select your own access group
edit the group name and / or selected access rights
pressSave
see that the access group has been updated
This will remove your own access group
select your own access group to delete
press the removal button
confirm deletion
you see that the access group has been deleted and is no longer visible list
check the user access group if recently deleted the group has left the user
National port Use of API interface
National Port API interface allows Port calls review of notifications relating to, dispatch to NEMO, notifications the transmission of reception and port statistics to the authorities. The interface uses the REST protocol and the JSON format.
You need:
Organisation account in NEMO
Main User Rightsso you can API tab
API data for identification
Port API
Select port API when your organisation is a port operator that controls and manage the operation of the port area. The interface allows you to download statistics, arrival, departure and vessel data Using the REST protocol.
Go to the technical Port API instructions for the guide: Integrate Suomen Maritime Single Window (NEMO) - National API - Port API
Data Service Use of Provider (DSP)
The port organisation can use external Data Service Provider (DSP) implementing technical interface integration and NEMO data apply on behalf of the organisation.
DSP will always act as a service provider authorised by the port organisation. The DSP will not automatically have its own access to the port organisation data in NEMO, and DSP cannot request or form itself port organisation API symbols.
If a port organisation uses the DSP, the port organisation shall:
be registered in NEMO
establish the necessary API for its organisation; and To that end, form a Client ID and a Client Secret (Client) Secret)
provide the appropriate API codes to the DSP it uses; safe
ensure that the symbols are maintained, renewed and, if necessary, their removal;
DSP uses the interface with the port organisation codes acting on behalf of that organisation. Responsibility for API connection and the management of associated symbols remains: the port organisation.
If Client Secret disappears, is discovered or DSP is terminated, the port organisation must renew or remove the API connection codes; NEMO.
Client ID and Client Secret
Client ID identifies an organisation that: use API. Press Create Connection. to connect The connection cannot be changed manually.
Client Secret works like a secret key couple alongside the Client ID. It is used for API invitations for authenticity.
If the Client Secret is lost, leaked or compromised, The API link must be removed and reestablished, creating a new The Client Secret.
When new The Client Secret?
A new Client Secret shall be created for example in the following situations:
change the integration system or server within the organisation; using API connection
the current Client Secret has disappeared or is no longer found system
suspected that the Client Secret has been discovered or abuse;
API-yhteys poistetaan ja luodaan uudelleen (esim. konfiguraation muutosten vuoksi)
Like this Enable national API reporting boundary
opens from the main menuMenu menuand select Business Maintenance
openAPI tab
pressCreate a connection
API connection created and information (Client ID and Client Secret) visible
Like this new Client Secret to the national API interface
openAPI tab.
selectCreate a new Client Secret
press Save when the changes have been made.
National Removing API interface
If a national API interface is no longer necessary, it can be removed by the main user of the organisation. After removal sending notifications via API is not successful, so the organisation must: introduce another mode (interface or RIM interface).
Remove National API interface
openAPI tab
pressRemove interface
confirm API removal