Note: Property Access is currently available to select customers only. If this feature is not visible in your Settings, it hasn't been enabled for your account yet. Contact your Re-Leased representative for more information.
Property Access lets you control which properties each user in your organisation can see and work with in Re-Leased. By default, all users have access to all properties - restrictions are opt-in. As an Administrator, you can limit a user's view to properties belonging to specific owners, within specific property groups, or a curated list of individual properties.
Who Can Set Up and Receive Property Access Restrictions
Only users with the Administrator role can see Property Access in Settings and manage restrictions.
Restrictions can be applied to any user with a user role other than Administrator. Administrators always have access to all properties, so they do not appear in the user list when you set up restrictions.
How to Navigate to Property Access
Navigate to Settings in the main menu.
Under the Company & Users section, select Property Access.
The Property Access page displays all users who have active restrictions configured, along with a summary of the owners, groups, and individual properties each user is restricted to.
How to Find Users With Property Access Restrictions
Use the controls above the restrictions table to find a user or check who can see a particular owner, group, or property:
Search users... - search by the user's name.
Filter by owner - show users whose restrictions include the selected owners. The list includes owners from all companies you have access to.
Filter by group - show users whose restrictions include the selected property groups.
Filter by property - show users whose restrictions include the selected properties.
Where a user is restricted to many owners, groups, or properties, click the names in that column to open the full list and search within it.
How to Set Up Restrictions for a User
On the Property access page, click + Set up restrictions in the top right corner.
Select the user or users you want to configure access for. Once confirmed, their name will appear at the top of the screen indicating which user/s the settings are being applied to. To edit the users, click Change users.
Use the three panels to choose which properties the user can access:
Owners - tick one or more property owners. The user will see all properties associated with those owners.
Groups - tick one or more property groups. The user will see all properties within those groups.
Properties - tick specific individual properties.
Use the Filter... search in each panel to find owners, groups, or properties quickly.
Use the Filter... search in each panel to find owners, groups, or properties quickly. Counters in the User panel show how many owners, groups, and properties are currently selected. A user with nothing selected shows as Unrestricted.
Once saved, a Saved successfully confirmation appears. Click Select more users to set up restrictions for someone else, or View active restrictions to return to the Property access page.
Note: You can combine owners, groups, and individual properties in any combination. A user will see all properties that match any configured restrictions.
Setting Up Restrictions for Several Users at Once
You can apply the same restrictions to several users in one save by selecting more than one user in step 2 above.
If the users you select already have different restrictions from each other, a Conflicting permissions message lists the affected users. Click Continue anyway to proceed, or cancel to change your selection. If you continue, a warning stays at the top of the page as a reminder.
Important: When you save restrictions for several users who had different existing restrictions, your new selection overwrites all of their existing restrictions.
How to Edit Existing Restrictions
On the Property access page, locate the user whose restrictions you want to update.
Click the three-dot menu (...) on the right side of their row and select Edit access
Adjust the owner, group, or property selections as needed.
Click Save for 1 user to confirm the changes.
Note: Saving replaces the user's existing restrictions entirely with your new selections. Any previously saved configuration will be overwritten.
How to Remove All Restrictions from a User
Removing all restrictions from a user restores their access to all properties - the default state.
On the Property access page, click the three-dot menu (...) on the user's row.
Select Remove restriction.
Confirm the action when prompted.
Important: Once restrictions are removed, the user will immediately have access to all properties in your organisation.
How Property Access Restrictions Work Across Re-Leased
Once restrictions are saved, they apply across the platform - not just the property list. Restricted users will only see data associated with their permitted properties across these areas:
Dashboard and global property search,
Property groups,
Leases and rent reviews,
Invoices, credit notes, receipts, and repeating invoices,
Budgets,
Arrears, owner fees, and late fees,
Maintenance, work orders, and inspections,
Compliance and insurance,
Documents and reminders, and
Utility meters and deposits.
Note: Access to all properties remains the default for all users. A user must have at least one restriction saved before the permission applies to them.
Features Restricted Users Cannot Access
Some areas of Re-Leased show data across your whole organisation rather than by property. Users with Property Access restrictions cannot open these areas, even if their user role includes the permission:
Insights - the Insights menu item and dashboards are hidden
Audit Log - the Audit Log option does not appear in Settings
To give a user access to these areas again, remove their Property Access restriction.
Frequently Asked Questions
Q: Does restricting a user's property access affect what they can edit, or just what they can see?
Restrictions control visibility only - if a user can see a property, they can edit it. Read-only access within the permission layer is not yet available.
Q: What happens to a user's access if a new property is added to an owner or group they're already assigned to?
It's automatically included. When you restrict by owner or group, the user inherits any new properties added to that owner or group without needing to manually update their access.
Q: If I restrict a user by owner, can they see properties owned by an owner group that owner belongs to?
Yes. Restricting by owner includes properties owned directly by that owner and properties owned by any owner group the owner is a member of.
Q: Can restricted users still see archived properties?
Yes. Archived properties that match a user's restrictions stay visible to them, so they can still view and restore them.
Q: Can I restrict an Administrator's property access?
No. Administrators always have access to all properties and do not appear in the user list on the Property access page. To restrict someone who is currently an Administrator, change their user role first.
Q: Does removing a restriction immediately affect the user's access?
Yes. Changes take effect as soon as you save. There is no delay or approval step.
Q: If I assign a user by owner, group, and individual property, how does the access combine?
They are additive - the user sees all properties that match any of the configured restrictions. There is no "and" logic between the three types.
Q: Are these settings separate from the existing "Has access to properties" permission?
Yes. The existing permission controls access to the Properties tab in settings. Property Access restrictions are a separate, independent layer that controls which properties appear across the platform.
Q: Does Property Access apply to mobile apps and Re-Leased Pay?
Not yet. Mobile apps and Re-Leased Pay are outside the current scope of Property Access restrictions.
Q: Do restrictions apply to reports?
Most reports respect Property Access restrictions, but a small number of reports (arrears, aged arrears, and occupancy) that run via background tasks are currently excluded and will be addressed in a future update.