Skip to content

Commit 7bed32e

Browse files
hotlongCopilot
andcommitted
fix(cloud-control): remove App-level permission gate
cloud_control is the default landing surface for any authenticated cloud user (create/manage their orgs and projects). Gating it on a 'cloud.control.access' permission was wrong — it would have hidden the App from the very users it's built for. Data-level isolation (which orgs/projects each user sees inside the App) is enforced by sharing rules on sys_organization / sys_project, not by an App-level requiredPermissions check. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 5f30834 commit 7bed32e

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

packages/services/service-tenant/src/apps/cloud-control.app.ts

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,10 @@ export const CLOUD_CONTROL_APP: App = {
3232
branding: {
3333
primaryColor: '#2563eb', // Blue-600 — distinct from Setup's slate
3434
},
35-
// Only org owners/admins see this app. The control-plane API itself
36-
// also enforces this; nav-time check is cosmetic.
37-
requiredPermissions: ['cloud.control.access'],
35+
// No App-level permission gate: any authenticated user can open the
36+
// Cloud Control App to create/manage their own organizations and
37+
// projects. Data-level isolation (which orgs/projects each user sees)
38+
// is enforced by sharing rules on sys_organization, sys_project, etc.
3839

3940
navigation: [
4041
{

0 commit comments

Comments
 (0)