# Members and roles Who is in your workspace, what each role can do, and what happens to someone's plans when they leave. Everyone in your workspace holds one of three roles. | Role | Can do | | ---------------- | ------------------------------------------------------------------------------------------------------------ | | **Owner** | Everything a member can, plus billing, members, company instructions, skills and formats, and the audit log. | | **Member** | Plan, write Specs, connect an issue tracker, and set anything at project level. | | **Comment-only** | Read and comment. Never edits a plan. | ## Your access is the lower of two things [#your-access-is-the-lower-of-two-things] Access to a particular plan is the **lower** of your workspace role and your role on that plan. The consequence worth knowing: giving a Comment-only teammate editor access on a plan does not make them an editor, because their workspace role is the ceiling. Plansmith refuses that grant outright rather than accepting it and quietly doing nothing. See [Sharing a plan](/docs/sharing-a-plan) for the per-plan side of this. ## Inviting people [#inviting-people] Owners invite by email from **Settings → Members**, choosing the role on the way in. An invite is the only way into a workspace; there is no domain-based auto-join. ## When someone leaves [#when-someone-leaves] Removing a member hands their plans to another owner in the same step, so nothing is left without an owner. You pick the successor as part of the removal. To find what needs re-homing first, **Settings → All plans** lists every plan in the workspace with its name, owner and visibility. That view is owner-only and deliberately shows those three things only: it exists so an owner can administer plans they cannot open, not to give them a way to read private ones. Plans are private until you share them. Your plan, what usage means, and how to add more.