Integration Consent Tracking Reference Guide

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.

About Resident Consent Tracking

• Staff-managed inside ALIS. 

• Lives on the resident's Compliance Summary. 

• Consents are driven by the partner apps enabled in your community. 

• Every change is audited. 

💡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.

Why it Matters

More of the services communities rely on require a documented resident opt-in. Consent Tracking gives your team one trusted, centralized place to capture and prove that consent, so you can walk into any survey ready.

Consent Tracking gives you:

• One source of truth: consent lives on the resident's Compliance Summary, not in a binder or spreadsheet.
• Audit-ready records: pull a complete consent matrix across a community or the whole portfolio.
• A clear staff workflow: a defined place to capture consent at move-in or as care changes.
• Compliance confidence: every change is captured with who, what, and when.

Enable Consent Tracking 

Enablement is primarily handled in the background by ALIS and the integration partner. 

1. Work with your Account Manager and/or the ALIS Integrations Team to enable the partner app. 
2. The ALIS team enables the app partner's required consents.
3. Review your Company's Security Role Permissions. Any staff member who can view a resident's Compliance Summary can see Consent Tracking. No new permission is required. 

Once your community has that partner's app enabled, the Consent Tracking subsection appears automatically in each resident profile's Compliance Summary. 

Don't see Consent Tracking? If the Compliance Summary section is empty when you expect to see a consent, it usually means no enabled partner in that community requires consent yet. Contact your ALIS Account Manager for assistance.

How It Works

1. Driven by your apps: the consents you see are determined by the App Store partner apps enabled in your community (set up by your ALIS administrator).
2. Tracked per resident: each applicable consent shows on the resident with a status staff can update anytime.
3. Lives in the Compliance Summary: Consent Tracking is an expandable section inside the resident's Compliance Summary, grouped by integration partner.
4. Audited automatically: every change is recorded in the resident's history for a defensible trail.

The Three Consent Statuses

• Opted In: the resident has agreed; the service can be provided.
• Opted Out: the resident has declined; the service should not be provided.
• Not Collected: the default until staff records a decision; counts as no opt-in yet.

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

Consent Types 

Five consent types exist with this feature. Which ones appear depends on what the enabled partner apps require:

Consent Type	What it covers
General Consent	General use of the resident's data by the vendor
Two-way Voice Consent	Two-way voice communication
Two-way Voice Recording Consent	Recording of two-way voice communication
AI Triage Consent	AI-assisted triage
Virtual Care	Virtual care services

Recording, Importing, and Auditing

Day-to-day actions are covered in the companion how-to guide, How to Record and Manage Resident Consent (for Integrations):

• Record a single consent on the resident's Compliance Summary.
• Bulk update many residents via the Import Center (ideal for onboarding or adding a new vendor). 
• Audit per resident (Audit History) or across a community or portfolio (consent matrix export). 

For Integration Partners

Consent Tracking also serves App Store partners. This is configured with the ALIS Integrations team, not by community staff:

• Partners declare the consent their service requires as part of their App Profile. It then appears automatically on residents in any community that enables the app, with no per-site setup.
• Partners can read a resident's current consent status through the integration API and are notified by webhook the moment a status changes.

Full API and webhook specifications are covered in a separate partner technical briefing. For partner setup, contact the ALIS Integrations Team.

FAQs

Is consent history saved if the app is disabled? 

Yes. Even if a vendor is later removed, prior consent records are retained for your audit trail. 

Can residents see their own consent history? 

Not at this time. Consent data is captured for staff and partner systems; there is curently no resident-facing view.

What if a resident transfers between communities?

Consent is stored per resident, so prior values follow them. The new community's view shows rows only for the vendors enabled there, but the underlying history is preserved.

Can we backfill consents collected on paper? 

Yes, you can do so by using the "Resident Consents" file via the Import Center. The filled template pre-populates each resident and consent row with its current status, so you can update the status column and re-upload. 

What does "No consents required" mean?

"No consents required" just means no enabled vendor requires consent yet. It is not an error.

Can a family member opt in or out from ALIS Connect? 

No. Consent is purely staff-managed in ALIS, and ALIS Connect is unchanged.

Related Articles: 

• How to Record and Manage Resident Consent (for Integrations)

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