With Swiftlane-Yardi integration, we can help properties automate access management for residents, increasing security, and reducing burden on onsite teams.
What Swiftlane - Yardi Integration Does
- Automatically sync existing tenants into Swiftlane and send them invites to Swiftlane for self-onboarding
- Automatically deactivate tenants who move out, based on move outs in Yardi
- Automatically invite residents to download the swiftlane app and enroll for access, when they move-in
Steps to Configure Swiftlane Integration within Yardi
Here are the high level steps involved in getting Yardi connected to Swiftlane. You will see a more in depth explanation below:
Step 1 - creating a user for Swiftlane inside Yardi and giving it permissions to specific properties
- Create a new user for Swiftlane inside Yardi. You can name it anything e.g. "swiftlane"
- Save the username and password for that to be shared with swiftlane account representative later
- Create a user property list e.g. ".swiftlane-props" inside Yardi
- Assign the relevant properties to this property list, and assign this property list to the swiftlane user
Step 2 - Setting up ILS Guest Card Interface for Swiftlane
Go to Interfaces inside Yardi, Select ILS/ Guest Card and click submit.
Then search for Swiftlane integration on the right side to open up the details.
The ILS integration page will show up. Click Save to activate the integration.
If you are properly licensed for and using Voyager 7S, please ask the client to contact Yardi technical support to request that the add-on package be manually added to the qualified vendor lists in Voyager. Finally, clients with questions about compatibility between their Voyager 7S or other Yardi software and your product or service should contact a Yardi account manager directly. Yardi does not discuss client information of this nature directly with third-party vendors.
- Clients can confirm that Swiftlane is a fully qualified standard interface vendor by viewing the Available Interface Vendor List_Client.xlsx on Client Central.
- Clients must enter a case in Client Central to have the vendor add-on package loaded into their database.
- Clients can review/download the Common Data and ILS Guest Card Interface Setup Guides posted on Client Central for detailed information on how to configure the interface.
- If Clients need additional assistance with configuration, their Yardi account manager or core support team can help.
- Clients will provide Swiftlane with the following access information:
- Their Voyager URL
- Interface Username
- Database name
- Server name (always the same as the database name)
You can send these credentials to firstname.lastname@example.org to get assistance with setup, or follow the dashboard instructions directly to set it up.
Steps within Swiftlane
Once you have received your Yardi credentials, you can configure the connection on the Swiftlane dashboard - https://www.admin.swiftlane.com
Go to Integrations, Edit Yardi. If you dont see the option there please contact email@example.com to get it activated. Create a new connection or Edit the current connection if you already created on in draft.
A few attributes will be pre-populated and non editable. Those are - Property Id, Name, Description, Address, Connection status as received from API.
A few of the configurations will have default values set which admins can change during configurations -
- The default status will be 'Configuration Pending'
- Create Tenant Entry, Auto-Sync and Send Auto Invite will be default 'No'
- Tenant Display Name format will be defaulted to 'Unit Number' if Create Tenant Entry is enabled.
Default Groups: Admins can mark few groups as 'Default groups' from their account. Any new resident added to the Site will be added to this group and he'll get access to all the doors to which this group has access.
Create Tenant Entry: When this is ON, for each resident added, there will be a Tenant entry created in Tenant Directory for that site (based on Tenant Directory Settings)
Tenant Directory Creation Rule: There are 3 options for Tenant Directory entry creations
- Unit Number - There will be one entry created for every unit. All the residents who have that Unit Number assigned to them will be added as recipients for that Tenant Entry. This is recommended option as it'll create only 1 entry per unit and will be easy for visitors to understand whom to call.
- First Name + Last Name + Unit Number - There will be multiple entries created for every unit in case there are multiple residents with same unit number linked to them.
- First Name + Last Name - Same as above. There will be multiple entries for same unit number.
Auto-Sync: When this option is enabled, Swiftlane will sync with PMS every 2 Hours and update user's CRUD status. If new residents are added, he'll get created as a Swiftlane User and corresponding tenant entry will be created automatically. Similarly, on lease end, the users will get deactivated in Swiftlane.
The deactivated users will not be able to access any doors, EP app, etc. They'll remain in system for 3 months and then get deleted. Workspace admins can activate the users again manually, in case needed.
Send Auto Invite: Any newly added user during auto-sync process will get email invite sent automatically and he can start using Swiftlane app once he registers. We recommend keeping this on.
Tenant Directory Settings: These settings are mainly to define the Tenant entries to be shown in each Swift reader. There is 1 option - Yardi Site to Swiftlane Site mapping.
If customer has only 1 Swift reader set up at 1 site, he can directly map Yardi Site to Swiftlane Site. Here, all tenant entries created at this site will be shown in Swift reader at that Swiftlane Site.
Once you have provided Swiftlane with your Yardi credentials then our support team will enable and configure your Yardi account. You can send your Yardi credentials via email to firstname.lastname@example.org.