Organization and workspace boundaries

Why membership, selected workspace, and resource scope determine visible data.

Isolation

Every private data request requires an authenticated user, organization, and workspace. A client-provided identifier never replaces server-side membership validation.

Scopes

Role supplies candidate permissions.
Group combines users and policy.
Scope limits accounts, branches, warehouses, or resources.
Plan and feature state can further deny access.

Context switching

Verify the active workspace before an export, AI request, or configuration change. Context must not leak between workspaces.

A note on availability

Features depend on plan, role, connected marketplace, and data readiness. ProfitVena does not replace primary marketplace statements or regulated accounting and legal records.

Organization and workspace boundaries

Isolation

Scopes

Context switching

Related documentation