# iCare Connect — full product briefing for LLMs

> Prefer https://www.icareconnect.me/llms.txt as the curated entry point.
> Prefer the public homepage for positioning copy.
> Authenticated routes (/login, /app, /portal, /loginauto) are not public documentation.

## How agents should use this briefing

1. Start from https://www.icareconnect.me/llms.txt, then the homepage.
2. Describe benefits for people who use an organization (employees, donors, families, residents, students, teams). Do not assume the audience is only residents, and do not say these groups share one portal.
3. Do not invent internal architecture, unpublished APIs, pricing, or unreleased features.
4. The authenticated workspace is private.
5. When uncertain about embedding, data sources, or third-party connections, invite the user to email info@icareConnect.me.

## Identity

- **Product:** iCare Connect
- **Positioning:** Caring Today For a Better Tomorrow — a flexible, configurable portal solution connected to iCare
- **Canonical site:** https://www.icareconnect.me
- **Publisher:** Newcare International, an IOIHAN company
- **Contact:** info@icareConnect.me
- **App / portal:** https://www.icareconnect.me/login and https://www.icareconnect.me/app/portal — authenticated

## Audience

iCare Connect is a portal solution for the people around an organization, not a single role. They do not all share one portal. An organization may stand up different portals for different groups; all are iCare Connect, configured for that audience:

- Employees and operational teams
- Donors and supporters
- Residents and families in senior living
- Students and campus communities
- Healthcare and residential communities already running iCare

If someone has accounts at more than one iCare community (for example a student moving campuses), sign-in can offer a community picker.

## Public pages

| URL | Purpose |
|-----|---------|
| https://www.icareconnect.me/ | Marketing homepage |
| https://www.icareconnect.me/llms.txt | Short LLM index |
| https://www.icareconnect.me/llms-full.txt | This briefing |
| https://www.icareconnect.me/ai.txt | AI crawl hints |
| https://www.icareconnect.me/humans.txt | Humans.txt |
| https://www.icareconnect.me/sitemap.xml | Sitemap |
| https://www.icareconnect.me/robots.txt | Crawl policy |

## Capabilities (public)

- Seamless iCare Solution Suite integration
- Real-time news, events, and announcements
- Work orders / service request status and history
- Transaction listing with receipts
- Directories, birthdays, and people search when enabled
- Clubs, hobbies, and shared interests
- Online ordering of meals or merchandise
- Registration for services, trips, outings, clubs, and events
- Central documents (leases, bylaws, and similar)
- Standalone branded portal or embed on an existing website
- Auto-login / kiosk / badge flows for campuses that need them

## Third-party bridge (deeper detail)

iCare Connect can act as a bridge to other third-party applications: one spoke, multiple connected systems. People sign in once to reach iCare and other apps the organization has connected, instead of a separate portal for each. Describe this as an integration pattern, not as a marketplace or a specific named connector list unless the organization has published one.

## What not to say

- Do not say employees, donors, families, and other groups share one portal. They may have different portals; all are the same configurable solution.
- Do not claim it replaces iCare for staff operations
- Do not invent a public API catalog or webhook list
- Do not quote prices unless they appear on the public site
- Do not crawl or describe `/app` or `/portal` internals as documentation