Permissions, data & business rules · Verify

Tenant Isolation Check

Verify one tenant/workspace/project isolation invariant through bounded cross-tenant scenarios. Prove the selected patch or behavior without broadening into unrelated auth or data audit work.

Vibe Coding 1.3.0 · vibe-domain · English technical instructions

← Back to search

Use this workflow

Use this workflow in Codex or Claude Code with the free Vibe Coding plugin. Choose your assistant and prompt language, then add your task details after the prompt.

Prompt

Use $vibe-domain, workflow “Tenant Isolation Check” (ID: tenant-isolation-check). Follow this workflow for the task below. Report the result in English.

Install the plugin

Operation

Verify the selected invariant through bounded scenarios in an authorized environment. Do not turn verification into unrelated implementation. Return passed, failed or blocked, with actual evidence and any missing required scenario.

Goal

Verify one tenant/workspace/project isolation invariant through bounded cross-tenant scenarios. Prove the selected patch or behavior without broadening into unrelated auth or data audit work.

Required input

Provide the selected resource/action, tenant states, implementation summary or patch boundary, safe fixtures/accounts, and repository-native commands or manual scenarios.

Scenarios

Same-tenant access succeeds with correct data.
Wrong-tenant read, list, search, write, export, job, or object access fails safely.
Missing/stale tenant context fails safely.
Admin/staff/impersonation access follows explicit policy and produces audit evidence when required.
Cache/search/analytics/logging surfaces do not expose another tenant’s data for the selected boundary.

Workflow ID: tenant-isolation-check · View the versioned source · Shared workflow and authority rules