How does the ElevateOS & Resman integration work?

How ElevateOS works with ResMan: what syncs, what to prepare so ElevateOS can connect your buildings, how to use it day to day, and what to check when something does not look right.

Last updated: October 2026
For: property management teams, on-site staff and ResMan administrators

Using another system? See the Yardi, RealPage or Entrata Integration User Guide.

ResMan administrator
What to prepare and how connecting works

On-site staff
Sync schedule, residents, maintenance requests

Something looks wrong
Troubleshooting and what to send ElevateOS Support

Overview

ElevateOS connects each building to ResMan. ResMan stays the place where residents, units and leases are maintained. ElevateOS reads that information on a schedule and never writes it back. Maintenance requests flow both ways: a request created in ElevateOS is sent to ResMan, and status changes made in ResMan come back.

ElevateOS connects ResMan for you

You cannot connect a ResMan building yourself, and neither can dashboard users. In the dashboard, the Resman choice under Integration Type is greyed out. ElevateOS Support connects each building. This guide explains what to prepare and send, and what you will see afterwards. See Connecting your buildings.

At a glance

Function	Direction	How often	What it does
Residents and households	ResMan → ElevateOS	6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time	Creates and updates accounts for people on an active lease, and for approved future residents. Deactivates people who no longer come back from ResMan. Read-only: nothing is sent back.
Units and unit types	ResMan → ElevateOS	Same schedule	Keeps units in step with ResMan and links residents to their units.
Leases	ResMan → ElevateOS	Same schedule	Keeps lease dates and status in step with ResMan. Rent, deposit and balance are not carried.
Work orders	Both ways	Sent to ResMan when submitted. Status changes made in ResMan are checked every 15 minutes.	Requests created in ElevateOS are sent to ResMan first. Status changes made in ResMan come back to ElevateOS.
Resident deactivation	ResMan → ElevateOS	With each sync	Accounts of people who are no longer returned by ResMan are deactivated. They are not deleted.
Rent payments	Not supported	n/a	Pay Rent opens your ResMan resident portal. See Rent payments.
Inspections	Not supported	n/a	See Units, leases and inspections.

Rent payments, inspections, vehicles, pets and custom fields are not part of this connection.

Good to know

ResMan is the source of truth for resident details. Change names, emails, units and move-out dates in ResMan. The next sync brings the change into ElevateOS. Edits made to those fields in ElevateOS are overwritten.

Requirements

Before you start

Your ResMan administrator has to authorize ElevateOS to use ResMan for your properties. ElevateOS cannot see or change settings inside your ResMan account. Your ElevateOS onboarding contact or ElevateOS Support will confirm exactly what is needed for your account.

On the ResMan side

A ResMan administrator who can provide or authorize ResMan access for ElevateOS. ElevateOS will ask for this during onboarding.
The ResMan property for each building. Each ElevateOS building is tied to one ResMan property, and to your ResMan account. Have the property name and ID ready exactly as ResMan shows them.
Access credentials issued by ResMan. ElevateOS Support will tell you how to share them securely. Never put them in a support ticket, chat or email.
Maintenance lists set up in ResMan: categories, areas, locations and the priorities Low, Medium and High. ElevateOS shows these lists in the request form. If a list is empty, residents cannot finish a request.
Unit names that match. A request is linked to the right location only when the resident's unit name in ElevateOS matches a ResMan location name exactly. See Maintenance and work orders.
The Pay Rent link for your ResMan resident portal, if you want residents to have one. It is set during onboarding.

On the ElevateOS side

The building must already exist in ElevateOS and be active.
A building can be connected to one property management system at a time.
ElevateOS Support does the connection. You do not need a dashboard role for it.

Resident data in ResMan

ElevateOS identifies each resident by email. These data rules decide whether a person gets an account.

