We split the name by the first space and assign the first part of the name as the First Name and the second part as the Last Name. For example:

We import the first email from a lot into our system. This is because the MyHome section will display sensitive financial Levy information.

As a result, all subsequent emails should simply be invited to the platform manually (or via a site code) as an owner so customers don't have to risk account info being shared with users not tied to the ownership.

In this scenario, an owner/user is associated to all the lots they own within a scheme/site. They can switch between lots when viewing Levy information or submitting requests.

When imported across different sites, owner/users can access multiple sites (including the MyHome section for the additional lot) by switching sites within the resident application.

No, the only user who can access the MyHome section and lot levy information are those who have been imported via the PIQ integration. Users already in the system won't be "linked".

The scheduler is an automatic function in the Resvu system that runs every 24 hours for your account. This will check the PIQ system for any changes in Site details, Documents, or Users. Think of this as a syncing feature to ensure all the details are up-to-date across both systems.

Every 24 hours the scheduler will run, our system will then check to see if any details have changed in PIQ. You can see what details get imported and checked here. If there's a change, it'll automatically update in the Resvu platform.

This included the email address used to log in to the system, meaning if a user updates their email address in PIQ, they'll need to use that new email to log in to the resident application.

Every 24 hours the scheduler will run, the Resvu system will then see there's a new User ID against the lot. As such, the Resvu system will remove the old users from that site (meaning they no longer have access to the site, lot information, and won't be able to login to the resident application).

If they are only a part of one site, they'll no longer be able to log in to the resident application. If they are a part of another site, the old user will still have access to the resident application for the remaining site(s).

No, any changes you make to a user, site, or document are not pushed back to the PIQ system at this point in time. This integration is currently a one-way system. If the scheduler is enabled for the site, then these changes will be overridden by the data in PIQ the next time the scheduler is run.

For example, if you rename a site in Resvu, it will return to the original name within 24 hours when the scheduler is run. This means in order to make any changes, please do so from PIQ.

If you delete a site in Resvu, it will be removed from your Resvu account and all the users against that site will also be deleted. In the PIQ integrations page, the site will be removed from your Previously Imported Sites list and returned to the search results when fetching a site.

This means you can re-import the site in the future if you wish, however you'll need to also re-import the users, plus the site code will be different.

If you delete a user from within a site, they'll be added to the Deleted Users list under User Management, and no longer have access to that site. If they are a part of multiple sites under your account, they'll still be able to log in to the platform and access those sites.

If you delete a user from account management, they'll be removed from the system entirely - including all sites they are assigned to.

When the user scheduler is run next, they won't be imported again either. If you'd like to re-import this user, please get in touch with the Resvu support team.

Resident App & Resident Portal

We import the following data into our system for each item:

Sites

Documents

Lot owners