One-click WordPress admin access from Stretch

What one-click access is

StretchWP sites support single sign-on (SSO) from your StretchSuite workspace. Instead of storing a separate WordPress username and password, you open the site from your workspace and land in the WordPress admin already authenticated. Your Stretch identity and permissions carry through.

This matters for agencies especially: you can manage many client sites without a password manager full of wp-admin logins, and access is governed centrally by your workspace membership rather than by credentials scattered across sites.

How to open your site's admin

1. Sign in to your StretchSuite workspace and confirm you're in the correct organization (top-left workspace switcher).
2. Open StretchWP from your app launcher.
3. Find the site you want in your site list. Confirm its status shows as Ready (a site that is still provisioning may not accept admin sign-in yet).
4. Click Open admin (or the site's admin action).
5. A secure handshake signs you in and opens the WordPress dashboard in a new tab, already logged in.

How it works under the hood

The Dashboard/SSO plugin on the WordPress site establishes a trusted, signed pairing with the Stretch Hub. When you click Open admin, Stretch mints a short-lived, signed authorization that the site verifies before logging you in. Because the trust is between Stretch and the site — not a shared password — access can be granted or revoked centrally, and there's no long-lived credential to leak.

A realistic example

An agency manages six client WordPress sites on StretchWP. A client emails asking for a copy tweak on their About page:

1. The agency staffer opens StretchWP in the workspace.
2. They click Open admin on that client's site and are instantly in wp-admin — no password lookup.
3. They edit the page, publish, and close the tab.
4. When that staffer later leaves the agency and is removed from the workspace, their access to all six sites is gone at once, because it was never tied to per-site passwords.

Troubleshooting

"WordPress login pending" — the SSO pairing between the site and Stretch hasn't finished establishing yet. This is normal right after provisioning. Wait a short while and retry. If it persists, the site's pairing or link record may need to resolve; request help and reference the specific site.

"Open admin" does nothing / opens a login screen — usually a popup blocker or the site being mid-provision. Allow popups for the workspace domain and confirm the site status is Ready.

You get a WordPress login form instead of being signed in — the SSO plugin may be inactive or the pairing broke. Don't try to guess a password; request support so the pairing can be re-established rather than creating a parallel local account.

Wrong site opens — confirm you clicked the right row and that you're in the intended workspace; sites are organization-scoped.

Tips

• Bookmark the workspace, not wp-admin. The whole point is that you enter through Stretch. Bookmarking the raw WordPress login bypasses SSO and asks for a password you may not have.
• Access follows your workspace role. If a teammate needs admin access to a site, add them to the workspace/organization rather than sharing a WordPress password.
• Revoking access is a workspace action. Remove the person from the organization to cut off site access everywhere at once.

FAQ

Do I have a WordPress password at all? You generally don't need one for day-to-day access; SSO handles it. If a genuine local WordPress account is ever required, request it through support.

Is SSO less secure than a password? It's typically more secure — access is centrally controlled, credentials aren't duplicated across sites, and the authorization that logs you in is short-lived and signed.

Can clients log in directly? They can be given workspace access with appropriate permissions, or a scoped WordPress account can be arranged. Prefer workspace-based access so it stays centrally managed.