Rule	Detail
Lease status	People on an active lease (a status such as Current, Month to Month or Notice to Vacate) get accounts. Future residents get an account when the lease is Pending, the person is Approved and a move-in date in the future is set. Applicants and past residents are not imported.
Each person is checked	A household member whose own status in ResMan is not an active one is not synced, even if the lease is active.
Minors	Household members listed as minors are skipped.
Email	Required, and it must be a valid address. A person with no email in ResMan is skipped.
Names	First name and last name come from ResMan.
One person, one email	Each email belongs to one ElevateOS account. A wrong email, a duplicate profile or an email that already has an account in another building can block or mislink an account.
Phone	Optional.
Units	Each person's unit comes from the unit on the lease. Keep units and leases consistent in ResMan.

Connecting your buildings

You cannot connect ResMan yourself

In the dashboard (Places, then the building, then the Integration tab), the Resman option under Integration Type is greyed out and cannot be selected. This is expected. ElevateOS Support connects each building, one building at a time.

What to prepare and send to ElevateOS

You prepare	Why
The list of buildings to connect	Each building is connected on its own.
The ResMan property for each building (name and ID as ResMan shows them)	Each building is tied to one ResMan property.
Your ResMan administrator's contact details	ElevateOS will ask this person to provide or authorize ResMan access and to confirm the property each building maps to. ElevateOS Support confirms exactly what is needed.
Access credentials issued by ResMan	Share them only through the secure method ElevateOS gives you.
Your resident portal link, if you use Pay Rent	The Pay Rent button opens this link.

Tell ElevateOS which buildings to connect. Contact your onboarding contact or ElevateOS Support with the building list and the ResMan property for each.
Your ResMan administrator provides or authorizes access. ElevateOS Support tells you what is needed and how to send it securely.
ElevateOS connects each building. You do not do anything in the dashboard for this step.
Check the result. Use the checks under Verify the setup.

What you will see afterwards

Open Dashboard › Organisation › Places, select the building and open the Integration tab. Organisation is available to Administrator and Manager roles.

Integration Type shows Resman.
The button reads Connected with Resman. This is the sign that the building is connected.
The company and property lists on that tab can still show Property Management Company Not Found and Select Property.... This is expected for ResMan and does not mean the building is disconnected.
A Disconnect button is shown. Do not use it. See Changing or disconnecting.
After a sync, each resident's profile shows a read-only ResMan ID.

First sync

Connecting a building does not start a sync. The building is included in the next scheduled sync (see Sync schedule). If you need the first sync sooner, ask ElevateOS Support. There is no sync button in the dashboard.

Verify the setup

The building shows Connected with Resman on the Integration tab.
After the next sync window, a resident you know is on an active lease in ResMan appears in Clients, and their profile shows a ResMan ID.
Create a test maintenance request for a test unit. Check that it appears in ResMan.
Change the status of that work order in ResMan and confirm ElevateOS shows the new status after the next 15-minute check.
If you use a Pay Rent link, open it as a resident and confirm it lands on your ResMan resident portal.

Sync schedule

What	When
Residents, units and leases	6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time
Work order status changes made in ResMan	Checked every 15 minutes
Work orders created in ElevateOS	Sent to ResMan when the request is submitted

Good to know

Resident sync is not real time. A move-in added in ResMan at 9:10 AM Central appears at the 12 PM sync.
If a sync fails for a building, the next scheduled run tries again.
The dashboard has no sync button, sync log or last-synced time. If you need a building synced sooner, or want to know how its last sync went, ask ElevateOS Support.

Residents and accounts

How residents get accounts

You do not enter residents in ElevateOS. At each sync, a person who is valid in ResMan and has no ElevateOS account gets one, and new accounts are sent a registration email. Residents do not need to register themselves.

Current residents come from active leases in ResMan.
Future residents appear with the Future status when the lease is Pending, the applicant is Approved and a move-in date in the future is set. If the lease is Pending but the person is not yet Approved, or no future move-in date is set, no account is created.
Applicants and past residents are not imported.

