oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

GITBOOK-408: Removed mermaid diagram added as an example in the roles page

Browse Source
This commit is contained in:
Ana Loznianu 2023-06-05 10:10:30 +00:00 committed by gitbook-bot
parent 00951841ea
commit 1c19f09da3
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
developers/contracts/roles.md
View File

@ -13,9 +13,6 @@ The permissions are stored in the data NFT (ERC721) smart contract. The data NFT
The data NFT is the base IP for the asset and all the datatokens are therefore linked to the data NFT smart contract — this has enabled us to do a bunch of cool new things around role administration. We’ve introduced a host of useful roles which give you flexibility in how you manage your project. This can be a big help for enterprises and startups who are ready to scale up and introduce a level of administration.
```mermaid
```
#### NFT Owner
The NFT owner is the owner of the base-IP and is therefore at the highest level. The NFT owner can perform any action or assign any role but crucially, the NFT owner is the only one who can assign the manager role. Upon deployment or transfer of the data NFT, the NFT owner is automatically added as a manager. The NFT owner is also the only role that can’t be assigned to multiple users — the only way to share this role is via multi-sig or a DAO.