Guide
Manage organizations, projects, and domains
Keep administrative actions in the correct organization, project, and verified website context.
Last reviewed September 12, 2026
Administration overview
SiteWall administration is organized around organizations, projects, monitored domains, team access, account and project settings, and in-app notifications. Always establish the active organization and project before making a change because operational records and controls are project-scoped.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Organization | Confirm the active organization and project, the person or team accountable for the change, and the role required to perform it. Verify the resulting access or ownership state from a second authorized context when practical. |
| Projects | Confirm the active organization and project, the person or team accountable for the change, and the role required to perform it. Verify the resulting access or ownership state from a second authorized context when practical. |
| Team | Confirm the active organization and project, the person or team accountable for the change, and the role required to perform it. Verify the resulting access or ownership state from a second authorized context when practical. |
| Access | Confirm the active organization and project, the person or team accountable for the change, and the role required to perform it. Verify the resulting access or ownership state from a second authorized context when practical. |
| Settings | Confirm the active organization and project, the person or team accountable for the change, and the role required to perform it. Verify the resulting access or ownership state from a second authorized context when practical. |
Organizations and projects
An organization contains users and projects; a project contains the monitored domain context, observations, findings, policies, alerts, and evidence for one deployment scope. Keep unrelated websites or environments in separate projects when their owners, policies, or evidence boundaries differ.
Procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Settings in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Record the administrative baseline
Capture the active organization and project, current owners or members, verified domain, relevant limit or schedule, and the existing value that will change.
- 3.
Hierarchy
Confirm the active organization and project, the person or team accountable for the change, and the role required to perform it. Verify the resulting access or ownership state from a second authorized context when practical.
- 4.
Isolation
Preserve the failing state, test the most local dependency first, and make one reversible change at a time. Reproduce the original journey after each check and stop when the evidence points to a different layer.
- 5.
Verify from the intended operating context
Reload the page and confirm the saved value in the correct organization and project. When the change affects another person, domain, or scheduled run, verify it from that operating context as well.
- 6.
Record ownership and continuity
Preserve who made the change, who owns the resulting state, the organization and project, time, validation result, and recovery or handoff instructions.
Switch projects
Use the project selector to change the active SiteWall context. After switching, confirm the displayed domain and project before reading totals or editing policies: navigation can stay on the same feature while its records change to the selected project.
Add and verify a domain
Add the intended website as a project domain, complete the verification method shown by SiteWall, and wait for the verified state before relying on monitoring results. If verification fails, check the exact domain, DNS or page placement, redirects, caching, and project selection.