WeCareRemote platform overview

WeCareRemote is a unified platform that connects refugees with NGOs through AI-powered conversations, collaborative content, and video meetings. Each component is designed to work together under a single login, so you move seamlessly between chatting with an AI assistant, reading published resources, and joining a live video call — without switching tools or re-authenticating. This page walks through each piece of the platform and explains how they fit together. If you are looking for a hands-on introduction, see the Quickstart. If you want to integrate WeCareRemote with your own tools, see the API overview.

​

Architecture at a glance

WeCareRemote is built around a set of cooperating components tied together by a shared authentication layer and connected to two integration services — n8n for automation and NocoDB for structured data: When you log in once on any component, the JWT token issued by getme.global is recognised everywhere else.

​

Technical diagram

The diagram below shows how a request flows through the system and where every component sits relative to the others.

​

How to read this diagram

• Solid arrows are synchronous HTTP calls made by the component at the tail of the arrow.
• Dashed arrows are asynchronous events — webhooks fired by the platform, or optional knowledge-base reads by the AI assistant.
• JWT verification is the small back-and-forth between every component and getme.global on the left. Every protected request flows through it.
• n8n sits in the middle as the event hub. It receives webhooks from the platform, calls back into the AI agent and recordings APIs, and pushes structured rows into NocoDB.
• NocoDB is read by two clients: NGO staff (via the spreadsheet UI) and n8n (via the xc-token-authenticated REST API). The AI assistant can optionally read NocoDB rows as a knowledge source.

​

Trust boundaries

• The platform, the blog, and getme.global share the JWT trust boundary — a token issued by getme.global is honoured by all of them.
• n8n is outside the JWT trust boundary on its inbound side: it authenticates webhook callers however you configure (webhook secret, IP allowlist), then uses a stored JWT to call WeCareRemote on the outbound side.
• NocoDB is a separate trust boundary — it uses its own xc-token API tokens and does not understand WeCareRemote JWTs.

​

AI assistant

The AI assistant is the primary way refugees interact with the platform. You can ask it questions, request information about available services, or get help navigating the support process. The assistant maintains conversation memory across sessions, so it builds on previous exchanges rather than starting fresh each time. When relevant documents or knowledge bases are available to your organization, the assistant can retrieve and reference that content directly in its responses — reducing the need for back-and-forth with staff. What the assistant can do:

• Answer questions in plain language about services, processes, and resources
• Retain context across messages and sessions
• Surface knowledge-base content when your organization has connected it
• Adapt its tone and the level of detail based on your role (refugee user vs. NGO admin)

​

Blog and content

The blog gives NGO administrators a space to publish resources, announcements, and guides that are visible to refugee users on the platform. It is built on WordPress and uses role-based access to control who can read, write, and manage content.

• NGO administrators (org_admin) can create, edit, and publish posts.
• Refugee users (blog) can read published content relevant to their situation.
• Logged-out visitors see only the public portion of the blog.

This separation ensures that the content refugee users see is curated and appropriate, while giving NGO staff full editorial control. Menu items and post visibility can be configured per role using the WeCareRemote WordPress plugin — see Role-based access for the full visibility rules.

​

Video conferencing

When a conversation needs to move beyond text, WeCareRemote includes integrated video meetings powered by Jitsi. Refugees and NGO staff can join a meeting directly from the platform — no third-party account or software download required. Meetings can be recorded, which is useful for documentation, case follow-up, or sharing session summaries with other team members. Recordings are stored in secure cloud storage and accessible through the recordings API or the platform UI.

​

Authentication

A single JWT-based authentication layer ties all of WeCareRemote’s components together. When you log in through the platform, your session token is recognized by the AI assistant, the WordPress blog, and the video conferencing system — so you never need to log in separately to access each feature. Your role (blog or org_admin) is encoded in your token and determines what actions you can take across the platform. If your role changes — for example, if an NGO grants you additional permissions — you will need to log out and back in to pick up the updated access. For full details on how authentication works, including how to obtain and verify a token programmatically, see the Authentication overview and the JWT auth reference.

​

A typical session

To make the pieces concrete, here is what a typical refugee user’s session might look like:

​

Where to go next