The "organization not found" error when the organization exists is likely a tenant scoping issue. In Permit.io, tenants represent isolated silos of resources and users (1) . Resource instances belong to specific tenants, and only users within that tenant can access those resources . When performing permission checks, you must specify the correct tenant. Here's the proper format for checking permissions on a resource instance:

const permitted = await permit.check(userKey, "action", {
  type: "resource_type",
  tenant: tenantKey,
}) ;

To troubleshoot this issue, I need some additional information from you: 1. Which Workspace / Project / Env are you using? 2. What calls are you performing? (Please share the SDK code or CURL request) 3. Which PDP version are you running? 4. Can you share relevant logs from your PDP? Additionally, verify: • The resource instance was created with the correct tenant specified • Your permission check includes the matching tenant parameter • The user has been assigned to the same tenant where the organization exists (2) You can use the List Role Assignments API to verify which tenant contains your organization resource instance (3)

To learn more, see the sources I considered: [[1] Multi-Tenant Authorization](https://docs.permit.io/concepts/multi-tenant-authorization) [[2] Sync your First User](https://docs.permit.io/overview/sync-your-first-user-with-sdk) [[3] GET /v2/facts/{proj_id}/{env_id}/role_assignments/detailed](https://api.permit.io/v2/redoc#tag/Role-Assignments/operation/list_role_assignments_detailed) [[4] Overview](https://docs.permit.io/api/examples/filter-role-associations)

There is no multi tenant

@Ask Inkeep live env. it's not about pdp, the error is on permit ui, not on pdp

* Thanks for clarifying this is happening in the Permit UI in your live environment and started suddenly today. Even if you're not explicitly using multi-tenancy, Permit.io has a default tenant that all resources belong to (1) . The "organization not found" error in the UI could indicate: • The organization resource instance exists but may have become associated with an incorrect or missing tenant reference • A recent change or sync issue affecting how the UI queries organization data Since this worked fine previously and broke suddenly today, this suggests a data sync or configuration issue rather than a code problem. To help diagnose this UI issue, please provide: 1. Which ​*Workspace / Project / Environment*​ you're using in the live environment 2. Can you share the ​*exact error message*​ you're seeing in the UI (screenshot would be helpful) 3. Are you able to see these organizations via the ​*API*​ (even if the UI shows the error) ? 4. Did any ​*configuration changes*​ happen today (policy updates, role changes, user assignments) ? You might also want to verify the organization exists by checking via the API directly, which can help determine if this is purely a UI display issue or a deeper data problem. For immediate support with UI-specific issues in your live environment, I'd recommend reaching out over Email with the above details so the engineering team can investigate your specific workspace configuration.

To learn more, see the sources I considered: [[1] Multi-Tenant Authorization](https://docs.permit.io/concepts/multi-tenant-authorization)

Will escalate to the team

I mean fails on sdk

give me min

@Or Weis okay, now assigning using sdk worked, but will the same problem of losing roles reappear again?

Frontend not working was something we faced while debugging that

If you see other errors in API,SDK, or PDP please share and we’ll investigate

Assign them; if you get an error for that we can investigate

It’s extremely unlikely that your assignments were removed automatically

it was on startup and we moved to pro to fix it