This walkthrough invites someone into a Space, follows their response, and verifies the resulting membership. It is useful when a Space is growing or when a private community is ready to admit another member.
Before You Send An Invite
You need to be the Space owner or have delegated Space-management access. The recipient makes the final decision, so an invitation is not completed membership until they accept it.
Choose the invitation path that matches what you know. Use Find user to invite when the person already has a Visual Space account. Use Send invite by email when you have their email address instead.
For a private root Space, acceptance matters twice: it establishes the person's protected entry and adds the Space to their joined-spaces rail. A nested private Subspace or Activity has a different access workflow for people who already belong to the Space; see Manage Private Area Access. Privacy explains why entry remains separate from authority.
Invite An Existing User
Invite By Email
Review The Invitation
The Invites page keeps sent records visible so a manager can distinguish an unanswered invitation from an accepted membership.
The status list is evidence of the invitation lifecycle, not a substitute for the member list. Members and Invites explains these related states in more detail.
Let The Recipient Respond
Acceptance does not assign a Role. In a private root Space it also supplies the protected root access needed to enter, but it still does not make the person an admin or moderator. The recipient can learn more about their joined state in Membership.
Verify The New Member
Use the settled member list as the verification surface after acceptance; role grouping does not itself prove added authority.
The verified Members workflow supports browsing, searching, Role context, and owner handoff. This guide does not treat that page as a general membership-removal surface.
Common Problems
The person does not appear in search.
Check the query, then send an email invitation if you cannot identify an existing account with confidence.
The email invitation cannot be sent.
Resolve the visible email-format or character-limit feedback. Send becomes available only when the field contains an acceptable address.
The recipient cannot find the Space in their rail.
Confirm that they accepted the invitation rather than declined or merely opened it. Then check whether the invite had expired before acceptance.
The member joined but cannot manage anything.
That is expected unless their ordinary-member baseline or assigned Roles grant additional capabilities. Joined membership, private entry, and authority are separate decisions.
The person needs access only to a private child area.
First confirm that they already belong to the Space, then follow Manage Private Area Access at the exact Subspace or Activity boundary.
Result And Next Steps
The recipient is now either a verified joined member or has declined without joining. The inviter can review the recorded outcome, and accepted members can be found through Members and given only the Roles their responsibilities require.
If the new member will take final responsibility for the whole Space, follow Transfer Space Ownership. Ownership transfer is an explicit owner-only handoff, not an ordinary Role assignment.
