Hi @Ryan Lonstein! Glad to have you here! I’m available for anything you might need ✌️

Hi, is it possible to use the Frontend Components without exposing any user data outside our own VPC ?

Hello @Jeremiah Isijola! Good to have you with us! I’m available for anything you might need check

Hi @Ben Rohald! Glad to have you here! Ask me anything! 💜

Hey @Aniket Roy! Good to have you with us! Let me know if there’s anything I can do for you 🌸

Hello @Alon Boshi! Good to have you with us! Let me know if there’s anything I can do for you check

Hi @Srinivas Medam! Good to have you with us! Let me know if you need my help check

👋 Hi everyone! I'm excited to join the Permit.io community! I'm currently working on implementing a modern RBAC system for a ChatGPT-like application built with: • Backend: Node.js + Express.js + MongoDB • Frontend: Next.js + React • Auth: Firebase + JWT What I'm building: A chatbot application with two main roles (admin & users) where: • Users can only access their own conversations • Admins can view/manage all conversations and users • Strong conversation isolation and admin protection rules I'm particularly interested in exploring Policy-as-Code patterns and learning from the community's experience with scaling authorization systems. Really looking forward to connecting with fellow developers who are tackling similar challenges! Currently researching the best approach between: 1. Custom RBAC middleware implementation 2. Integrating OPA for policy-as-code 3. Using Permit.io's SDK for a more robust solution Any insights or experiences you'd like to share would be greatly appreciated! 🚀

Hello @Samuel Taylor! Welcome to the community! Ask me anything! ✌️

Hello @Gabriel Sandrini! Good to see you here. Ask me anything! 🌸

Hi @Matheus Poleza! Good to have you with us! Let me know if you have any questions 👋

Hi @Suhas Kelkar! Good to see you here. Let me know if there’s anything I can do for you 💪

Hi @Gabriel L. Manor We are a young startup and have been using permit.io successfully. It's been a while since I created my permit.io account. I am trying to figure out what plan I am currently on and whether or not I want to upgrade to a paid plan. I am having tough time figuring out where to look for this info. Everytime I log into permit.io, and then click on Upgrade (in the left hand menu) it asks me to sign in again. Then it shows me the attached screen. I am not able to find what plan I am on, and how to upgrad.

Hello @Ryan Barriger! Welcome! Let me know if there’s anything I can do for you ✌️

Hey @Nam Nguyen! Welcome! Feel free to ask us anything! ⭐

Hello @Sibin Sajan! Good to have you with us! Let me know if there’s anything I can do for you ✌️

Hi @bdjgs! Good to see you here. Let me know if you have any questions 😊

Hi @Alex Leonov! Welcome to the community! Let me know if you need my help check

Hey @Raphael Ehindero! Good to have you with us! Let me know if you have any questions 💜

Hello @Pouya Xo! Welcome to the community! Happy to answer questions! ✌️

Hi everyone! I'm experiencing an issue with ABAC where user sets and resource sets aren't working together as expected. I followed the exact setup from this official video tutorial (), but I'm running into permission denied issues. My Setup User Configuration • Test User:

<mailto:test-user5@test.com|test-user5@test.com>

