How to Record and Manage Resident Consent (for Integrations)

Consent Tracking is an add-on feature that gives communities one structured place to record, manage, and prove resident consent for the services your App Store partner integrations require. It is built right into the resident record, replacing spreadsheets and paper.

💡Currently available with the Inspiren integration only. Inspiren is the first App Store partner to use the Consent Tracking feature. The steps below apply to any partner that adopts it in the future.

For more general information about this feature, see the Integration Consent Tracking Reference Guide.

Locate Consent Tracking

Consent Tracking is an expandable section inside the resident's Compliance Summary:

1. Go to Residents and select the resident.
2. Scroll to the Compliance Summary section.
3. Expand the Consent Tracking subsection.

Rows are grouped by integration partner, with the vendor name and a row count.

Workflow 1: Record a single resident's consent

Use any time a resident or responsible party gives or withdraws consent.

1. On the resident, expand Compliance Summary, then Consent Tracking.
2. Find the consent on the row you want to update.
3. Set the Status dropdown to Opted In, Opted Out, or Not Collected.
4. It saves itself. The "Success - Consent updated" message confirms the status change. 

💡Re-selecting the same status a resident already has will have no effect (no change, no duplicate entry, and no confirmation message).

Workflow 2: Update many residents at once (bulk import)

Ideal for onboarding, entering paper records, or quickly updating all current resident and applicant statuses when a new vendor is added.

1. Navigate to the Import Center.
2. Download a template:
   • Blank Template (under Import File): The file contains just the column headers, with dropdown validation in Excel.
   • Pre-Filled Template (under ALIS Data): This downloads every current resident and applicant in the community (in alphabetical order), each row showing its vendor, consent, and current status.
3. Under Data/Data to Import, select Resident Consents.
4. Fill in the six required columns, save, and upload the file. 
5. On the Data Prep screen, ensure options are set to Yes and Resident Consents; you should not have to change any fields. Click Go to Next Step.
6. The Map Headings screen confirms that the columns in your spreadsheet will import the data into the intended ALIS fields. All six columns should be included. Click Go to Next Step. 
7. On the Review Data screen, fix any rows flagged red (if applicable). The Import button stays disabled until every row is valid. Click Import.
8. The batch shows its progress under Past Imports. 

Import file columns (all six required)

If a row is flagged on 'Review Data'

If any rows are flagged as errors, they will need to be updated or deleted in order to import the file. Click directly into the file on the screen to make changes.

Once you have fixed an error, click the Reevaluate button to ensure the issue was resolved. Once all errors are cleared, the Import button will become available again.

Possible error types:

• Community Name is invalid: the name doesn't match a community you can access.
• Resident First/Last Name is invalid: no active or applicant resident in that community matches the name (discharged residents are excluded).
• Integration Partner is invalid: the vendor isn't enabled in that community, or has no consent requirements.
• Consent is invalid for the selected Integration Partner: that vendor hasn't declared that consent.
• Consent Status is invalid: the status isn't one of the three allowed values.
• Duplicate found: two rows target the same resident, vendor, and consent. Keep one and remove the other.

Review and Audit Consent

There are two ways to review and audit resident consent statuses: 

1. Per resident

The resident profile's Audit History lists every change (for example, "[Consent Type] consent for [Partner Name] set to 'Opted In' from 'Not Collected'."), with the staff name who updated the record.

2. Across a community or portfolio

In the Import Center, use Download ALIS Data, then Resident Consents, to export residents and their consents as rows. Run it for one community or the whole portfolio to get a complete matrix. 

Important Considerations

• If you see "No consents required" justthis means no enabled vendor requires consent yet. It is not an error.
• Consent values follow a resident who transfers communities, and history is retained even if a vendor is removed.
• Consent is staff-managed. Families do not see or edit it in ALIS Connect.
• Only active and applicant residents can be recorded or imported; discharged residents are excluded. 

For answers to more frequently asked questions (FAQs), refer to this Integration Consent Tracking Reference Guide.

Related Articles:

• Integration Consent Tracking Reference Guide

For more assistance: 888.404.ALIS (2547) | support@go-alis.com