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
  • Functionalities
  • Services executed via an Enterprise Vault
  • Interacting with the Enterprise Vault

Was this helpful?

Edit on GitHub
  1. Platform
  2. Vault

Enterprise Vault

Last updated 5 months ago

Was this helpful?

An Enterprise Vault (EV) is a secure service similar to an End-user Vault with added functionality tailored to enterprises. Enterprise refers to any entity, for example a company, government, or association. In the context of an EV, an “Organisation” is the entity that controls and manages their own EV.

Functionalities

The key functionalities of an Enterprise Vault are as follows:

  • , , , , , (as per an End-user Vault).

  • Fined-grained consent capabilities to manage the sharing of data with end-users.

  • The Organisation that manages an EV can have one or more Administrators who are authorised to onboard and manage other Administrators.

  • The Administrator(s) of an EV can manage and deploy additional services that work harmoniously with the EV's features and functions.

  • Administrators, with the associated access rights, have access to , and in the EV.

  • Organisation Administrators have the ability to onboard third-party services (associated with the Organisation) to act on behalf of that Organisation. This enables third-party services access to , and within the EV in a secure, controlled way.

  • An Organisation can connect to any user or other Organisation via a Vault-to-Vault conenction in order to undertake various workflows.

Services executed via an Enterprise Vault

The following are examples of services the EV offers:

  • Secure data storage: Storage of data including, but not limited to:

    • raw data

    • structured data

    • verifiable data

    • self-attested data

    • semantic data

    • verifiable and verified data (including Verifiable Credentials)

    • documents

  • Secure sharing: Structured data shared in a persistent or one-off way, for example: a document or attachment. Shared data can also include a business rule that determines if the data can be edited/updated, or locked to prevent editing by the Organisation or other parties.

    • A specific implementation of secure sharing is the creation of an pushed via a secure API to an End-user Vault, without storing the in the EV. This allows the secure sharing of sensitive data from other systems without the need to maintain the in the EV.

  • Securely receiving: Structured data from any authorised party (end-user or third-party) within an EV ecosystem. This enables easy integrations with other services.

Interacting with the Enterprise Vault

There are multiple ways to interact with and manage an EV, including:

Onboarding to an Enterprise Vault: To set up an EV, an authorised user must first create an Organisation. Note that setting up an Organisation will require either approval via the creation of a Meeco Licence, or via an ecosystem's Tenant Administrator.

SVX Portal: The is a web application that enables Organisation Administrators to onboard, invite additional Organisation Administrators, and begin accessing Meeco's Vault API via a low-code interface. When using the EV via the Portal, Administrators can view , and . It also provides a view of the End-users and other third-party services that the Organisation is connected to.

SVX API: All functionality is available using the to connect services.

Command Line Interface (CLI): Meeco provides a to facilitate interactation with the EV.

Items
Slots
Connections
Sharing
Classifications
Attachments
Items
Connections
Shares
Items
Connections
Shares
Item
Item
Item
Portal
Items
Connections
Shares
SVX API (sandbox)
CLI