THE KNOWLEDGE CENTRE0.1.1-dev DEV
Browse the knowledge centreKnowledge centreMake sense of your workspace.The complete manual 16 chapters · print or save
REFERENCEFree & Pro1 min read

Site, network and permission boundaries

Use the workspace that owns the evidence and keep viewing, settings and deletion permissions distinct.

IN YOUR WORDPRESS WORKSPACE

Site Admin → Logged.ai; Network Admin → Logged.ai

01

Choose the right scope

#

The site workspace follows the current authorized WordPress site. Network Admin has a separate Logged.ai workspace for network-origin evidence, network exports and network privacy settings.

A network-origin export does not combine all site timelines. Other networks and individual sites have their own scope. Logged.ai's WordPress multisite views are not a shared dashboard for unrelated client installations.

02

Permissions remain separate

#

Viewing events does not automatically permit changing settings, exporting evidence, examining sensitive address context, managing response or purging data. Navigation shows only registered pages that your current account can access.

Pro investigation and reporting workflows also check evidence authority. A shared search or an authenticated link does not grant missing permissions. If a page becomes unavailable, check the current account, site context, active plugin pair and assigned permissions.

03

Operational planning

#

Use a staging copy of your own multisite arrangement before rollout. Confirm compatibility with the WordPress, WooCommerce and multisite versions you use. Commercial site allowances are a separate licensing policy from WordPress capabilities.

ABOUT THIS REFERENCE

Written for Logged.ai Studio v7 / Free and Pro 0.1.1-dev. The development build and its documented limits apply.

A question we haven’t answered?

Get help with your next step.

Contact support