Is there someone I can talk to about the issues that I am having with the API? I am getting timeouts on multiple endpoints when trying to PATCH and DELETE

Hello @Bart Massey! Glad to have you here! Feel free to ask us anything! 💜

Hi @Jarek Głowacki! Good to see you here. Let me know if you have any questions 😊

Hiya! We just paid for pro license, and are still seeing trial bubble on the workspace:

Hi team, I have a pro subscription but still see this in the slack channel any ideas?

Hello @Andrew Brooke-Reid! Welcome to the community! Let us know how we can help 💪

Hi @Michael Chen! Glad to have you here! Happy to answer questions! ⭐

Hi @Jeff Lantz! Good to have you with us! Happy to answer questions! check

Hi @JesperLMadsen! Good to see you here. Let me know if you need my help ⭐

Hey @Sebastian Lauwers! Good to see you here. Let me know if you need my help 😊

Hi @Harshita Kalani! Glad to have you here! Let me know if you need my help 💜

Hi @Nicole Pellicena! Good to have you with us! Happy to answer questions! ✨

Hi @Niall Inglis! Good to see you here. Happy to answer questions! 🌸

Hey @Mihiru Kongahage! Glad to have you here! Let me know if you need my help ✨

Hey @Esteban Andres Murcia Acuña! Good to have you with us! I’m available for anything you might need 😊

Hello @Ethan Kong! Good to see you here. Feel free to ask us anything! 💜

Hi team, I’m running into an intermittent issue when initializing the Permit Node.js SDK. Most of the time the SDK fails, but occasionally the request succeeds.

{"level":50,"time":"2025-11-22T09:40:20.177Z","label":"<http://Permit.io|Permit.io>","msg":"[undefined] permit.api.getApiKeyScope(), err: undefined"}
Error creating resource instance: PermitContextError: could not fetch the api key scope in order to set the api context level

I’ve tested this with both Cloud PDP and a local PDP, but the behavior is the same. SDK Initialization:

const permit = new Permit({
  token: process.env.PERMIT_API_KEY || '',
  pdp: '<https://cloudpdp.api.permit.io>',
  timeout: 30000,
  apiContext: {
    project: "default",
    environment: "dev",
  },
  throwOnError: true,
  log: {
    level: 'debug',
  }
});

Can you clarify what causes this intermittent failure and how to resolve it?

Hi @James Bohrman! Glad to have you here! Let me know if there’s anything I can do for you 👋

Hey Permit.io team!!!

Love your branding 😭

🙂

Hello @Nathan Rydel! Welcome to the community! Let us know how we can help ✨

Hello @Imran Bohoran! Glad to have you here! Ask me anything! ⭐

Hi Team, We have need to implement a simple RBAC + ReBAC access control model and I'd like to validate the approach and design. Our Use Case I have a system with organizations, and each organization contains projects and users. Every user in an organization is assigned the member role by default. Members are allowed to create projects. Each project has its own project-level roles: - project_admin - project_member When a user (who is an member) creates a project, they automatically become the project_admin for that specific project. A project_admin can: Add or remove project_members Add or remove project_admins Current Permission Model Resource Types - project Roles - member - project#project_admin - project#project_member Each role has specific allowed actions on the resource types. Example permission check:

{
  "user": {
    "key": "user_id1"
  },
  "action": "create",
  "resource": {
    "type": "project",
    "tenant": "default",
    "key": "project_test10"
  },
  "context": {}
}

Is this RBAC + ReBAC design and resource-instance model valid for Permit.io for this use case? Any other design options/candidates that you'd recommend? In the first iteration, we'd like to use the cloud PDP exclusively without a local PDP setup. Is there a another approach where this kind of permission model can be supported by exclusively using cloud PDP?

Hi @Charlie Cetin! Good to see you here. I’m available for anything you might need 😊

Hey @Anuradha Weeraman! Welcome! I’m available for anything you might need check

Hello @Bartosz Wasilewski! Good to have you with us! Happy to answer questions! 👋

Hey @Matan Benjio! Glad to have you here! Happy to answer questions! 😊

Hey @Suman.p! Welcome to the community! Let us know how we can help 💜

Hi team, I'm integrating Trino with Permit.io for Row Filtering and Column Masking. However, I'm facing a 'deny-all' behavior. Trino sends authorization checks for everything (loading catalogs, system metadata, etc.), and the OPA logs show that every single request is returning

result: false

. Could you please help me identify the root cause of this issue?