Accounts
Understand personal identities, organizational workspaces, third-party connections, and enterprise multi-tenant isolation.
In MuseCanto, User Accounts and Workspaces follow strict multi-tenant isolation principles. Whether you are a solo content creator or an enterprise editorial team collaborating across departments, grasping these boundaries ensures smooth asset management.
Core Hierarchy Architecture
User Account ── Bound to personal Email / Google / GitHub
│
├── Personal Workspace ── Private topics, articles, and drafts
│
└── Organization Workspace ── Team collaboration, shared knowledge bases
├── Role: Owner
├── Role: Admin
└── Role: MemberIdentity & Auth
A single email/credential represents a globally unique user. Supports email/password, Google OAuth, and passwordless login.
Physical Data Isolation
All documents, calendar topics, and schedules belong to a specific workspace. Data across workspaces is strictly isolated.
Workspace Types & Context Switching
Switch contexts instantly using the Workspace Switcher in the top-left corner:
| Dimension | Personal Workspace | Organization Workspace |
|---|---|---|
| Creation | Automatically generated upon sign-up | Created on-demand by users |
| Collaboration | Single-user read/write, no invites | Multi-member collaboration with fine-grained RBAC |
| Billing & Quota | Independent plan (Free / Pro) | Calculated by team seats and shared Team allowances |
| Content Assets | Private library, personal editorial calendar | Public organizational asset library, team matrix distribution |
Switching workspaces does not move data
Changing active workspaces only alters your current view context. It never moves, merges, or deletes existing topics or documents.
Third-Party Connections & Credential Ownership
Social accounts connected under Settings → Integrations (e.g. X / publishing accounts):
- Owned by the individual user: Connections are OAuth authorizations tied to your user identity. Other team members cannot export your access tokens or inspect your connections via MCP.
- Granular target selection: During multi-account publishing, creators can only select accounts authorized by themselves or explicitly shared by workspace administrators.
MCP Cross-Workspace Authorization Scope
When you complete an MCP OAuth authorization in Cursor, Claude Code, or Windsurf:
- Single authorization, smart routing: Your authorization token automatically encompasses all workspaces where you have membership.
- Real-time permission enforcement: If you are removed from an organization, subsequent AI client calls targeting that organization immediately receive
403 Forbidden. - No quota leakage: Write privileges earned within a Pro organization do not spill over to upgrade your personal Free workspace.
For further details, see Member Permissions and MCP Authorization.