Accounts and collaboration questions

Do I need an account?

Yes for the current signed-in project and collaboration workflow. A local profile is also part of how the desktop app resolves projects for MCP. Account installation, login, and recovery still need packaged-app runtime verification before this page is approved.

How do I share a project?

From the Dashboard, open the project's menu, choose Invite User, and enter the email of an existing Misaki Studio account. The invited person sees the project through the invitation flow.

Use the collaboration workflow.

Can I invite someone who has not signed up?

No in the current flow. The invitation action expects an existing account; otherwise the UI reports that the profile was not found.

Are there granular editor/viewer or per-file roles?

Do not assume them. Current public behavior is documented as project-level invited access, and this rewrite does not claim a supported per-person role matrix or per-file permissions.

Can the owner remove a collaborator?

Yes. The owner can remove an invited user through the project or user-management surface. The invited collaborator can leave a project through their own project menu.

Removing access changes future access; it does not erase already synchronized edits.

Can two people edit at the same time?

Project state can receive connected edits, but simultaneous structural work on the same file is risky. Assign a clear file or feature owner, reread before writes, and review incoming/local differences before sharing a milestone.

How do we review and synchronize changes?

Use the desktop Sync Changes workspace to refresh incoming work, inspect file and nested differences, resolve incoming changes, review outgoing work, and then push with a meaningful message. This is different from file-content Undo and from Git/local export.

Review sync and history.

Does the activity indicator show who changed something?

No. MCP activity marks identify recently read or changed files/elements in the local editor session and remain until explicitly cleared. They are session-only navigation aids, not collaborator identity, authorship, history, or approval evidence.

Does each collaborator get their own agent identity?

No. An MCP agent connects through that collaborator's trusted running desktop app and selected project. The agent is not added as a separate project member.

Can an agent invite, remove, or leave on behalf of a collaborator?

No production MCP route is documented for those account actions. Perform them in the Dashboard and verify the exact project and email before confirming.

Can I recover work after a sync mistake?

Sometimes. Project history can be inspected, copied beside the live file, or restored into live content as a new outgoing change. Exact conflict and undo behavior still needs runtime verification, so prefer copying a historical version when you are unsure.

Use the history recovery model.