Sharing & Access Control

Roles

vibe-coded.ai uses a role-based permission system with four levels:

Role	Can do
Owner	Everything. Delete the vibe, manage billing, transfer ownership.
Admin	Manage access, modify settings, plus all Writer permissions.
Writer	Create, edit, and delete data. Use the vibe's tools and API.
Viewer	Read-only access. Can see data but not modify it.

Each role inherits all permissions from the roles below it. An Admin can do everything a Writer and Viewer can do, plus manage access.

Sharing with people

To share a vibe with someone:

1. Go to your account dashboard
2. Find the vibe you want to share and click Share
3. Enter the person's email address
4. Choose a role (Viewer, Writer, or Admin)
5. Click Grant Access

The person will need a vibe-coded.ai account with that email address. If they don't have one yet, they'll be able to access the vibe after signing up.

Sharing with AI clients

When an AI client connects to your vibe via MCP, it authenticates through OAuth. The permissions it gets depend on the OAuth scopes you approve:

• mcp:read — Equivalent to Viewer access for MCP tools
• mcp:write — Equivalent to Writer access for MCP tools
• mcp:admin — Equivalent to Admin access for MCP tools

See OAuth for MCP for the full authentication flow.

Public vs private vibes

By default, vibes are private — only you and explicitly granted collaborators can access them.

Public vibes are accessible to anyone with the URL. MCP tools on public vibes can be used without OAuth authentication, making them easy to share but less controlled.

Managing collaborators

From the Share dialog on your account dashboard, you can:

• View all collaborators and their current roles
• Revoke access by clicking the remove button next to a collaborator

Revoking access takes effect immediately. The person will lose access to the vibe's data and tools on their next request.