Only people found in ResMan stay active. A resident added by hand in the dashboard, or one who registers in the app, is deactivated at the next sync if there is no matching ResMan profile with the same email.

What stays up to date

Name, unit, status, move-in and move-out dates, lease dates and unit type are refreshed from ResMan at each sync. Manual edits to those fields in ElevateOS are overwritten. To change a resident's email, change it on their ResMan profile.

Move-ins and moving from Pending to Current

Update the lease after move-in

After a resident moves in, make sure the lease status is updated in ResMan from Pending to Current. A Pending lease whose move-in date has arrived no longer counts as a future resident. If the lease is not updated, the account is deactivated at the next sync.

When accounts are deactivated

Deactivated accounts are not deleted. A resident is deactivated when any of these is true:

No profile with that email exists in ResMan, or the email in ResMan is different.
The person is on a lease that is no longer active, or the lease is still Pending after the move-in date.
The person has a duplicate ResMan profile with the same email and a Past status.
The account is linked to a building the resident lived in earlier. Contact ElevateOS Support to move it.

Also keep in mind:

The sync decides who is active. For a connected building, activating a contact by hand in ElevateOS does not hold, and the Activate Contact action may not be available. Fix the data in ResMan instead.
Deleting a synced resident in ElevateOS does not remove them. They are created again at the next sync while they are still valid in ResMan.
If a person comes back on an active lease, the next sync reactivates the account.
Residents who sign up with a community code are still deactivated at the next sync if ResMan has no matching active profile.
Test residents created during onboarding are deactivated by the sync unless ResMan has a matching profile. ElevateOS Support can mark corporate, staff or test accounts so the sync leaves them alone. These accounts cannot submit maintenance requests.

Before changing a property in ResMan

If a ResMan property is changed, removed or re-created, residents who no longer come back from ResMan are deactivated at the next sync. Tell ElevateOS before you make that change.

Maintenance and work orders

Lifecycle

A resident or staff member submits a request. Residents use the app. Roles that can create and view requests in the dashboard are Administrator, Manager, Property Manager, Staff and Shift Manager. For ResMan buildings, a dashboard request needs a resident or unit.
ElevateOS sends it to ResMan first. The request is created in ElevateOS only if ResMan accepts it. Because ResMan is contacted first, creating a request can take longer than usual. Wait for the confirmation instead of submitting twice. If ResMan fails, ElevateOS shows an error and does not create the request.
Status changes come back. When a work order's status changes in ResMan, the next 15-minute check updates the request in ElevateOS, including dates and completion notes where ResMan provides them. Completion notes appear as the Job Summary, and long notes are shortened.

The request form

The lists in the form (categories, areas, priorities) come from your ResMan setup each time the form opens. The ResMan form is different from the form for other systems. There are no photos, entry note, short description, subcategory or phase fields.

Resident app

Field	Required	Notes
Description	Yes
Category	Yes	List comes from ResMan.
Areas	Yes	Multi-select. List comes from ResMan.
Priority	Yes	List comes from ResMan.
Permission to enter	No	On by default.
Timeframe preference	No	Appears only when permission to enter is off and your community has it turned on.

After a resident submits, the app returns to the previous screen instead of showing the request detail.

Dashboard

Step 1 asks for the building and the resident or unit (search by name, email address or unit). Step 2 has these fields.

Field	Required	Notes
Select Priority	Yes	Low, Medium or High, as set in ResMan.
Select Category	Yes	List comes from ResMan.
Select Area	No	Multi-select. List comes from ResMan.
Request Description	Yes	250 characters maximum.
Pets	No	Off by default.
Permission to Enter	No	On by default.

Location is set automatically

The form has no location field. ElevateOS sets the location only when the resident's unit name matches a ResMan location name exactly. In the dashboard, Create Request stays unavailable until Priority, Category, Location and Description are all filled in. If the button stays disabled, check that the unit name in ElevateOS matches the location name in ResMan.

What is sent to ResMan

