Changes

Jump to: navigation, search

Administrating MINT

104 bytes added, 09:19, 6 October 2014
no edit summary
==Managing organisations==__NOEDITSECTION__
{{Note | Organisations only exist in MINT, there is no equivalent in lightMINT.}}
===The organisation concept===
The ''organisation'' concept in MINT is a way to have separate, private ''spaces'' for each mine action programme, operator, or any other actor using MINT. Each organisation has its own data sources, reports, dashboards, etc. that only users belonging to that organisation can access (depending on their specific permissions). For example, users from the organisation ''MAC1'' cannot access objects from the organisation ''MAC2''. An exception to this are organisations in parent-child relationships. For example, the organisation ''MAC1'' could have a sub-organisation named ''Regional MAC1''. In this case, users from the parent organisation ''MAC1'' can access the objects of the child organisation ''Regional MAC1'', but not the other way round.
The organisation name needs to be provided when logging into MINT. There is no drop-down list of organisations, so users need to know the exact spelling of their organisation.
[[File:MINT_login_box.png|center|200px]]
 
===Adding sub-organisations===
{{Note | Administrators of an organisation can create sub-organisations. The initial parent organisation has to be created by the global MINT administrator though. This is done when a programme / actor decides to get started on MINT.}}
1,068
edits

Navigation menu