Overview
One dashboard for the REC stack
Connect United, Operly and R-Link Studio shown as a single integrated workspace for Dr. Tory Brooks and MeChelle. Choose a service to see its current connection state and what it would take to connect it for real.
All services: demo — disconnected
Services in scope
3
Connect United · Operly · R-Link Studio
Live connections
0
DemoNothing is connected in this build
Setup checks tracked
15
5 per service — see the checklist
Contacts synced
—
SampleNo records exist in this demo
Choose a service
Each tile opens that service's panel. Nothing on this page connects, submits or sends.
Next-step workflow
The order REC would work through to turn this concept into a real, connected dashboard.
-
Confirm the service and the scope
Agree exactly what REC wants visible, and for whom.
-
Request official API access
Ask each provider in writing for API or integration access to REC's own account.
-
Agree data fields and consent
Decide which fields sync, who can see them, and what consent and privacy terms apply.
-
Build the secure server-side connection
Credentials live server-side only. Nothing secret is ever placed in a web page.
-
Test in staging, then enable
Verify with non-production data before switching anything on for REC.
Why this build stops here
A front-end concept can show the shape of the dashboard, but it cannot create an integration. Single sign-on and data synchronisation require provider authorisation, a backend that holds secrets safely, and legal and privacy review. Anything that claims otherwise would be a mock-up pretending to be a product.
Service 01 · Community & connector network
Connect United
The community and connector layer in REC's working plan. In this concept it is one tile of the integrated dashboard — shown so REC can review the shape of the experience.
Demo — not connected
Intended role in the stack
- Hold REC's community and connection activity in one place.
- Surface the connector relationships REC already tracks by hand.
- Give MeChelle one view of who REC is connected to, and why.
These are REC's working assumptions about the role, not verified product capabilities. Confirm current features, plans and program terms against Connect United's own documentation before building, quoting or promising anything.
What it would take to connect
Connection status: demo — disconnected
No request was sent and nothing was connected. A real connection to Connect United would require official API access from the provider, written authorisation for REC's account, an agreed data and consent model, and a secure server-side service to hold credentials and sync data. None of that is part of this demo.
Service 02 · Workspace & agent operations
Operly
REC's internal workspace — tasks, notes, documents and agent work. This concept shows how it would sit alongside the other two services in one dashboard.
Demo — not connected
Intended role in the stack
- Tasks, projects and follow-ups for REC work in one place.
- Documents, notes and research kept alongside the work they belong to.
- The operating layer MeChelle uses day to day.
Working assumptions only. Confirm the current feature set, plan limits and data-handling terms with Operly before relying on any of it for REC's operations.
What it would take to connect
Connection status: demo — disconnected
No request was sent and nothing was connected. A real connection to Operly would require workspace authorisation, documented API or export access, an agreed field mapping and permission model, and a secure server-side service to hold credentials. None of that is part of this demo.
Service 03 · Studio, affiliate & white-label tooling
R-Link Studio
The studio and partner-tooling layer in REC's working plan. Represented here as a tile only, so REC can see how it would appear next to the other services.
Demo — not connected
Intended role in the stack
- Studio and asset work for REC content and partner materials.
- Partner, affiliate and referral link tooling.
- White-label presentation of REC's services.
Affiliate, white-label and program terms are unverified. Review the current terms in writing and take qualified advice before committing REC to anything or representing a benefit to anyone.
What it would take to connect
Connection status: demo — disconnected
No request was sent and nothing was connected. A real connection to R-Link Studio would require documented API or embed scope, confirmed brand and asset permissions, reviewed affiliate and white-label terms, and a secure server-side service to hold credentials. None of that is part of this demo.
Readiness
Integration checklist
Every check REC would clear before a service goes live. Tick them off as they are genuinely completed — this is a working list for the review, not evidence that anything has been done.
15 checks · 0 complete
Connect United
0 / 5Operly
0 / 5R-Link Studio
0 / 5Progress is stored in this browser only, so REC can come back to the review. Clearing site data or opening the page elsewhere resets it. No account is required and nothing leaves the page.
Readiness
Make it real
What has to happen before this concept becomes a connected dashboard. Nothing below has been started or approved — it is the sequence REC would need to work through.
-
Tory & MeChelle
Confirm the service and the scope
Decide exactly what REC wants visible in the dashboard, and who should see it.
-
Tory
Request official API or integration access
Ask each provider in writing for access to REC's own account, and keep the written terms.
-
Tory, MeChelle & counsel
Agree data fields, consent and privacy
Which fields sync, who can see them, how long they are kept, and what consent covers it.
-
Tory, MeChelle & CPA
Review program, pricing and contract terms
Confirm current terms in writing, and check any tax or business question with REC's CPA.
-
Developer
Build the secure server-side connection
A backend service holds credentials and performs the sync. No secret ever enters the web page.
-
Developer & MeChelle
Test in staging with non-production data
Prove the connection and the permissions before anything touches real REC information.
-
Tory & MeChelle
Review, then enable for REC
A final read-through together, then switch on. Keep it review-only until this point.
About this code
This whole block is self-contained. index.html in the same folder is the standalone version of
the same dashboard, and README.md explains where each piece goes, how to preview it, and what
has to be true before any of it can connect to a real service.