Private REC Workspace

REC Command Center

A focused home for REC tools, integration planning and operational visibility.

Concept mode · No live integrations

Ripple Effect Connections

One place to see the systems behind the work.

This concept brings REC's key platforms into one clean command center so Dr. Tory Brooks, D.C. and MeChelle can see what each system is for, what is ready, and what still needs to happen before anything is connected for real.

“Every step ordered. Every connection intentional.”
Systems in view
3

Connect United, Operly and R-Link Studio.

Live integrations
0

This remains a review-only concept.

Readiness checks
0 / 15

REC Systems

Each system has a defined role. Open a workspace to review its purpose and requirements.

Connection Network

Connect United

REC's relationship and connection layer in the current concept.

Not connected
Operations

Operly

Internal tasks, projects, notes and operational work for REC.

Not connected
Studio & Partner Tools

R-Link Studio

Asset, partner-link and white-label tooling in the current REC concept.

Not connected

What this dashboard is for

A private decision and operations layer, not another public-facing page.

Keep REC's systems visible without making the experience feel technical.
Show what each platform is responsible for and what remains disconnected.
Give REC one consistent place to review integration readiness.

What this dashboard does not do yet

No pretend integrations or misleading live-data displays.

No customer, contact or financial data is loaded.
No provider credentials or API keys are stored here.
No button on this concept sends data to an outside system.

System 01 · Connection Network

Connect United

A relationship and connector layer in REC's current working concept.

Role inside REC

Organize REC's connection activity in one place.
Make relationship pathways easier to see and follow.
Support REC's connection-focused operating model.

These are working assumptions from the current concept and are not claims about verified product capabilities.

Integration readiness

5 requirements before any real connection.

0 / 5

System 02 · Operations

Operly

The internal operating layer for REC tasks, projects, notes and organized execution.

Role inside REC

Keep REC projects and next actions organized.
Keep notes and working documents close to the work they support.
Provide a day-to-day operational workspace.

The exact feature set and integration options still need to be confirmed against Operly's current product terms.

Integration readiness

5 requirements before any real connection.

0 / 5

System 03 · Studio & Partner Tools

R-Link Studio

The studio, asset and partner-tooling layer in REC's current concept.

Role inside REC

Support REC assets and partner-facing materials.
Organize affiliate or referral link tooling where appropriate.
Support approved white-label presentation needs.

Affiliate, white-label and integration terms should be confirmed in writing before REC relies on them.

Integration readiness

5 requirements before any real connection.

0 / 5

Integration Readiness

Make the dashboard real

A practical sequence for moving from concept to approved, secure integration.

Overall readiness

Checklist progress is saved only in this browser.

0 / 15 complete
01
Confirm each system's role

Decide exactly what REC wants visible, and who should see it.

Tory & MeChelle
02
Request official access

Get API, export or integration permissions in writing from each provider.

Tory
03
Define data and permissions

Agree what data moves, who can see it and how it is protected.

REC + counsel
04
Build server-side connections

Keep all credentials out of Squarespace and in a secure backend.

Developer
05
Test before launch

Use non-production data first, verify permissions, then approve the live rollout.

REC + Developer