Site, network and permission boundaries
Find the workspace that owns the evidence and understand why viewing a page does not grant every action on it.
For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.
On this page
Site Admin → Logged.ai; Network Admin → Logged.ai
A site workspace covers that authorized site. Network Admin has a separate view of network-origin evidence; it does not merge every site’s timeline.
| What you are reviewing | Open | Scope |
|---|---|---|
| An action inside one site | That site’s Admin → Logged.ai | The current authorized WordPress site. |
| An action from network administration | Network Admin → Logged.ai | Evidence originating in the current network’s administrative context. |
| A network-origin export | Network Admin → Logged.ai → Exports | Network-origin evidence; not a combined export of all sites. |
| An unrelated client installation | That installation’s own WordPress admin | Multisite views are not a remote dashboard for separate installations. |
Use the WordPress site switcher when you need another authorized site. Shared plugin, theme or WordPress files can affect multiple sites even when the recorded action originated in a network workspace.
| Task | Why viewing alone is not enough |
|---|---|
| Change collection or privacy settings | Settings authority is checked separately. |
| Download evidence | Export authority is checked separately. |
| Inspect sensitive address context | The account needs the relevant sensitive-context grant. |
| Manage alerts or response | The corresponding management authority is required. |
| Shorten retention or purge evidence | Deletion needs its own evidence-purge authority and confirmation. |
Navigation shows registered pages the current account can access. Pro investigation and reporting workflows also check evidence authority. A saved search, shared link or Pro installation does not grant missing permissions.
- Confirm the account and selected site or network.
- Check that Free and the compatible Pro package, when needed, are active.
- Ask the site administrator to review the specific missing permission; avoid granting broad access just to make a button appear.
This can be an intentional permission boundary. Their ability to read a record does not automatically authorize a downloadable copy.
- Use a staging copy that represents your WordPress and WooCommerce setup.
- Test one site action and one network action; confirm each appears in the expected workspace.
- Verify viewing, export and deletion boundaries using the actual roles your team will use.
- Keep commercial site allowances separate from WordPress permissions; a licence allowance does not change capabilities.
The packages have scoped multisite behavior, not a guarantee for every host, extension or network arrangement. Preserve each site’s own privacy and retention requirements.
This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.
Get help with your next step.