This guide explains how Resvu works and how to run it day to day. Read it top to bottom if you're new, or jump to the section you need. Most sections link to a short video (under three minutes) and a full article.
1. What is Resvu?
Resvu streamlines the daily management of residential communities through five core functions:
Outbound resident communications — send bulk or targeted messages to whole communities, specific buildings, or individual residents.
Inbound resident requests — manage requests, applications and venue bookings submitted by residents.
Information access 24/7 — store documents, contacts, useful links and connection details residents can reach any time through the app.
Committee management — run committee discussions, approvals and voting through a dedicated Committee Hub.
Resident management — add and maintain community members across all your buildings.
Together these deliver:
Administrative efficiency — see where everything is at a glance, prioritise easily, and collaborate as a team.
Resident transparency — residents see real-time updates on their own requests, so they chase you less.
Committee engagement — committees see what's happening and vote on items, with every decision permanently recorded.
Record keeping — once information is in the system it stays there and can be traced back at any time.
Resident self-service — residents find what they need without contacting the strata manager.
2. Finding your way around
Resvu uses a top bar across the admin portal, giving you navigation, settings and support from any screen. Help and support sit behind the help icon in the top bar.
Global selectors appear throughout the system and control what you're working on:
Community selector — work on one community, several, or all. Search by name, scheme number or address.
Resident selector — find residents by name, lot or unit.
Audience selector — target user types, groups, committee groups or named individuals.
If a selector doesn't show what you expect, it's almost always permissions or community assignment on your admin account.
3. How integrations work
Most customers run a partner platform alongside Resvu. When the two are connected, the integration keeps core community information aligned between the systems, so you can use Resvu for communication, documents, requests and resident engagement without maintaining the same details separately in two places.
One important framing: integrations are designed to complement your partner platform, not replace it. That platform remains the primary source of records, and Resvu reflects what's held there.
Integrations live under Settings > Integrations. To manage any of this, your admin account needs full access to both Integrations and Residence under Settings > Admins > Roles & Permissions.
What comes across
Partner platform integrations all support the core information needed to establish and run communities in Resvu:
Community, building or scheme details
Lot details
Owners, tenants and their contact information, including their lot associations
Committee members
Supplier, creditor and contractor information
Levy information, including levy lists and balances
Beyond that core set, each partner platform has its own additional capabilities and data fields. What you actually see in Resvu depends on which platform is connected and on the records maintained in it, so two customers on different platforms won't necessarily see identical data.
Communities come across automatically
Active communities in your partner platform flow into Resvu on their own. You don't need to create them by hand. If a community is active on that side, it will appear here.
The one manual job left is to assign admins to those communities. This is worth knowing, because a community can be sitting in Resvu perfectly happily and still look missing to you. If you can't see a community, check Settings > Communities first. If it exists there and you still can't see it elsewhere, you almost certainly just need to be assigned to it.
Contractors come across automatically too
Like communities, contractors flow into Resvu from your partner platform on their own. Once the integration is set up there's no import step and nothing to maintain. Some partner platforms also bring contractor compliance information across with them.
Residents have to be brought across by an admin
This is the part that catches people out. Residents do not arrive automatically to begin with. Active residents from your partner platform land under Settings > Integrations > User Management > community > Pending import, and an admin decides who actually comes across. There are two ways to do it:
Import individual users — pick specific people out of the Pending import tab.
Go Live for a whole community — bring everyone across at once, choosing which user types to include: owner-occupier, tenant, owner-investor, committee, and in some cases property manager and other.
Which user types you get depends on your partner platform. Some send property manager and other across, some don't. To check what yours provides, go to Settings > Integrations > User Management and look at your communities. You'll be able to see whether those user types are populated with residents.
When you run a bulk import, either for a single community or for several at once, Resvu shows you the estimated number of welcome emails about to go out, so you can sanity-check the number first. Once imported, residents:
move into the Imported tab
are sent the welcome email you configured under Settings > Invitation Email, assuming you toggled send welcome email on during the import
show as Pending Activation under Residents > Users, again assuming the welcome email was toggled on
show as Not Invited under Residents > Users if you left the welcome email toggled off, ready for you to invite later
can begin receiving communications and be assigned to requests
Read more: View and import community members
Automatic import and how it switches on
Automatic import doesn't change how residents get into Resvu. What it changes is where you see them. Instead of going into each individual community under Settings > Integrations > User Management and filtering through your communities to find new people, everything new turns up in one place: the resident user table under Residents > Users.
Two things to know first. It's enabled per community, not across your whole organisation. And it isn't a switch you flip. Resvu marks it on for a community once that community has no residents left waiting in Pending import. To get a community there:
Go to Settings > Integrations and select the relevant integration.
Open User Management and find the community.
Either use Go Live to bring everyone across at once, or Import users to bring them across individually.
Once no residents remain pending for that community, the Automatic import column is marked automatically. You'll find this under Settings > Integrations > User Management. You need full Integration access to import users, and a community needs at least one imported resident before it counts as live.
What changes once it's on
Anyone added in your partner platform flows straight through to the resident user table, arriving as:
state Active — a live record in the community
app status Not Invited — in the system, but not yet emailed
To give them access, filter the resident user table by Not Invited, select them, and choose Resend Invitation from the three-dot menu. Their app status moves to Pending Activation.
The nightly sync
The integration syncs every night. Anything changed in your partner platform during the day, such as new residents, ownership changes or committee membership, is picked up by the nightly sync and reflected in Resvu the following morning. New residents picked up this way show as Not Invited.
So don't expect same-day changes to appear instantly. If something looks missing, it's usually just waiting on the next sync.
Editing integrated records
Imported residents are flagged as Imported in the Source column. If you edit one of those fields in Resvu, that account becomes hybrid. Resvu keeps your version and the partner platform stops syncing those particular fields from then on. That's handy when a resident gives you a better mobile number, and less handy if done by accident, so edit deliberately.
Read more: Managing integrated resident data
Documents, levies and payments
Documents can also come through the integration, based on how you configure your document categories. You choose which categories to pull, what to call them, who they're shared with, and the date to show them from.
Levy information is a big one: the moment a resident or committee member has access, levy details become visible to them, provided the account is connected to a partner platform. It's often the single most compelling reason to bring residents on sooner.
In-app payments are handled by a separate payments connection, set up the same way under Settings > Integrations.
Watch: Import documents via API
Read more: Configure document categories | All integration articles
4. How communities come into the system
Everything in Resvu hangs off a community, so this is usually the first thing to get sorted. Communities arrive one of two ways:
Automatically from your partner platform — active communities flow in on their own, with no import step.
Created manually — set them up under Settings > Communities if you aren't integrated, or if the community doesn't exist on the partner side.
Either way, the one thing you do by hand is assign admins. Until an admin is assigned to a community, they won't see it in the places they'd expect.
Active and archived
An active community is one you can work in. Admins can be assigned to it, workflows can be assigned to it, and you can get on with setting it up.
An archived community is one you've finished with. It's kept for historical record rather than day-to-day use, so it isn't somewhere you assign admins or workflows.
Live and not live
Live is a separate idea from active, and it's only about residents.
Not live — no residents have been invited into the community. It's being used internally only. Your team can still raise requests, issue quotes and work orders, and build everything out.
Live — at least one resident has been invited to begin using the platform, whether they came across from your partner platform or were created manually.
This distinction matters more than it first appears. It means you can run a complete Phase 1 rollout on a community that isn't live, because Phase 1 is about getting your own admin team working in the platform and none of it depends on residents being there.
For the practical steps of configuring a new community, see Setting up a community further down.
5. How residents come into the system
There are four ways residents get into Resvu:
Via a partner platform — the most common route, covered in the integrations section above.
CSV import — bulk upload using the provided template.
Manually — an admin adds one user at a time.
Self-registration — residents register themselves using the community code, found under Settings > Communities. Self-registrations sit as Pending until an admin approves or denies them.
Watch: Invite residents via integration | Manually add a user | Setting up resident self registration
Getting residents activated
Being in the user table isn't the same as having app access. Every resident has both a state and an app status.
Resident states show their standing in the community:
Active — in the user table. Can receive emails, be assigned to requests and reservations, and be exported.
Pending — self-registered and awaiting admin approval.
Denied — the self-registration was rejected.
Archived — no longer in the community. Kept for historical record only, with no access and no communications.
App statuses show whether they can log in:
Live — activated, password set, terms accepted. They can use the app or portal.
Pending Activation — sent a welcome email in the last 7 days, not yet activated.
Activation Expired — the 7-day link lapsed. Resend the welcome email.
Not Invited — added by CSV or integration but never sent a welcome email. Send one to move them toward Live.
Opted Out — chosen not to use the portal. Contact them by post or phone instead.
Welcome emails expire after 7 days as a security measure, so check activation status about a week after inviting and resend where needed.
Managing the resident list
Beyond getting people in, you'll group residents for targeted communications, export the table for reporting, and archive people when they move out. Archived residents keep their history but lose all access.
Read more: How to add new community members
6. How requests come in and get managed
Requests are the workhorse of Resvu. The flow is always the same: a workflow defines the form, a request comes in through one of several routes, then your team manages it on the dashboard and optionally turns it into a quote or work order.
Workflows, the forms behind every request
A workflow is the form a resident fills in. You control its fields, its stages, which communities it applies to, and who can see it. Workflows must be assigned to a community before anyone there can submit.
Common workflows: maintenance request, pet application, renovation application, access key & card request, FOB request, feedback form, incident report, insurance claim, general enquiry, update my details, levy arrears payment plan, schedule a callback, committee enquiry to strata manager.
Watch:
The four ways a request arrives
A resident submits it through the app or portal.
An admin raises it from the dashboard on a resident's behalf.
From Outlook — the Resvu Outlook add-in turns an inbound email into a request without leaving your inbox.
Via a public link — enable external access on a workflow to share a form with people who don't have an account. You then assign the community and requester when it lands.
Watch:
Read more: How requests come into Resvu
Managing requests on the dashboard
The dashboard is where your team will spend most of its time. Tabs separate requests, quotes, work orders and closed items. You can filter by community, ID, status, priority, assignee and date, customise which columns you see, and export results to CSV.
Inside a request you can edit the details, set properties (requester, assignee, status, priority, follow-up date), link related items, and comment. Comments come in two kinds: public comments are visible to the resident, internal comments are admin-only. Everything is captured in the activity log, which can be downloaded as an audit trail.
You can also share a request with the committee or the wider community, generate a live link, and close it when done.
Watch:
Read more: Managing a request via the dashboard
Quotes and work orders
From a request you can issue quote requests to contractors and work orders to get the job done, or create either as a standalone item. Both stay linked to the originating request, so the resident sees progress and you keep the full history.
The typical path: raise a quote request to one or more contractors, contractors return prices, you attach them, the committee votes if needed, then you convert the winning quote into a work order and issue it.
Before you start, populate your contractor list, which can be filled manually or from your partner platform, and set up your quote and work order email templates so everything going out is branded and consistent.
Watch:
7. Communicating with residents
Resvu gives you five outbound communication types. Pick based on urgency and shelf life:
Alerts — urgent and reactive. Water outages, lift faults.
Notices — planned communications. AGM notices, maintenance windows.
Newsletters — regular community updates.
Procedures — permanent references. Move-in and move-out processes, community rules.
Surveys — structured feedback you can export.
Each can be built from a template or uploaded as a PDF, targeted at a community and audience, and sent by email, SMS or push notification. Reusable templates save time on anything you send regularly. The communication log shows what went out, to whom, and whether it was read.
Watch:
8. Committees and the Committee Hub
The Committee Hub is a dedicated area of the app where committee members discuss topics, vote on approvals, and follow progress on requests and work orders.
Committee groups
Committee members belong to committee groups, one per community. If you're integrated, groups are created and populated automatically and sync overnight. Otherwise you create the group and add members manually.
Topics and voting
A topic is a discussion thread. Add a vote to it when you need a decision, with options, a close date, and settings for visibility and anonymity. If a member votes off-platform, you can record it on their behalf and attach the correspondence. Votes and topics can be exported as a permanent record.
Watch:
9. Community information and documents
Community information
This is the 24/7 self-service part of the platform. Three content types show in the app:
Community contacts — strata manager, building manager, concierge, committee chair, after-hours and emergency contacts.
Useful links — by-laws, council information, welcome packs, owners portal, your company website.
Connections — gas, electricity, internet, water, Foxtel connection details.
Watch: Create and edit community contacts | Create and manage useful links | Create and manage connections
Documents
Documents are uploaded manually or imported from your partner platform. Typical content: AGM documents, by-laws, financials, contracts, building plans, forms, manuals, warranties and welcome packs. When uploading you choose which communities and which user types can see each file, so you can keep something visible to committees only, or share it with owners and tenants. Files with no user permissions land in the Internal tab, visible to admins alone.
10. Reservations and venues
Admins create venues that residents book through the app. Typical venues: lift bookings for moving in and out, gym, BBQ area, tennis court, cinema, dining room, kitchen, meeting rooms.
For each venue you set availability windows, booking duration, notice periods, limits, terms of use, and whether bookings need admin approval. Admins can also book on a resident's behalf and view bookings by future, past or calendar view.
Lift bookings are usually the single most useful feature for residents, so get that venue configured before you activate them.
Watch: Creating a venue for residents to make bookings | Approve a reservation | Manage resident reservations
11. Internal tasks
Tasks are for your team, not residents. Use them for anything you need to track internally: AGM checklists, resident callbacks, debt collection, insurance renewals, inspections, onboarding or offboarding a community.
Tasks carry an assignee, due date, priority and status, can hold files and subtasks, and can be linked to a request, quote, work order or committee topic. You can duplicate a task across communities when the same job repeats.
Watch: Create a task | Managing tasks
12. Setting up a community
Go-live checklist for a new community
Work through this before inviting residents:
Assign admins — Settings > Admins > Edit, or Settings > Communities > Edit.
Assign workflows — Workflows > Options > Edit > Communities > Add community. Residents can't submit anything until a workflow is assigned to their community.
Set up community information — contacts, useful links and connections.
Assign venues — Reservations > Venues > Edit > Communities > Add community.
Upload documents — manually, or automatically from your partner platform.
Toggle app features — Settings > App features. This is set per community and applies to committees and residents alike.
Customise the invitation email — the first impression every new user gets.
Watch:
13. Other modules worth knowing
Asset register — create, track and report on community assets, including costs, warranty details and attachments. Create and manage assets
Concierge tools — parcel deliveries, visitor and security logs, shift logs, and local business deals for on-site teams.
Resident engagement — community events, social clubs and a community wall for resident posts.
JACmedia digital displays (add-on) — physical screens installed in the community, acting as a digital notice board. Alerts and notices sent from Resvu can be pushed to them. JACmedia setup
14. Common issues
A resident hasn't received their invitation email. Check their status under Residents > Users. Not Invited means nothing has been sent, so send one manually. Activation Expired means the 7-day link lapsed, so resend it.
A resident can't activate their account. The invitation email contains an "Activate your account here" button. They must activate before signing in.
A resident can't reset their password. Password resets only work on activated accounts. If they haven't activated, they need the activation link. Resend the invitation if it has expired.
A manually added resident can't register. They can self-register using the community code under Settings > Communities. Integrated users don't need to self-register. They just activate from the invitation email.
A resident can't set a password. Passwords need at least 8 characters, one uppercase letter, one number and one special character (e.g. @ * & $).
A resident can't download the app. The app is only available in Australian app store regions and needs Android 14 or higher. They can use the online resident portal instead, which has the same functionality.
A migrated resident is on the wrong app version. The login screen must show v25.0.0 or higher. Anything lower is Version 2, which is no longer supported.
A community isn't showing up. Check Settings > Communities. If the community is there, you just need to be assigned to it.
15. Where to go next
Every short video referenced above is collected in one place in the Short video library, grouped by area. That's useful when you know the task you want and just need the short version.
If you're rolling Resvu out for the first time, follow the three-phase approach. Roll out to your internal admin team first, then your committees, then your residents. Each phase has its own guide: