Clear entrance. Private pipeline.

This host keeps the operator workspace off the public root. Use the public pages to choose the right WordPress access point, sign in with your existing permissions, and continue into the protected course publishing app.

Public root Explains the route clearly.

WordPress SSO Uses existing staff permissions.

Protected app Uploads and publishing stay private.

Open Operator Login Enter Protected App

Public pages stay readable while the working pipeline remains behind authentication.
Operators choose the correct WordPress source before entering the app.
The protected production workflow continues inside /app.

Access flow

What happens next

This public surface is only the handoff layer. WordPress authenticates the session, then the protected app takes over.

Choose the right site Use the WordPress source that owns your pipeline permissions.

Sign in once WordPress attaches the operator session and returns you to the pipeline.

Work inside the app Uploads, preflight, lessons, and publishing stay inside the protected shell.

Staff-only surface Only authenticated WordPress administrators and approved operators should continue into the publishing workspace.

Review the public entry

Confirm the correct host and understand the route split before opening the operator workflow.

Authenticate with WordPress

Use the site that manages your permissions. The pipeline does not ask for a separate password here.

Continue into /app

The protected app keeps uploads, readiness checks, lesson building, and publishing away from the public root.

Available routes

Open the right destination

Website links stay public. Operator access continues through WordPress SSO and returns into /app.

https://newsite.somislamic.com//login?return_to=%2Fapp