Administrating MINT

From IMSMA Wiki
Revision as of 09:15, 6 October 2014 by Evinek (talk | contribs)
Jump to navigation Jump to search
This page is under construction

Managing organisations

Organisations only exist in MINT, there is no equivalent in lightMINT.

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.

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.


Managing roles

Managing users

Managing the folder structure

Managing permissions on objects

{{#switch:|subgroup|child=|none=|#default=

}}{{#ifeq:|Template|{{#ifeq:|child||{{#ifeq:|subgroup||{{#switch:administrating mint

|doc
|sandbox
|testcases =
|#default = {{#switch:hlist
 |plainlist
 |hlist
 |hlist hnum
 |hlist vcard
 |vcard hlist = 
 |#default = 
 }}
}}

}}}}}}