Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • All users that are members of a Top level agency has access to all Containers within that agency's Country, with the rights given by the assigned role in user management. 
  • In a reconciliation context, the rules of file disclosure and agency-induced global rights applies, not the Container role.Losing you're global rights:specific container role from the Containers of participating files. The rules of file disclosure can be found here: Linking and Reconciliation (Flow & lingo).  The general rule is that if the two files are from the same agency, no file disclosure is needed.

  • Losing your global rights on activating a file from a Container 
    When you start the system, you can see your current role in the

    statusbar

    status bar at the bottom of the screen (available from version 5.1.0.3) :
    Image Modified

    You will always be able to track

    you're

    your current role in the

    statusbar

    status bar

    Once you activate a file from a container where

    you're

    your rights are different from your agency-based global rights,

    these

    the rights of the current active file kick in globally. In this example an Administrator users rights are reduced to be Read Only: 
    Image Modified

    The user can return to the "

    global

    normal" state by

    clicking on  

    clicking  Image Modified 
     

    Warning
    titleAssigning container roles to users

    You should not give a user access to administrative operations through a role in a container that she doesn't already have. Potentially this could be taken advantage of while the file is active.
    E.g. If the user globally has a Read Only role through the agency and she is given Admin rights in a specific Container, then while a file from that particular container is active, she has all the rights of an Administrator in the system and can mess with stuff she's not supposed to mess with.