How does workspace sharing affect privacy?

Every account has a personal space and may belong to one or more workspaces. The active context is shown in the top bar — switch it to change which space new projects are created in and which existing projects are visible. Personal projects stay private to your user account; only you can read or edit them. Workspace projects belong to the workspace and are visible to other members by default.

When you create a project, double-check the active context in the top bar. A project created in a workspace cannot be quietly moved to your personal space later without the workspace admin's involvement. If you need a private draft of work-related material, create it in personal first, then move or share it into the workspace when ready.

Workspace owners and admins can see every project, generation, and credit-spend row in the workspace. They pay the bill and need full visibility for billing reconciliation, audit, and member management. Regular members see the projects they create plus any explicitly shared with them at the project level. Member-level credit usage is visible to admins for the same billing reason — there is no per-member private spend log.

Project-level sharing inside a workspace lets a creator restrict a specific project to a subset of members rather than the whole workspace. Use this for sensitive client work or pre-launch material. Open the project, click Share in the top bar, and pick the members who should have access. Owners and admins still see the project regardless — there is no way to hide a workspace project from an admin.

Inside a project, the Share button in the top bar controls visibility. Options: workspace-wide (default for new workspace projects), project-level invite (specific members only), link-only (anyone with the URL can view, useful for client review), and personal-private (only you, applies to personal-space projects). Each option is reversible — turn sharing off and the link or invite stops working immediately.

Moving a project between contexts requires a duplicate-and-delete pattern. Open the project, choose Duplicate, switch to the target context (personal or another workspace), and paste. Delete the original after confirming the duplicate is intact. Workspace admins can move projects between members of the same workspace via the workspace project settings.

Removing a member from a workspace revokes their access to workspace projects immediately. They lose read and edit access on every workspace project, including projects they created. The projects themselves stay in the workspace — generations, uploads, prompts, and history remain accessible to remaining members and admins. The removed member's personal-space projects and personal wallet credits are unaffected.

A workspace owner change transfers billing responsibility and admin permissions to the new owner. The old owner becomes a regular admin (or is removed entirely, depending on the choice). Project visibility for non-owner members does not change during an owner transfer.