Projects and people
There’s no workspace or organization above a project — each project owns its own list of members, and being on one project gives you no access to any other. If you work across several projects, you’re added to each one separately.
Two roles
A project has exactly two roles: owner and editor. The owner of record is whoever created the project, or whoever it’s since been transferred to, and there’s only ever one: only they can delete the project or transfer it. Other members can be owners too — co-owners — made by an invite link that grants Owner or by changing a member’s role. A co-owner holds every other owner control, including revealing and rotating the machine’s credential, inviting people and changing roles. Everyone else is an editor. There’s no read-only or viewer tier: if someone just needs to see something without being a member of the project, share the thing itself (a preview link, for instance) rather than adding them.
Open Project Settings › Members to see the roster, change someone’s role or remove someone. The owner of record’s own row can’t be changed or removed from there — that’s what transfer is for.
Transferring ownership
Only the owner of record can hand the project to someone else, from the same Members page — a co-owner can’t. Pick another member and transfer it to them: they become the owner of record, and you stay on the project as a co-owner. Being the owner of record always moves this way; an invite link that grants Owner makes a co-owner, never the owner of record.
See Inviting people for adding someone to a project, and Signing in for how an invited person gets an account in the first place.