SVX Documentation
HomepageAPISDK
Current
Current
  • Docs
  • Concepts
    • Digital Identity and Why It's Important
    • Digital Wallets
    • Ecosystems
    • Information Security
    • Personal Data & Attributes
    • Privacy- and Security-by-design
    • Secure Data Storage
    • Selective Disclosure / ZKP
    • Tokens and Tokenisation
    • Verifiable Credentials
    • Terminology
  • Platform
    • Secure Value Exchange
    • Authorisation, Tenant & Organisation Manager (ATOM)
    • Credential Service
    • Decentralised Identifiers (DIDs)
    • Keys
    • Tenants, Organisations, and End-Users
    • Vault
      • Enterprise Vault
    • Portal
    • Supported Standards
  • Guides
    • Onboarding to SVX
    • API Guides
      • Credentials
        • Credential Schemas
        • Credential Types
        • Issue Credentials
        • Presentation Definitions
        • Presentations
      • DIDs
        • DID Resolver
        • DID Registrar
        • DID Methods
          • did:key
          • did:web
          • did:ebsi
          • did:indy
        • DID Controller Keypair
      • OpenID Connect
        • For Verifiable Presentation
      • Users
        • Inviting End-Users
        • Authenticating End-Users
      • Vault
        • Items and Slots
        • Connections and Sharing
        • Classification Hierarchies
        • Attachments
        • On-sharing & Client Tasks
        • Account Delegation
      • Machine-2-Machine Communication
    • Portal Tutorials
      • Tenant Administrators
        • Onboard to a Tenancy
        • Dashboard and Navigation
        • Manage Tenancy
        • Manage Tenant Administrators
        • Manage Organisations
        • Manage Organisation Administrators
        • Credential Schemas
        • Applications
        • End Users
      • Organisation Administrators
        • Manage Organisation
        • Onboarding and Organisation Setup
        • Dashboard and Navigation
        • Manage Organisation Administrators
        • Credential Templates
        • View Credentials
        • Verification Templates
        • Verification Requests
        • Connections
        • Applications
    • Wallet Tutorials
      • Wallet Set Up
      • Provider Registration
      • Organisation Configuration
      • Credentials
      • Requests
      • Security
      • Wallet Recovery
  • Tools
    • Meeco SDK & CLI
    • Cryppo SDK & CLI
  • Releases
    • 2.1.1
    • 2.1.0
    • 2.0.0
    • 1.4.3
    • 1.4.2
    • 1.4.1
    • 1.4.0
    • 1.3.8
    • 1.3.7
    • 1.3.6
    • 1.3.5
    • 1.3.4
    • 1.3.3
    • 1.3.2
    • 1.3.0
    • 1.2.5
    • 1.2.4
    • 1.2.3
    • 1.2.2
    • 1.2.1
    • 1.2.0
    • 1.1.0
    • 1.0.0
    • Legacy API-of-Me
  • Policies
    • Privacy
    • Developer Policy
Powered by GitBook
On this page
  • Users and Organisations Explained
  • Network Participants and their Role

Was this helpful?

Edit on GitHub
  1. Platform

Tenants, Organisations, and End-Users

Last updated 29 days ago

Was this helpful?

Within Meeco’s Secure Value Exchange (SVX) platform, different entities have been developed for different purposes. Understanding the difference between these entities, how it maps to users and organisations is important, as it will help you to understand the responsibilities of each.

It is worth noting that regardless of whether you are using Meeco’s APIs, or if you are interacting via our , the different users and organisations are consistent across both.

Users and Organisations Explained

Throughout this documentation, the term ‘Users’ broadly refers to individuals interacting with the SVX platform, including our customers' customers and those engaging with various workflows. Within SVX, the term ‘End-users’ specifically denotes Wallet Holders and users associated with a Tenant (refer to the section below for further details).

Please note that the term ‘Organisation’ is occasionally used throughout our documentation as a cover-all term for any enterprise, company, group, or association. When utilising SVX, ‘Organisation’ refers to a specific role played by an enterprise, company, group, or association undertaking actions within a Tenancy.

Network Participants and their Role

SVX network participants as follows:

Ecosystem Participant
Role

Tenant

A Tenant is operated by an enterprise. Its main responsibility is the governance of its network, participating organisations, and end-users.

Tenant Administrator

An individual (user) who has administrator access within a Tenant. A Tenant Administrator is responsible for the actions that take place within their Tenant, including the onboarding, management and governance of Organisations.

Organisation

An Organisation participating in the ecosystem will typically take the role of a credential or data Issuer, Verifier, or both. Organisations connect to End-users to exchange data.

Organisation Administrator

An individual (user) who has administrator access within an Organisation. An Organisation Administrator can use the Portal to manage the lifecycle of credentials and set up machine-to-machine access.

End-User

End-users are associated with a Tenant and benefit from services offered by that Tenant including the ability to connect to Issuers, Verifiers, and create a vault.

For more information on how users and organisations form an ecosystem, see our page.

Portal
Ecosystems