I need operator tools
You want tenant settings, bundle publishing, or platform-side verification.
Expected result: You should land in Rights Editor or the operator control surface.
This page is the easy-button version for operators. It tells you where to log in, which system to use for which job, and what to do first without making you parse the full platform vocabulary.
This is a lightweight decision tree. Pick the path that matches your job, then use the destination and expected outcome to verify you are in the right system.
You want tenant settings, bundle publishing, or platform-side verification.
Expected result: You should land in Rights Editor or the operator control surface.
You need the site's native dashboard, plugin upload, or content administration.
Expected result: You should land on the native WordPress login page.
You are updating the tenant bundle or checking the manifest that WordPress should install.
Expected result: You should be able to save settings, refresh the bundle card, and open the manifest.
You need to confirm the alias and canonical domains are sending people to the correct system.
Expected result: Alias routes should go to Rights Editor; canonical WordPress login should stay native.
Go to peterbstories.social-fabric.us for Rights Editor and tenant operations. Go to peterbstories.com only for the public site and native WordPress administration.
Use this page when you need the operator path for Peter B Stories. The public website lives on its own WordPress host, while Social Fabric provides the operator entry and plugin publishing tools.
There are two different login destinations here. Use the Social Fabric alias for operator work. Use the WordPress login only for the tenant's own website admin.
If you are onboarding or updating this tenant, start with the shortest successful path. Publish the current bundle, confirm settings, then verify login behavior on both domains.
These details matter when you need the deeper implementation record. Most operators can ignore this until they are troubleshooting config ownership, governance, or documentation sync.