---
title: "Discussion on \"A Practical Specification for Roles, Permissions, and Policy Decisions\" | Hashnode"
description: "Discussion on \"A Practical Specification for Roles, Permissions, and Policy Decisions\". The full specification is available here: Authorization Model Specification.\n\nAuthorization logic often starts simple.\nAt first, a role like admin, editor, or viewer is enough. Then the product grows."
url: "https://hashnode.com/posts/a-practical-specification-for-roles-permissions-and-policy-decisions/6a09b09c3104e2aff08f2796"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A Practical Specification for Roles, Permissions, and Policy Decisions](https://hamidreza.tech/a-practical-specification-for-roles-permissions-and-policy-decisions?utm_source=hashnode&utm_medium=feed)

The full specification is available here: Authorization Model Specification. Authorization logic often starts simple. At first, a role like admin, editor, or viewer is enough. Then the product grows.

May 17 · 4 min read · hamidreza.tech  
Read the article

-   [#authorization](https://hashnode.com/tag/authorization)
-   [#rbac](https://hashnode.com/tag/rbac)
-   [#auth0](https://hashnode.com/tag/auth0)
-   [#authentication](https://hashnode.com/tag/authentication)

## Written by

[Hamidreza Mahdavipanah](https://hashnode.com/@mahdavi)

@mahdavi

  
[View profile](https://hashnode.com/@mahdavi)

Software Engineer

Software Engineer | Code, Life, and Debugging the Human Experience.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
