1
0
mirror of https://github.com/bigchaindb/site.git synced 2024-11-22 01:36:55 +01:00
This commit is contained in:
Ricardo Garcia 2017-12-29 13:58:19 +01:00 committed by GitHub
parent bdf68bbb6a
commit b61d5416f9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -1,20 +1,20 @@
---
layout: guide
title: "Tutorial: RBAC"
tagline: Create tribes where people with different roles can create proposals and or vote.
title: "Tutorial: Role-based access controls in BigchainDB"
tagline: Learn how to assign different roles and permissions to different user types in BigchainDB
header: header-rbac.jpg
order: 4
learn: >
- How RBAC works on BigchainDB
- How Role-based access controls work in BigchainDB
---
Hi there! Welcome to our next tutorial about Role-Based Access Control in BigchainDB. For this tutorial, we assume that you are familiar with the BigchainDB primitives (assets, inputs, outputs, transactions etc.). If you are not, familiarize yourself with the [Key concepts of BigchainDB](../key-concepts-of-bigchaindb/). We also assume that you have completed our [first tutorial](../tutorial-car-telemetry-app/).
Hi there! Welcome to our next tutorial about Role-based access controls (RBACs) in BigchainDB. For this tutorial, we assume that you are familiar with the BigchainDB primitives (assets, inputs, outputs, transactions etc.). If you are not, familiarize yourself with the [Key concepts of BigchainDB](../key-concepts-of-bigchaindb/). We also assume that you have completed our [first tutorial](../tutorial-car-telemetry-app/).
# RBAC
# About RBACs
Role based access control is a way to restrict the system access to certain users. In BigchainDB this function enables the creation of hierarchies of role and permissions. Furthermore, users can be assigned roles to “act on behalf of” or “represent” other users or groups.
In our case we propose different tribes where people have different roles, some can create proposals and some others can vote those proposals.