Dark mode only

Dashboard

Welcome back! Here's your workspace overview.

Total Content
0
↑ 12% this month
Active Tasks
0
0 completed
Scheduled
0
Posts this week
Projects
0
0 active
Recent Activity

No recent activity

Upcoming Deadlines

No upcoming deadlines

Content Pipeline

No content in pipeline

Quick Actions
Create Task
Add a new to-do item
New Content
Plan a new piece of content
📝
New Note
Capture research or ideas
📁
New Project
Start a new project
📅
Schedule Post
Plan your content calendar

Content Hub

Plan, create, and manage all your content.

All
📝 Blog
🎬 Video
🎙️ Podcast
📱 Social
📧 Newsletter
🎞️ Reel

Content Calendar

Visual overview of your content schedule.

Select a date

Click a date to see scheduled items

Post Scheduler

Schedule and manage your social media posts.

Scheduled Posts
Title Platform Date Time Status Actions

Task Manager

Kanban-style task tracking for your team.

Projects

Track progress on your media projects.

Notes & Research

Your knowledge base — like Notion for your team.

All
📌 Pinned
Strategy
Research
Branding
Ideas

Asset Manager

Store links, references, and media assets.

Name Type Link Tags Added Actions

Analytics

Track your content performance and engagement.

Overview
Content
Engagement
Total Views
0
Engagement
0%
YouTube Feed Items
0
Posts Published
0
This month
Content Performance
Platform Breakdown

Settings

Configure your workspace.

Appearance
Dark mode is enforced for this workspace.
Data
Currently using: MongoDB Atlas via API proxy

Sync runs through your own API proxy, which talks to MongoDB Atlas from the server side.

About

Vichar Media Workspace v2.0.0

A streamlined workspace for media and podcast management.

Features: Content Pipeline, Task Management, Notes, Calendar, Projects, Assets.

MongoDB Atlas Setup

How database sync works now:

  1. Frontend loads the latest snapshot from /api/bootstrap
  2. All writes go to your own /api/* proxy
  3. The proxy talks to MongoDB Atlas on the server side
  4. No MongoDB credentials live in the browser
  5. Browser CORS is no longer the problem

This removes the browser CORS error completely.