• Assigned Role: Manager • User Attributes: ◦ `location`: "USA" ◦ `department`: "Eng" Resource Configuration • Resource Type: Services • Resource Attributes: ◦ `cost`: numeric value ◦ `hasApproval`: boolean User Set Definition Engineer Managers in USA: { "allOf": [ { "allOf": [ { "user.location": { "equals": "USA" } }, { "user.department": { "equals": "Eng" } } ] } ] } Resource Sets Services Above $500: { "allOf": [ { "allOf": [ { "resource.hasApproval": { "equals": true } }, { "resource.cost": { "greater-than-equals": 500 } } ] } ] } Services Below $500: { "allOf": [ { "allOf": [ { "resource.cost": { "less-than": 500 } }, { "resource.hasApproval": { "equals": true } } ] } ] } Code Implementation const serviceCost = 400; const userEmail = "test-user5@test.com"; const userLocation = "USA"; const userDepartment = "Eng"; const serviceApproval = "true"; const checkPermission = async () => { setIsLoading(true); setError(null); try { const response = await fetch("/api/permit/check", { method: "POST", headers: { "Content-Type": "application/json", }, body: JSON.stringify({ user: { key: userEmail, attributes: { location: userLocation, department: userDepartment, }, }, action: "subscribe", resource: { type: "services", attributes: { hasApproval: serviceApproval, cost: serviceCost, }, tenant: "default", }, }), }); if (!response.ok) { throw new Error(

HTTP error! status: ${response.status}

); } const result = await response.json(); setIsAllowedToSubscribe(result.permitted); } catch (err) { setError( err instanceof Error ? err.message : "Failed to check permission", ); } finally { setIsLoading(false); } }; ``` The Problem Main Issue: Permission is always denied when using user sets and resource sets together. The system only works when I assign permissions directly to the user's role and specific resources. Error Scenarios Scenario 1: "No User Roles" Error Sometimes I get this error even though the user IS assigned to a role: { "__data_use_debugger": true, "__input_use_debugger": true, "allow": false, "allowing_sources": [], "debug": { "rbac": { "allow": false, "code": "no_user_roles", "reason": "no roles assigned to user 'test-user5@test.com'", "support_link": "https://docs.permit.io/errors/no_user_roles" }, "request": { "action": "subscribe", "resource": { "attributes": { "cost": 400, "hasApproval": "true", "type": "services" }, "type": "services" }, "tenant": null, "user": { "attributes": { "department": "Eng", "location": "USA", "roles": [], "tenants": [] }, "key": "test-user5@test.com", "synced": false } } }, "debugger_activated": true } Workaround: Deleting and recreating the user with role assignment temporarily fixes this. Scenario 2: "No Permission" Error After recreating the user, I get this error indicating the system isn't matching the user to the user set: { "__data_use_debugger": true, "__input_use_debugger": null, "allow": false, "allowing_sources": [], "debug": { "rbac": { "allow": false, "code": "no_permission", "reason": "user 'test-user5@test.com' does not have any role that grants him the 'subscribe' permission on resources of type 'services'", "support_link": "https://docs.permit.io/errors/no_permission" }, "request": { "action": "subscribe", "resource": { "attributes": { "cost": 400, "hasApproval": "true", "type": "services" }, "type": "services" }, "tenant": null, "user": { "attributes": { "department": "Eng", "email": "test-user5@test.com", "key": "test-user5@test.com", "location": "USA", "roles": [ "Admin" ], "tenants": [ "default" ] }, "key": "test-user5@test.com", "synced": true } } }, "debugger_activated": true } Environment • PDP running on Docker • Direct role-to-resource permissions work fine • Issue only occurs with user set + resource set combinations Questions 1. Is there a known issue with user sets and resource sets working together? 2. Why does the system sometimes not recognize assigned roles? 3. Are there any configuration steps I might be missing for ABAC setup? 4. Is there a way to debug why the user isn't being matched to the user set? Any insights or suggestions would be greatly appreciated! Has anyone encountered similar issues with ABAC implementations? Thanks in advance! 🙏

Hey @Abe Clark! Glad to have you here! Ask me anything! 💪

Anyone here succeeded in using permit for ReBAC working well with supabase RLS? I'd really like to have the flexibility of permit for modeling access, but still benefit from the RLS features of supbase. I've seen a few tutorials on permit that dance around it, but most implement as a backend check in an API route. One kinda gets close -- but doesn't go as far as ReBAC: https://www.permit.io/blog/postgres-rls-implementation-guide Seems like it may require replicating a version of the rules into postgres and standing up some helper methods to support RLS

Hi guys, I am experiencing a problem now: We have a backend call to

permit.getUserPermissions(id)

through the sdk, and it will return a full list of permission to the front end to render the items. Previously when we changed the roles of a user, the changes in the permission returned from that call also happens near real-time/immediately, but starting yesterday the

getUserPermissions

only returns the correct permission after around 5 mins approximately (different every time) after we changed the roles. Do you know why ? It looks like the rendering of the roles on permit.io side has some issue and propagation of the policy to our PDP is delayed

Hey @Maksym Petyak! Glad to have you here! Ask me anything! ✌️

Experimenting with Elements. It's unclear how to scope them to a specific resourceId -- for example to enable a google docs style sharing interface (grant access to a specific doc)

src="<https://embed.permit.io/workspace?envId=ABC&resourceInstance=DEF>"

Feels like it would go as a url param? I tried a few different options but the resulting request always ended up with

resource_instance_id=null

I set up email sending via SMTP (via sendgrid) but it doesn't seem to work. I assume it should work even though the official sendgrid integration isn't yet ready. Any advice?

Hey @Marshall Evans! Good to have you with us! Let me know if there’s anything I can do for you 😊

Hey @Aarsh Patel! Welcome to the community! Let us know how we can help ✌️

Hi @Bella! Welcome to the community! Let me know if there's anything I can help you with check