Roles
It's crucial to understand the basic Hadron by Tether access control model and how your API access fits within it. A central part of the Hadron by Tether access control model is the concept of roles. The following roles are currently supported:
Hadron by Tether Access Control Roles
Role | Description | System Privileges |
---|---|---|
Issuer | A legal entity that registers and sells securities/digital tokens, with the purpose of generating income to fund operations. | Create assets, allocations, distributions, manage customers, issue and tokenize assets |
Minter | A person from the Issuer Organization, who is responsible for Asset Management of the Tokens deployed | Minting, Burning, Transfer of Tokens |
Signer | A person responsible for signing proposals within the system. | Sign proposals related to various operations within the platform |
Customer | Any party (either individual or institution) that invests in an offering, either directly with the issuer or through a minter. | View distributions, holdings; and transactions |
KYC Analyst | A person responsible for KYC/KYB collection and management of compliance documents of the customers | KYC/KYB Documents, manage approve/disapprove the customer KYC documents. |
Every account on the platform is assigned one of these roles. This role-based access control system ensures that each user has the appropriate permissions and capabilities within the Hadron by Tether ecosystem.
Updated about 1 month ago