Create and update sites
Register public domains, names, and allowed origins for the sites LoopAware should monitor.
Site management
Owner and admin site management
LoopAware gives owners and admins the controls needed to create sites, update allowed origins, manage settings, reassign ownership, and keep site access role-aware.
What managers own
Site managers own the boundary between public collection and private review. That includes allowed origins, widget settings, team membership, health monitors, traffic schedules, and protected LA Sentry tokens.
Read-only team members can review site signals but do not get these management controls.
Common management jobs
Assign access
Add team members for read-only review and keep manager-only actions restricted.
Operate settings
Configure widget display, subscriber forms, traffic schedules, uptime checks, and LA Sentry setup.
Limitations
- LoopAware site management is not a full CRM or support-seat system.
- Global admin access should remain an operator-controlled deployment decision.
- Separate unrelated products or clients should use separate sites.
Best fit
Use this when one operator account needs to manage several public signal surfaces with clear role boundaries.
Implementation checklist
- Confirm which operator is the owner and which users need team-member access for the site.
- Review allowed origins, snippets, traffic reports, uptime checks, and LA Sentry settings before changing ownership or access.
- Use the dashboard role boundaries to keep management actions with owners and admins.
Common questions
When should teams use this owner admin site management guide?
Manage LoopAware sites, ownership, allowed origins, settings, and role-aware dashboard access from the operator account. It is useful when LoopAware access needs to match how people actually review and act on site signals.
What should teams verify after setup?
Confirm the workflow is tied to the correct LoopAware site, then check the first dashboard records with the people who will act on them.