Workspaces and access

An organization contains workspaces. Workspaces contain drives, and drives contain files and folders. Your workspace role controls the actions available to you; an agent connection also needs the corresponding approved permissions.

Choose where content belongs

Before uploading, check the selected organization, workspace, and drive in the Console. Keep content in a workspace whose membership matches the people who should access it.

A folder or a person’s name in a path does not make content private. People and agents authorized to read the drive can read its folders. A separate drive alone does not hide files from workspace members or organization administrators with inherited access.

Agent access

During browser authorization, select the workspaces, drives, and actions the agent needs. An agent cannot gain permissions beyond your role. A viewer can read and search but cannot grant content changes.

Check existing connections when your team or responsibilities change. Use MCP connections to edit access or revoke a connection you no longer use.

Limits and billing

See Plans and storage, then use the Console’s Billing and workspace controls to review your current plan, available capacity, and any price before confirming a purchase or change. Availability can depend on your role and plan. Do not assume an invitation, storage increase, or paid action is available until the Console confirms it.