Give an existing WordPress network user access to another subsite by assigning a role on that site. Multisite shares user identities across the network, while each site's membership and role determine what that person can do there.
IN THIS ARTICLE
01 Choose the correct person and role
Confirm the person's existing username or email and the specific subsite they should access. Decide whether they need to contribute drafts, publish content, manage other authors or administer the site. Do not grant Super Admin merely to solve a subsite access problem, because that role controls the entire network.
02 Add the existing account
- Sign in with permission to manage membership for the intended subsite.
- Open the subsite's Users screen, or use the Users tab when editing that site in Network Admin.
- Choose the existing-user option and identify the approved network account.
- Select the site's appropriate role and complete any invitation or confirmation workflow shown.
- Ask the user to sign in and verify that the site appears in their available sites with the intended permissions.
Does this create another password?
No. The existing network identity is reused. Creating a duplicate account just to reach another site complicates ownership and access reviews. Password changes to the shared account affect that identity across the network, so account recovery should be coordinated with the actual user.
Why can the user log in but not edit this site?
A network account can exist without membership on a particular subsite. Check the membership and role on the target site, not only the network user list. Plugins may also add capability checks or approval requirements, so test the actual task after assigning the standard role.
03 Remove access at the right scope
When the person finishes work on one subsite, remove that site's membership or reduce its role as appropriate. Do not delete the network user without checking their access and authored content on other sites. Review application passwords and external access separately when ending the whole relationship.
04 Verify the handoff
Use a representative action, such as creating a draft or editing an assigned page, to confirm the role meets the need. Avoid asking the user to send their password as proof. Record who approved the access and schedule a review for temporary collaborators. Site administration and network administration are distinct responsibilities even though they share the same login system.