You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
24 lines
1.9 KiB
24 lines
1.9 KiB
3 years ago
|
# Definitions
|
||
|
|
||
|
- **Stock owning organisation** (parent): an organisation that owns housing stock (parent). It may manage the allocation of people in and out of their accommodation, or it may contract this out to a managing agent (child).
|
||
|
|
||
|
- **Managing agent (child)**: These are about orgs. In scenarios where one organisation owns stock and another organisation is contracted to manage the stock and tenants, the latter organisation is often called a ‘managing agent’. A managing agent is the same as a child and is the term more commonly used by data providing organisations. Parent/child is what we call them internally but is not a term that should be used for external customers. Managing agents are responsible for the allocation of people in and out of the accommodation, and/or responsible for the services provided to support those people in the accommodation (in the case of Supported Housing).
|
||
|
|
||
|
# Permissions
|
||
|
|
||
|
## Organisational relationships:
|
||
|
|
||
|
Organisations that own stock can contract out the management of that stock to another organisation. This relationship is often referred to as a parent/child relationship. This is a useful analogy as a parent can have multiple children, and a child can have many parents. A child organisation can also be a parent, and a parent organisation can also be a child organisation:
|
||
|
|
||
|
![Organisational relationships](images/organisational_relationships.png)
|
||
|
|
||
|
The case logs that a user can see depends on their role:
|
||
|
|
||
|
- Customer Support users can access any case log
|
||
|
- Data coordinators can access any case log for which the organisation they work for is ultimately responsible for, meaning they can see logs managed by a child organisation
|
||
|
- Data providers can only access case logs for which their organisation manages (or directly owns)
|
||
|
|
||
|
Taking the relationships from the above diagram, and looking at which logs each user can access:
|
||
|
|
||
|
![User log access permissions](images/user_log_permissions.png)
|