Detailed walkthroughs of the four User Personas in the ConsenSource UI
The ConsenSource UI allows users to accomplist two primary tasks:
- Submit transactions to the ConsenSource network that update the state of the blockchain
- Discover and monitor certification data, and organizations involved in the certification process
In order to submit transactions to the network, users are represented on the blockchain as an agent. Agents can act on behalf of an organization.
Passwords and private keys are not stored on the blockchain - only the agent assosciated to a user is stored on-chain.
Agents are created for a user during the sign up process. The admin of an organization can add or remove an agent at any point. All transactions that are submitted to ConsenSource must have an assosciated agent and organization.
An organization is representative of one of four distinct persona types:
Each of the personas has a distinct role in the certification lifecycle, and can only perform a specific set of actions that will update the state of the blockchain. For example, an agent that is a member of a factory organization cannot approve or deny certifications.
The organization that a user belongs to determines the set of components that they are able to interact with in the UI. For example, a Retailer/Brand is able to favorite a list of factories that they do business with, but a factory cannot favorite other factories.
Read the guides below to learn more about the ConsenSource UI.
ConsenSource UI Guides
Overview of how private and public keys are managed in the UI
Explanation of the transaction & batch building processes
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.