mirror of openzeppelin-contracts
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
openzeppelin-contracts/contracts/access
NishantKoyalwar e7ba2f7784
Move beneficiary zero address check to Ownable (#4531)
1 year ago
..
extensions Use named arguments in mapping types (#4433) 2 years ago
AccessControl.sol Use named arguments in mapping types (#4433) 2 years ago
IAccessControl.sol Update pragma to 0.8.20 (#4489) 2 years ago
Ownable.sol Move beneficiary zero address check to Ownable (#4531) 1 year ago
Ownable2Step.sol Update pragma to 0.8.20 (#4489) 2 years ago
README.adoc Change access folder structure (#4359) 2 years ago

README.adoc

= Access Control

[.readme-notice]
NOTE: This document is better viewed at https://docs.openzeppelin.com/contracts/api/access

This directory provides ways to restrict who can access the functions of a contract or when they can do it.

- {AccessControl} provides a general role based access control mechanism. Multiple hierarchical roles can be created and assigned each to multiple accounts.
- {Ownable} is a simpler mechanism with a single owner "role" that can be assigned to a single account. This simpler mechanism can be useful for quick tests but projects with production concerns are likely to outgrow it.

== Core

{{Ownable}}

{{Ownable2Step}}

{{IAccessControl}}

{{AccessControl}}

== Extensions

{{IAccessControlEnumerable}}

{{AccessControlEnumerable}}

{{IAccessControlDefaultAdminRules}}

{{AccessControlDefaultAdminRules}}