Show HN: Permit Elements- UIs to let your customers manage their own damn RBAC

Hi HN! Co-Founder of Permit.io here, I’ve built access-control to my products, thousands of times throughout my career - and at no point did I want to.

We adopted OPA, created OPAL.ac (open-source), and Permit.io on top - so no developer would have to build permissions again.

To truly solve this problem end-to-end we’re releasing Permit-Elements (https://permit.io/elements) - embeddable UIs providing the interfaces you need so your end-customers can control access-control (e.g. user-management, audit-logs, approval flows, permission requests, api-key management, …)

Check out the full tutorial: https://youtu.be/xGYdDF65lkQ

The solution highlights: - Authorization for Authorization (who can control who controls permissions) - Security (auditing, real-time decision making and meeting industry standards) - An easy integration (generate and embed a JS snippet)

There’s a lot more to do, we’d love your feedback on Permit in general, this feature, and others. Chat with us on Slack (https://bit.ly/permit-slack)

Thanks, Or Weis

Show HN: Permit Elements- UIs to let your customers manage their own damn RBAC
youtube.com

Hi there! I appreciate the concern - But note that Permit elements allow you to delegate access control to any one of your team members, end users, or customers - as it uses a simple no-code UI to do that, It could allow your security team easier access to overview the entire process, and thanks to Permit.io building on policy as code you always have full control of the generated flow via Git.

[flagged]

Seems like you're trolling with your user you created less than 10 minutes ago... :D But here's a serious honest answer: OPA is the fundamental policy engine used by this tool to write and enforce policies. It does not, however, offer the ability to abstract, control, and manage permissions through a UI. Rego code isn’t easy to write, and managing this with OPA only still leaves 100% of the work on the dev side. The idea here is to allow your end users (Which, a lot of the time, are not technical at all) to manage permissions without having to write code, and without the devs having to build a UI that allows them to do so.

Glad you like it! Let us know if you need any help to get started. We are very responsive on Slack :) https://bit.ly/permit-slack