Set up a managed SSO site

A managed BlockNinja site is provisioned before you enter its CMS. Start in the BlockNinja account portal, choose the intended site, and let SSO apply your assigned access.

Managed sites do not use the standalone Welcome, Admin Account, Site Settings, or Sample Content wizard. If you see BlockNinja Setup, stop and confirm that you opened the correct site.

Before you begin

• Accept the invitation to the correct BlockNinja account if one was sent.
• Know the managed site name and the role you were assigned.
• Use your own portal account. Never borrow or share another person's login.
• Save unfinished work before launching a different site.

Understand the managed path

Site settings and content are reviewed through the normal CMS after sign-in, not through a separate managed setup wizard.

Find the intended site

1. Sign in to the BlockNinja account portal.
2. On Dashboard, find the intended card under Sites.
3. If the card is not in the recent list, open Sites from the workspace navigation.
4. Check the site name and status before continuing.

An Online site is ready to launch. Provisioning, stopped, or error states must be handled through the portal before repeated sign-in attempts.

Launch the CMS through SSO

1. Select Launch on the intended site.
2. BlockNinja opens a new tab and completes the secure handoff.
3. Confirm the new tab lands on the CMS Dashboard.

Do not copy, share, or bookmark the temporary handoff address. Bookmark the account portal or the final CMS address instead.

Understand your mapped role

Confirm access by the permitted controls you can use. A missing restricted action is not, by itself, a sign-in failure.

Confirm the signed-in account

1. Open Account in the admin header or Account > Profile.
2. Confirm the signed-in person without recording personal details in evidence.
3. If the role is not what you expect, stop before making changes and ask the site owner to check portal membership.

Do not create an emergency local account to work around a managed role mismatch.

Continue ordinary site setup

An Admin or Superadmin can now review the site through normal destinations:

• Settings > Site Settings for the title, description, and public domain.
• Content > Pages for provisioned or starter content.
• Settings > Theme for the active visual system.
• Administration > Users to understand local access, while managed membership remains owned by the account portal.

A Viewer should inspect only the information their role permits. Request the smallest additional role needed for an assigned task.

Verify the first sign-in

• Launch opened the intended site, not another site on the account.
• The CMS Dashboard appeared without a setup wizard.
• The account and permitted controls match the assigned role.
• No token, personal data, site domain, billing detail, or identifier was captured.
• Desktop and narrow layouts contain no inaccessible controls or horizontal overflow.

Fix launch and access problems

When escalating, send the site name, expected role, safe timestamp, and visible error. Never send the handoff address, credentials, personal data, or an identifier.

Finish safely

• Close the CMS tab or use Account to sign out when the session is complete.
• Return to the portal before launching another managed site.
• Read Sign in and tour the admin for the CMS navigation journey.
• Read Roles and access at a glance before requesting or granting more access.