Products & tools
The staff workspace behind the care experience. Bring program coordination, content, and review into the work your team is already doing.
Who it is for
Frontline staff, care managers, educators, and program leaders have different responsibilities. The Partner Portal provides workspaces for the modules their organization uses, with access appropriate to their role and program.
Some teams begin with content and community coordination. A day-center team may also need intake, reservations, attendance, activity capture, family communication, and closeout. The aim is to connect these pieces without assuming every organization works in the same way.
The components
Care-management and Community Sense workspaces help authorized staff find a participant and review intake, preferences, and relevant support information. Care Cues bring recorded points from the staff profile into view; staff can return to the source before drawing a conclusion.
Day-center teams manage enrollment and reservations in the context of a site, program, and service date. The expected roster supports preparation, while staff still need to confirm who arrives and what has changed.
Staff record arrival, attendance, activities, and relevant observations through Community Sense. Day review and closeout help reconcile the recorded day and identify work to carry into a handoff or the next visit.
The portal is also where teams prepare tiles and pathways, manage wall content, and use the human-led coaching console. Operational work and participant experiences can draw on the same prepared resources.
Staff review family-facing summaries before preparing a PDF or using an enabled Care App delivery workflow. The recipient and channel matter. A family report is not a copy of every internal note, and digital delivery is not enabled in every deployment.
Teams can review available participation, feedback, usage, and operational information. The useful question is what needs a closer look: an incomplete handoff, a missed activity, or a resource people are not finding.
Authorized administrators manage staff accounts, roles, and access to configured workspaces. Team activity and communication tools support coordination without giving every staff member the same responsibilities or access to every record.
Training, help sheets, and reviewed learning resources help staff understand workflows and prepare for the work. Some education experiences are previews or pilots and should retain those labels. Completing a module is not, on its own, evidence of competency.
In practice
An illustrative day-center workflow. The exact modules, responsibilities, and sharing arrangements are agreed with the program.
Staff review the day's roster and reservations, confirm the participant, and record arrival or attendance through the supported workflow.
During the day, staff record relevant activities and observations. Prepared resources or a Mingle session can support participation; the team adds the context software cannot observe on its own.
At closeout, staff consider the day's information, review a family-facing draft where available, and decide what is appropriate to share or carry into a handoff. Open questions remain visible for follow-up.
How it connects
The portal prepares and coordinates; the Care App and Care Wall provide participant and family experiences. Content and Mingle connect education and activities to the program. Connections to another organization's systems require a defined purpose, permissions, and technical scope.
Where AI helps
The Portal Companion can assist with guidance, supported drafts, and proposals for specific actions. In day-center workflows, this can include an attendance or activity action for the selected participant. A proposal needs review and approval before the supported change is carried out.
Day-in-review and family-summary assistance works from the information supplied by the workflow. It can help staff organize that information, but it must not add events or personal facts that were never recorded. Staff remain responsible for checking the source, context, and wording.
What to confirm
Modules, staff roles, reporting, AI assistance, and system connections depend on the configured deployment. We should confirm which steps are available, which need configuration, and which involve further work. A preview or proposed capability should be identified as such.
Reports are only as complete as the information behind them. Participation and feedback may help identify a question or an opportunity to improve support; they do not establish that genusConnect caused a clinical outcome or that a program meets a funding or regulatory requirement.
