This is more of an issue in consistency in behaviour.
While a systemuser only works under the context of his office, he "can" create
child offices on offices at the same level or higher.
Steps to Reproduce:
1. Make two divisional offices under MifosHO. Say DO1 and DO2.
2. Make a system user with admin rights SU1 in office DO1.
3. Login as SU1.
4. Now try creating a Branch Office in office DO2. He can!
The way our office hierarchy works everywhere is inconsistent with this
behaviour. SU1 should not be allowed to make Branch Offices under DO2. Like
everywhere else, DO2 and Mifos HO should not even be visible as a choice. SU1
should only be able to make child offices under DO1 and DO1's child-offices.
Platform: All, OS: All
Pooja - this is a great catch. We agree that this is a data scope issue where
users under one divisional office should not be able to create offices or see
data under a different divisional office. We will address this issue in a
release after v1.1.
Still see this issue in Gazelle C, this should be fixed...
Bug still exists in Release 2.2