How ali-elnopy/agency works
ORVIA is an agency-management workspace for staff and clients. The user-facing flow spans sign-in and role-aware workspace views, then brand and client management, content planning and briefs, task execution, and client review. The backend provides authentication and agency data APIs backed by PostgreSQL; the frontend also has browser-local workspace state, which the README says is not yet shared across devices. The graph retains documented product areas, but several frontend/backend connections and unsampled routes are omitted where the excerpts do not establish their wiring.
Main entry points: App.jsx Workspace shell · Sprint3Context.jsx Workflow state · ClientPortalPage.jsx Client portal · api.js API client
Components 30
Web workspace
- Workspace shell
frontend/src/App.jsx - Sign-in view
frontend/src/pages/LoginPage.jsx - Client portal
frontend/src/pages/ClientPortalPage.jsx - Account dashboard
frontend/src/pages/DashboardPage.jsx
Agency management
- Brands state
frontend/src/context/BrandsContext.jsx - Workspace state
frontend/src/context/WorkspaceContext.jsx - Brand management
backend/src/modules/brands/brands.service.js - Team management
backend/src/modules/teams/teams.service.js - User management
backend/src/modules/users/users.controller.js - Dashboard data
backend/src/modules/dashboard/dashboard.service.js
Content workflow
- Workflow state
frontend/src/context/Sprint3Context.jsx - Workflow records
frontend/src/data/sprint3.js - AI brief generation
backend/src/modules/brand-briefs/brand-briefs.service.js - Campaign management
backend/src/modules/campaigns/campaigns.service.js - Content planning
backend/src/modules/content-plans/content-plans.service.js - Content items
backend/src/modules/content-items/content-items.service.js - Task endpoints
backend/src/modules/tasks/tasks.controller.js - Task workflow
backend/src/modules/tasks/tasks.service.js - Social accounts
backend/src/modules/platform-accounts/platform-accounts.service.js
API and persistence
- API client
frontend/src/services/api.js - Workflow API
frontend/src/services/sprint3Api.js - Express API
backend/src/app.js - PostgreSQL
Identity and access
- Auth provider
frontend/src/auth/AuthProvider.jsx - Auth hook
frontend/src/hooks/useAuth.js - Session storage
frontend/src/services/tokenStorage.js - Authentication
backend/src/modules/auth/auth.service.js - Session model
backend/src/modules/auth/auth.model.js
Other components
- Agency staff
- Agency client
Connections 18
- Workspace shell → Sign-in view: renders
frontend/src/App.jsx - Workspace shell → Client portal: renders
frontend/src/App.jsx - Workspace shell → Account dashboard: renders
frontend/src/App.jsx - Workspace shell → Workflow state: provides state
frontend/src/App.jsx - Workspace shell → Brands state: provides state
frontend/src/App.jsx - Workspace shell → Workspace state: provides state
frontend/src/App.jsx - Workspace shell → Session storage: checks session
frontend/src/App.jsx - Auth provider → Auth hook: supplies context
frontend/src/hooks/useAuth.js - Workflow state → Workflow records: uses records
frontend/src/context/Sprint3Context.jsx - Workflow state → API client: calls
frontend/src/context/Sprint3Context.jsx - Workflow state → Workflow API: calls
frontend/src/context/Sprint3Context.jsx - Client portal → Auth hook: reads session
frontend/src/pages/ClientPortalPage.jsx - Client portal → API client: checks mock mode
frontend/src/pages/ClientPortalPage.jsx - API client → Express API: sends API requests
README.md - Authentication → Session model: manages sessions
backend/src/modules/auth/auth.service.js - Task endpoints → Task workflow: dispatches
backend/src/modules/tasks/tasks.controller.js - AI brief generation → PostgreSQL: persists data
- Express API → PostgreSQL: uses database
README.md