Managed Visibility Policy
How organization-managed accounts disclose what the company can see, what stays scoped to the employee, and how visibility templates are applied and audited.
Visibility should be governed by named templates instead of being inferred from loose admin behavior.
Every managed visibility template should be tied to employee-facing disclosure and an audit trail.
The workspace should make the current default posture obvious before any employee is onboarded.
The platform workspace should treat visibility policy as a first-class operational control instead of burying it in a generic role setting.
That protects both the employee and the organization when permissions evolve over time.
{
"visibility_template": "full_managed_account_visibility",
"scope": [
"org_markets",
"assigned_programs",
"permitted_global_markets"
],
"disclosure_required": true,
"audit_logged": true
}Managed visibility should be explicit, disclosed, and auditable.
Managed visibility should never be hidden in fine print. The employee needs a clear explanation of what the organization can review, what remains outside scope, and which visibility template is being applied.
The platform workspace should treat visibility policy as a first-class operational control instead of burying it in a generic role setting.
Visibility templates should be versioned, timestamped, and easy to compare so the company can prove what it disclosed and when it changed.
That protects both the employee and the organization when permissions evolve over time.