.alice.yaml. For the purposes of this example let's also create a second user .carol.yaml..organization-config.yaml with the content something like the following..organization.yaml file will look something like the following.status field is set to requested at this stage, this means our team has been notified of your intent to create the organization and will review and get in contact with you via the email provided. At this stage only you and the team at Meeco can see the organization. You can check organization was created and in requested state waiting for approval with the following command.@meeco/sdk npm package or hitting our API endpoints directly using the SDK as a guide..organization-service-config.yaml something like the following. (Hint: you can use the cryppo cli https://github.com/Meeco/cryppo-cli to quickly and easily create a keypair with the command cryppo genkeypair -p private.pem -P public.pem)..organization-service.yaml should have output like the following.requested. The metadata.privateKey here should be saved as configuration for your organization service application..organization-service-auth.yaml should look like the following.metadata.vault_access_token should be saved as configuration for your organization service application. So from now your application has a vault_access_token and a private_key, these should be set as configuration variables. But how do we use them.keypair_external_id can be left blank in this case if we are using the same public key to connect with all users. In some cases you may wish to use a unique public key for each user connection, in this case you should store the related private key somewhere with reference to the user who you are connecting to.encrypted_recipient_name is a record to be used by your organization only, it should identify in some way who the invitation has been created for. It should encrypted and serialized using a Cryppo serialization format (see https://github.com/Meeco/cryppo-js for more details).public_key here can be unique per connection but in this case we are just going th use the keypair from the organization service.Authorization header here should be the vault_access_token from the .organization-service-auth.yaml from above. To convert the public_key into the format needed for betlow you can use yq (https://mikefarah.gitbook.io/yq/) like so cat .organization-service.yaml | yq -j eval.invitation.json file should have output that looks something like.public_key somewhere that we can use for this connection for Dave, dave might use the meeco keystore to manage this but in this case lets forget about the keystore for now to keep it simple.keypair_external_id would be a reference for Dave to retrieve the appropriate keypair (when using the keystore this would be the id of the key record) but we can just put the name of the organization service in there for this reference.invitation_token here would be .invitation.token from the invitation.json file.Authorization here should be Dave's authorization token (from .dave.yaml).connection.json will look something like.OrganizationService has now made it's first connection with a user.