6. Landlord access
To allow landlords access to the back office we need to link their Entra directory to the system. In order to do this we need to know their domain. This is the part of their email addresses after the '@'.
In order to do this efficiently we would ask for you to collate all the landlords who you wish to have access so that we can set them up in one go.
Landlord setup
When a user from a landlord initially tries to access the system this is what they will see:
The Sign you in and read your profile is essential for the Single Sign On to work as it gives our system permission to know about the currently logged in user (name, username, email addresses).
The Read all user's basic profile is optional as it just enables the ability for them to add their users into the Huume system, rather than waiting on them logging in for the first time and then assigning roles. This permission allows one of their users to search their Entra directory so they can find users and the system can get the required information to setup their access (Entra Object ID, name, username, email addresses).
This permission does require an Entra Admin to consent to this (by checking the Consent on behalf of your organisation or via the Entra Enterprise Application pane in Azure Portal).
If they are uncomfortable with granting this permission, then you can just decide not to grant the Admin Consent (i.e. don't check the Consent on behalf of your organisation ). The Huume system will still work but they just won't be able to use our Add User functionality to setup their users in advance.
However, to clarify, none of these permissions give Huume (or anyone else) access to their Entra directory. These permissions only control what their own users will have access to do whilst using the Huume system. Any requests to retrieve data from their Entra directory need to be authenticated and be from one of their valid users.
Landlord teams
A Team will need to be created for each landlord before you can set their users up. A landlord team will typically be granted the following permissions:
Assigning a Team and Role
Once a user has accessed the system they will will have a User account automatically created but won't have any permissions or be able to do anything in the system. They will need to have both a Team and a Role assigned to their account.
Once a Team and Role has been assigned to a user they may need to click on the Reload menu option in the left-hand explorer before they see their permissions updated
Related Articles
How can Registered Providers be setup to use multiple teams?
The Landlord and Team structure within the system allows for flexible filtering of data so that users are only able to access the data that is relevant to the their roles. However for some users, i.e. managers, they may require a wider view of the ...Blank screen when trying to access the back office - Supported browsers
If you encounter a blank screen when trying to log into the back office please check the browser you are using. The Huume solution is designed to work on all modern HTML5 compliant web browsers. Browsers must support the below functionality, which ...Release v3.5.1 01/11/2021
New & improved Back office Permissions The People & Cases permission group has been split into the following groups: People Cases Cases: Bedroom assessments Cases: Health assessments Cases: Homeless (English) Cases: Risk assessments Cases: Tenancies ...10. Users, Teams & Roles
Users Users are granted access to the system through your organisations Azure AD configuration, or can be added manually. When editing a user certain fields cannot be modified as they are managed through Azure AD. If the Users First name and Family ...Release 7.0.1 17/04/2023
New & improved Back office Comms A new message sub type has been created called Housing register bid/offer letter. This sub type allows fields to be added from: - Property - Void - Landlord - Bid When creating a Comms message using this type the user ...