When a request is created, ElevateOS sends ResMan the description, category, areas, location, priority, permission to enter and pets setting, and the name of the person who submitted it.

Not sent to ResMan: photos, assignee and cancellation reason.

Changes after a request is created

Edits made in ElevateOS after creation (priority, category, location, permission to enter, pets) may not reach ResMan. Make important changes in ResMan as well.
Status is managed in ResMan. Complete and cancel work orders in ResMan. A status change made only in ElevateOS may not reach ResMan.
Cancelling in ElevateOS asks for a free-text Cancellation Reason. The reason stays in ElevateOS.
ElevateOS updates a request from ResMan when its status changes. Other edits made in ResMan come across only together with a status change.
The ResMan work order number is shown in the request detail heading and in the file name of the PDF. Use it to find the order in ResMan.

Work orders created in ResMan

Work orders created directly in ResMan for a unit are not imported into ElevateOS. Create unit requests in ElevateOS so both systems have them. Work orders in ResMan that are not tied to a unit can be imported.

Status names

ElevateOS reads these ResMan statuses.

ResMan status	Shown in ElevateOS as
Submitted, Not Started	Pending
In Progress, Scheduled	In Progress
On Hold	On Hold
Completed, Closed	Finished
Canceled, Cancelled	Canceled

A ResMan status that is not in this list is not mapped. If you use other status names in ResMan, tell ElevateOS Support.

Units, leases and inspections

Units and unit types

Units come from ResMan and are read-only in ElevateOS. ElevateOS uses them to link residents to units, and unit types come from ResMan. Units that ResMan no longer returns are marked inactive.

Leases

Active and pending leases are read from ResMan. ElevateOS keeps lease dates and status as read-only data and records each household member's role on the lease. A lease that is no longer active or pending in ResMan is closed in ElevateOS. Rent, deposit and balance are not carried and are always empty. Nothing about leases is sent back to ResMan.

Inspections

ResMan is not integrated with inspections. In Checklists › Settings › Manage Inspection, a ResMan building shows Not integrated. The Activated toggle is unavailable and there is no unit type merge step. Ask your ElevateOS representative if you need inspections for a ResMan building.

Rent payments

ElevateOS does not read rent balances or post payments to ResMan. The in-app payment flow is not available for ResMan buildings.

If your building has a Pay Rent link, residents are sent to your ResMan resident portal. The link is set during onboarding. Payments made there are outside ElevateOS, and the portal has its own sign-in. If a resident cannot sign in to the portal, they should contact your property team or ResMan, not ElevateOS.

Changing or disconnecting

Before you change anything

Tell ElevateOS before any change in ResMan that affects the connection: a property removed, re-created or replaced, a new ResMan account, or a move to another system. Do not wait until after the change.

Do not disconnect a building yourself

The Disconnect button is available on the Integration tab, but reconnecting is not. ElevateOS Support has to reconnect a building, because Resman cannot be selected in the dashboard. If you want to disconnect or change a connection, ask ElevateOS Support first.

If a building is disconnected, it stops syncing and no longer sends requests to ResMan. The building's synced unit data is cleared and the ResMan link is removed from its residents' profiles. Resident accounts are not deleted.

Changed property or account in ResMan

Send ElevateOS the new property name and ID. Support updates the connection.
History from the old connection, such as old work orders, does not move.
Plan the change with ElevateOS so residents are not deactivated by an empty feed.

Switching from ResMan to another system

Tell ElevateOS before the cutover. After a building is disconnected, requests that are still open no longer sync with ResMan, so plan how to handle them. ElevateOS will plan the order of steps with you.

Troubleshooting

What the dashboard does not show

The ElevateOS dashboard has no sync log, no last-synced time, no sync button and no connection test. It does not show why a particular resident or work order was skipped. ElevateOS Support can check sync status for a building. See What to send ElevateOS Support.

I cannot select Resman, or the building shows "Property Management Company Not Found"

