TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Best practices around RBAC for modern digital banks

1 点作者 slavomirvojacek将近 5 年前
Anything people could share on best practices around RBAC for modern digital banks (or perhaps for any type of software, if same applies)?<p>For example, do you name the roles Prospect, User, Admin, etc.? Or do you use levels to determine the level of access a user has, e.g. L0, L1, L2, ...?<p>How do you approach naming permissions? Let&#x27;s say I want to enable adding a payee:<p>a) create:payees b) create:payees:own c) ???<p>How about a UK-only payee?<p>a) create:payees:uk:own b) create:payees:own:uk c) ???<p>Or would you explicitly name the permission?<p>a) add_own_uk_payee b) add_uk_payee c) ???<p>Thanks in advance!

暂无评论

暂无评论