Connect PAUIOps Center

1. Open the PAUIOps Center registration page.
2. Create your account and choose a plan.
3. Complete the subscription flow.
4. Open your hosted Center workspace in the browser; PAUIOps runs and maintains the Center service.

1. Install PAUIOps Manager on the destination server.
2. Publish its API through HTTPS and its WebSocket endpoint through wss://.
3. Allow the exact hosted Center origin in PAUIOPS_ALLOWED_ORIGINS.
4. Confirm Manager health and sign-in before adding it to Center.

1. Sign in to a registered Manager with an administrator account.
2. Open Settings > Server Registry. Center forwards that active Manager session for server-side role verification; there is no second frontend-secret unlock.
3. Add the server name, environment, location, and API URL. Center derives ws:// or wss:// until you deliberately edit the WebSocket URL.
4. Test the connection, then set its enabled state, environment default, and display order.
5. Sign in to that Manager when Center prompts for a server-specific session.

API URL:       https://<manager-api-domain>
WebSocket URL: wss://<manager-api-domain>

1. Start Add Project with the Git repository URL.
2. Review the derived project name and contained clone destination.
3. Choose a branch discovered from the remote; retry the probe or use manual entry only when discovery cannot complete.
4. Submit only after branch discovery settles. Manager revalidates the remote, destination, branch, checkout result, conflicts, and active branch.
5. When editing, choose from remote branches while the existing clone destination remains read-only.

A repository cloned with a narrow single-branch refspec can use Fetch all branches from the branch switcher before selecting another remote branch.

The Center login form offers a server selector when several Managers are registered, so an unavailable default server does not block access to another reachable destination. Switching to a Manager without a live session still requires that Manager’s own login.

When a signed-in user deliberately changes their password, Center can propagate that new password to other Managers where the same user already has a live server-specific bearer session. Each destination uses its own identity and token; partial failures are reported per server.

Each enabled Manager registered in Center counts toward subscription capacity. Disabled or removed destinations should be reviewed before replacing a server, and a plan upgrade is required before enabling a Manager beyond the current limit.

Use Center account billing when you need to move between the 2-server, 5-server, and Unlimited plans.