The Resman option is greyed out for every account. ElevateOS Support connects the building.
On a connected building, Property Management Company Not Found and Select Property... are expected. Look at the button. If it reads Connected with Resman, the building is connected.
If it is not connected, contact ElevateOS Support. Do not disconnect and try again.

A resident cannot log in

The email the resident uses must match the email on their ResMan profile.
The lease must be active, or the person must be an Approved future resident. A Pending lease after the move-in date is not enough.
The account may have been deactivated by a sync. See When accounts are deactivated.
If the resident is trying to sign in to the Pay Rent portal, that sign-in belongs to ResMan.
Send ElevateOS Support the resident email and unit.

A future resident got no registration email

In ResMan, the lease must be Pending, the person must be Approved and a future move-in date must be set.
The person needs a valid email on their ResMan profile.
Wait for the next sync window.

An account was deactivated after move-in

Check the lease status in ResMan. If it is still Pending, change it to Current. The next sync keeps the account active. If it was already Current, check that the email on the profile has not changed and that no duplicate profile with a Past status shares it. Then contact ElevateOS Support.

A resident does not appear in ElevateOS

Wait for the next sync window.
In ResMan, check the person has an email, a name and an active lease, or is an Approved future resident with a future move-in date. Applicants, past residents and minors are not synced.
Check that no other ResMan profile uses the same email.
Check the building shows Connected with Resman.
Send ElevateOS Support the resident email and unit.

Two residents share an email, or an account shows in the wrong building

ElevateOS keeps one account per email. Fix duplicate profiles in ResMan. A person who lived at another ElevateOS building may still have an account there. Contact ElevateOS Support to move it. Sync does not move accounts between buildings.

A name or unit is wrong or not updating

Name, unit, status and dates come from ResMan. Fix them in ResMan. Edits made in ElevateOS are overwritten at the next sync.

Nothing has updated for a building

The dashboard has no sync log. Ask ElevateOS Support to check sync status for the building and tell them what you expected to see.

A work order reached ResMan with no unit

Older app versions can send a blank unit. Ask the resident to update the app and submit again.
Check that the resident's unit name in ElevateOS matches a ResMan location name exactly.

The Create Request button is disabled

Priority, Category and Description must be filled in.
Location is set automatically, and only when the unit name matches a ResMan location exactly. Check the unit name against ResMan.
Send ElevateOS Support the unit and building if it still stays disabled.

I got a generic error when creating a request

ElevateOS shows only a general message when ResMan does not accept a request, and the request is not created. Ask ElevateOS Support for the details. Send them the building, unit, category, priority and the time you tried.

A work order completed in ResMan still shows Pending

Wait for the next 15-minute check, and refresh the page. If the request still shows Pending, contact ElevateOS Support with the ResMan work order number and the request ID.

A work order created in ResMan is not in ElevateOS

Work orders created directly in ResMan for a unit are not imported. See Maintenance and work orders. Create unit requests in ElevateOS.

A change I made in ElevateOS is not in ResMan

Changes after creation, including status, may not reach ResMan. Make the change in ResMan as well.

A ResMan property was changed or replaced

Contact ElevateOS Support before the change if you can, and send the new property name and ID. A changed property can make the connection invalid, and residents who no longer come back from ResMan are deactivated at the next sync.

Manage Inspection says "Not integrated"

This is expected for ResMan buildings. See Units, leases and inspections.

What to send ElevateOS Support

☐ Building name
☐ The ResMan property name and ID as ResMan shows them
☐ Resident email and unit (for resident issues)
☐ For maintenance issues, the resident, unit, description and date, the ElevateOS request ID and the ResMan work order number
☐ For app issues, the phone type and app version
☐ The date and time it happened, with time zone
☐ A screenshot of what you see, and of the profile or work order in ResMan if you can
☐ What you already checked in ResMan

Never send credentials in a ticket, chat or email.

FAQ

Can I connect ResMan myself?

