SOURCE_URL: https://majikah.solutions/products/majik-signature/docs/ms-contacts-documentation --- title: "Contacts" id: "ms-contacts-documentation" group: "majik-signature" type: "products" version: "1.2.0" lastUpdated: "2026-09-19T00:00:00.000Z" difficulty: "Beginner" time: "4-6 minutes" tags: [contacts, public-keys, signature-verification, multi-signature, identity] --- # Contacts > Learn how to import, manage, organize, and use contacts for signature verification and multi-signature files. ## Overview Contacts let you save other people's public keys for reuse across Majik Signature. A saved contact can be used as a verification key when checking signatures or assigned as an expected signer when creating multi-signature files. ### Understanding Contacts Contacts are saved records of other people's public keys. They let you keep a reusable reference to someone's signing identity without storing any private keys. Once a contact is saved, you can use their public key to verify signatures or assign them as an expected signer for a file. > **NOTE:** Contact management is available under Identity → Contacts. ### What Can You Use Contacts For? Contacts are primarily used for two signature workflows: verification and multi-signature files. During verification, Majik Signature can compare a file's signature against a public key saved in your Contacts. When preparing a multi-signature file, you can assign one or more contacts as expected signers so their public keys are associated with the required signatures. ### Contact Use Cases | Use Case | How Contacts Are Used | | --- | --- | | Signature Verification | Use a saved contact's public key to verify a signature against a known signing identity. | | Expected Signer | Assign a contact to a file as one of its expected signers. | | Multi-Signature Files | Add multiple contacts as expected signers when a file requires signatures from more than one person. | | Key Reuse | Save a public key once and reuse it across future verification and signing workflows. | *Caption: The main ways contacts are used throughout Majik Signature* ### What a Contact Contains A contact contains public identity information needed to identify and verify a signer. Contacts do not contain your private keys or another person's private keys, and adding someone as a contact does not give you the ability to sign on their behalf. ### A Contact Is Not Automatically Trusted > ⚠️ **WARNING:** Saving a public key as a contact does not by itself prove that the key belongs to the person you expect. Before relying on a contact for important verification or signature requirements, make sure the public key was obtained from a source you trust and belongs to the intended signer. ### Add a Contact 1. **Open Contacts** *Go to your saved public keys* - Open Identity from the main navigation - Select the Contacts sub-tab - Click the Add Contact button 2. **Choose an Import Method** *Add the signer's public key* - Paste their Invite Key into the contact import field, or - Import their contact card PNG if they shared one with you 3. **Confirm the Contact** *Save the public-key record* - Review the contact information shown by Majik Signature - Confirm the import to save the contact - The contact will appear in your Contacts list and can be used in supported signature workflows ### Importing with an Invite Key An Invite Key is a shareable representation of a user's public signing identity. Ask the signer to provide their Invite Key, then paste it into the Add Contact flow. This lets you save their public key without requiring access to their private keys. ### Importing a Contact Card PNG Contacts can also be exchanged as a contact card PNG. When someone shares their contact card, use the PNG import option in the Add Contact flow to load the encoded contact information into Majik Signature. > **NOTE:** Invite Keys and contact cards are intended to share public identity information. They do not expose the signer's private signing keys. ### Using Contacts as Expected Signers Contacts become especially useful when a file requires signatures from specific people. You can assign one or more saved contacts as expected signers. Each expected signer represents a public key that can later be checked against a corresponding signature on the file. ### Create a Multi-Signature Requirement 1. **Choose the File** *Open the file signature workflow* - Open the file you want to sign - Enter the workflow for configuring its signature requirements 2. **Add Expected Signers** *Select people from Contacts* - Choose the option for adding or managing expected signers - Select a contact from your saved Contacts - Repeat the process for each additional signer required by the file 3. **Review the Signer Set** *Confirm the required public keys* - Review the contacts assigned to the file - Make sure each expected signer corresponds to the intended public signing identity - Save or continue with the file signing workflow > **NOTE:** A file can have multiple expected signers. Each signer is associated with a specific public key, allowing signatures to be verified against the identities defined for that file. ### Using Contacts for Signature Verification When verifying a signed file, a saved contact can provide the public key used to identify the signer. This is useful when you already know the signer and want verification to be performed against a previously saved key rather than manually supplying the key each time. ### Verify a Signature Against a Contact 1. **Open Verification** *Start the file verification workflow* - Open the signed file in Majik Signature - Start the signature verification process 2. **Select the Contact** *Use a stored public key* - Choose the contact whose public key corresponds to the expected signer - Majik Signature uses the saved public key as the verification reference 3. **Review the Result** *Confirm the signature identity* - Review the verification result - Confirm that the signature corresponds to the expected public key - For multi-signature files, repeat the process for the applicable expected signers ### Organizing Contacts with Groups Groups help organize contacts when you work with many signers. You can create groups for teams, organizations, projects, or other sets of signing identities and use them to keep your Contacts list easier to manage. ### Manage Contact Groups 1. **Open Groups** *View your contact organization* - Open Identity → Contacts - Locate the Groups section - The default Favorites group is available for frequently used contacts 2. **Create or Edit a Group** *Organize your contacts* - Create a new group to organize a specific set of contacts - Select an existing group to filter its members - Use the group management controls to rename it, update its details, manage members, or delete it ### Rename a Contact 1. **Locate the Contact** *Find the contact you want to rename* - Open Identity → Contacts - Find the contact you want to update - Hover over the contact to reveal its actions 2. **Update the Display Name** *Customize how the contact appears to you* - Click the edit/pencil icon - Enter the new display name - Save the changes > **NOTE:** Renaming a contact only changes how that contact is displayed in your local Contacts list. It does not modify the signer's account, public key, or identity. ### Remove a Contact 1. **Locate the Contact** *Find the contact you want to remove* - Open Identity → Contacts - Find the contact you want to remove - Hover over the contact to reveal its actions 2. **Remove the Contact** *Delete the saved public-key record* - Click the delete icon - Confirm the removal when prompted - The contact will be removed from your local Contacts list ### Removing a Contact > ⚠️ **WARNING:** Removing a contact deletes its saved record from your Contacts list. It does not revoke the signer's key, invalidate their signatures, or modify the original identity. However, you will no longer be able to select that contact as a stored public-key reference until you add it again. ### Quick Reference: Contact Actions | Action | Purpose | Requirement | | --- | --- | --- | | Add Contact | Save another user's public key to your Contacts list | Invite Key or contact card PNG | | Verify with Contact | Use a stored public key when verifying a signature | Existing contact | | Add Expected Signer | Associate a contact with a file's required signer set | Existing contact | | Create Multi-Signature File | Assign multiple contacts as expected signers | One or more existing contacts | | Manage Invites | View and manage incoming or outgoing contact invites | Contacts access | | Create Group | Organize contacts into a logical collection | Contacts access | | Rename Contact | Change the local display name | Existing contact | | Remove Contact | Delete the saved contact record | Existing contact | *Caption: Common contact tasks and what they are used for* ### Contacts vs. My Keys My Keys contains your own signing identities and the private key material required to create signatures. Contacts contains other people's public signing identities for reference. Your private keys remain associated with your own identities; contacts only provide the public information needed to identify and verify other signers. ### Verify the Identity Behind the Key > ⚠️ **WARNING:** Cryptographic verification confirms that a signature matches a specific public key. It does not by itself confirm that the public key belongs to the person, organization, or account you intended to trust. For sensitive workflows, independently confirm the public key or contact information before adding it as an expected signer or relying on it for verification.