If someone needs to review indexing, coverage issues, or search performance, give them access directly in Search Console instead of passing one main login around. The clean setup is property-level access with the smallest role that still lets them do the work.
According to Google, only a property owner can add or remove users. Search Console also distinguishes between owners, full users, and restricted users, so it is worth choosing the role intentionally instead of defaulting to ownership.
Step by step
- Open the correct property in Google Search Console.
- Open Settings and go to Users and permissions.
- Click Add user.
- Enter the Google Account email of the person you want to add.
- Choose the role and save the change.
Which role usually makes sense
- Use Full user when someone needs to inspect performance and indexing in a meaningful way.
- Use Restricted user if they only need a light read-only view.
- Use owner access only when they genuinely need user administration or ownership-level actions.
Google also notes that users must have a valid Google Account, and email groups cannot be added as users. If someone should not be a user any more, remove the access in the same Users and permissions screen.
Practical rule: keep verified ownership on the client side, add delegated access only where it is needed, and treat Search Console as a property-specific tool rather than a shared team inbox.
If you need similar instructions for the rest of the stack, open the Sharing Access hub.