No. ElevateOS Support connects each building. The Resman option in the dashboard is greyed out for all users.

What do I send ElevateOS?

The list of buildings, the ResMan property for each, and your ResMan administrator's contact. ElevateOS Support will confirm exactly what else is needed and how to share ResMan access credentials securely.

How often does ElevateOS sync with ResMan?

Residents, units and leases sync at 6 AM, 9 AM, 12 PM, 3 PM and 6 PM Central Time. Work order status changes made in ResMan are checked every 15 minutes.

Do I need to create residents in ElevateOS?

No. Add them in ResMan with an email and an active lease, or as an Approved future resident with a future move-in date. Accounts are created at the next sync.

Can I edit a resident's name or unit in ElevateOS?

Those fields are refreshed from ResMan at every sync, so edits are overwritten. Change them in ResMan.

Does the Pending to Current lease change matter?

Yes. After move-in, update the lease status in ResMan. A lease that stays Pending after the move-in date stops counting as a future resident, and the account is deactivated at the next sync.

Can residents pay rent in the ElevateOS app?

Not for ResMan buildings. Pay Rent opens your ResMan resident portal.

Can I add photos to a maintenance request?

No. The ResMan request form has no photo upload.

Should I disconnect a building to fix a problem?

No. Disconnecting is available, but reconnecting is not. Contact ElevateOS Support first.

Does ElevateOS provide ResMan technical support?

No. ElevateOS supports the ElevateOS side of the connection. Questions about ResMan settings, resident profiles and the resident portal go to ResMan or your ResMan administrator.

What ResMan does and does not do in ElevateOS

Feature	With ResMan	Notes
Residents, units and leases	Yes, read-only	ResMan to ElevateOS, several times a day.
Work orders	Yes	Created in ElevateOS and sent to ResMan first. Status comes back from ResMan.
Rent, deposit and balance on leases	No	Always empty.
Rent payments and ledger	No	Pay Rent is a link to your ResMan resident portal.
Inspections	No	Manage Inspection shows Not integrated.
Vehicles	No
Pets	No	Only the Pets toggle on a work order is sent.
Custom fields	No
Photos on work orders	No
Assignee and cancellation reason on work orders	No	These stay in ElevateOS.
Phase filters for staff	No
Applicants and past residents	No	Not imported.
Connecting from the dashboard	No	ElevateOS Support connects each building.
Sync log, sync button and connection test in the dashboard	No	Ask ElevateOS Support.

Other property management systems that ElevateOS supports may cover more. If a feature you need is missing here, ask your ElevateOS representative.

Quick reference

Glossary

Property	One community in ResMan. Each ElevateOS building is tied to one ResMan property.
Account	Your ResMan account. Buildings of the same company can share it, and each building has its own property.
ResMan ID	Shown on a resident profile. It identifies the person in ResMan and is read-only.
Lease status	The status of a lease in ResMan, such as Pending, Current or Notice to Vacate. It decides whether a resident gets an account.
Location and Area	Two lists on a ResMan work order. The location is the unit. Areas are the parts of it that the request is about.
Not Applicable	A status ElevateOS Support can set so the sync leaves an account alone, for corporate, staff or test accounts. These accounts cannot submit maintenance requests.

Setup checklist

In ResMan

☐ ResMan administrator identified and available to provide or authorize access
☐ The ResMan property for each building collected (name and ID)
☐ Categories, areas, locations and priorities set up for work orders
☐ Unit names match the ResMan location names
☐ Resident emails, names, lease status and move-in dates checked

With ElevateOS

☐ Building list and properties sent to your onboarding contact or ElevateOS Support
☐ Access credentials shared only through the secure method ElevateOS gave you
☐ Integration tab shows Connected with Resman
☐ Pay Rent link set up by onboarding, if you use one

After the first sync

☐ A known resident on an active lease appears with a ResMan ID
☐ A test work order reaches ResMan and a status change comes back
☐ Staff know to update leases from Pending to Current after move-in