BlindVault User Guide

This guide is written for everyday users. You do not need technical knowledge to use it.

You will learn how to:

After sign-in, you land on the main app. The left menu is your main navigation. The upper-right menu gives quick access to your profile, settings, language, theme, and notifications. The root dashboard is a neutral home with a combined Today summary, compact trend graphics, and recent activity across both workspaces.

Menu items:

The bell icon in the upper-right shows unread notifications for invitations, completed requests, and team updates. Open it to jump straight to the related request or profile area. User-originated message notifications can also open a dedicated message thread directly. You can also mark notifications as read or unread, delete a single notification, or clear all read notifications directly from the notification menu. The header now keeps a large centered search box that opens the universal search palette with Ctrl+K, so you can jump across requests, threads, workspaces, and contacts from one place. When you first open the palette, it already shows your contact-scoped people results alongside recent requests, threads, and workspaces, so you do not need to type before opening a person. On desktop, selecting a contact in search opens a contact card with quick actions. On smaller screens, the same contact opens in its own page. On supported mobile app builds, BlindVault can also register your device for push notifications so important request updates open the related screen directly. The mobile companion app focuses on inbox, notifications, request tracking, signing or review actions, basic profile/security access, and template-first request creation rather than full desktop authoring. Long request names are shortened in tight UI areas like headers, activity cards, and tables so the layout stays usable.

Conversations now lets you create either a New thread or a New workspace from the conversation workspace create controls. New thread now opens as its own page under the thread section rather than under the generic new route. The thread and workspace create pages use the same split-pane layout as Sign requests: a large central workspace panel and a smaller right-side panel for owner, name, and participant controls. When creating a standalone thread or a new workspace, choose the owner or payer first. This can be your own account or an organisation you actively belong to. The submit action for those create pages lives in the top header, matching the Sign create flow. The participant field also uses an explicit Add participant button. Standalone message creation requires valid recipient email addresses. Workspaces under Conversations now provides shared file workspaces with editable workspace membership. Use the Workspaces item under Conversations to open the full workspace table, where you can switch between active and archived workspaces and archive, unarchive, or delete a workspace from the row menu. The workspace table uses the same compact row layout as the inbox and thread tables, so rows open directly and the overflow menu holds secondary actions. Workspace members now have roles. Editors can upload shared files and manage workspace content. Observers can view the workspace and shared files, but they cannot upload. The Conversations dashboard itself is a lightweight module landing page with direct cards for Threads, workspace access, New thread, and linked activity. It also includes a Smart filters & saved views strip and a Recent Conversation Threads table for quick browsing. The overview tiles on both the Conversations and Sign dashboards are clickable, and clicking a tile applies the matching filters to the table below. Open workspaces from the conversation navigation and create new ones from the New menu, rather than from a separate header button on the dashboard page. Workspaces are file-sharing containers for members and shared encrypted files. If you want to discuss a file, start a standalone thread and mention the workspace with its #CODE reference in the message text. You can start a signing request directly from a workspace or standalone thread. BlindVault passes that conversation context into the request editor. When a signing request is actually sent, BlindVault automatically creates one system-managed linked signing thread for that request. That linked signing thread does not replace the earlier discussion. Instead, it keeps a reference back to the source thread or workspace so pre-signing collaboration stays separate from request-specific signing discussion. The system-managed signing thread follows the signing process lifecycle, so archiving, unarchiving, and deleting the signing process also updates the linked thread automatically. On the signing request page, use Open conversation thread to jump to the linked conversation when it exists. In a workspace’s shared file area, choose files first and then upload them into the encrypted workspace file list. BlindVault shows the decrypted original filename in that list so you can tell which shared file you are opening. Shared file timestamps are shown relative, and the exact clock time appears when you hover over them. Use the Threads item under Conversations to open the full encrypted thread table, where you can switch between active and archived threads and archive, unarchive, or delete a thread from the row menu. The thread table uses the same compact row layout as the inbox table, so rows open directly and the overflow menu holds secondary actions. Each thread row has an actions menu for thread-specific shortcuts. Workspaces and threads now expose public hashtag-style references like #ABCD-EFGH in search and headers, while the app routes still accept the system UUID or the public code as an alias. In message text, you can also use #CODE to link to a workspace. If a recipient has no public key yet, the conversation is still created, an invitation email is sent, and BlindVault fills in that participant’s key automatically once it becomes available. When you open an encrypted thread, BlindVault asks you to create or unlock your own private key in an in-app passphrase dialog. It does not ask recipients for the sender’s signing-process passphrase. Workspace-linked threads are no longer part of the regular workspace workflow. Standalone threads are separate, and workspace references stay in the message text. When you add recipients on New request, BlindVault starts suggesting matching contacts after the third typed character. You can search by email address or by the contact’s first and last name. Suggestions combine registered users with recipients from signing processes you can still access. Resolvable signing-process references in message text, such as #SP-2W5S-KPSM, #S-2W5S-KPSM, or #2W5S-KPSM, open the related request as links. In new messages and thread replies, type @ to mention people from your BlindVault contact suggestions. Use the up and down arrow keys to highlight a suggestion and press Enter to insert it. BlindVault stores the mention target as metadata, even if two people share the same display name. New thread, reply, and inline edit boxes also include a basic formatting toolbar for bold, italic, strike, code, links, and simple lists. Links now render visually while you type, so the editor shows the linked label instead of raw markdown syntax. Each thread message also has its own permalink. Use Copy link on a message to reopen and highlight that exact reply later. For messages you sent yourself, BlindVault also shows inline Edit and Delete actions directly on the message card. While editing one of your own messages, you can add more files or remove existing attachments before saving. Deleting your own message opens a themed in-app confirmation dialog instead of a browser pop-up. Each thread also has a private note area in the sidebar. That note is encrypted separately and only visible to you.

The root dashboard is now a lightweight home view.

You can:

Detailed request metrics, grouped Received / Sent overview cards, and the Recent Signing Processes table now live on the dedicated Sign dashboard. Detailed encrypted thread activity, grouped Linked / Standalone overview cards, and the Recent Conversation Threads table now live on the dedicated Conversations dashboard.

Click New request in the left menu.

Drafts are requests you saved but did not send yet.

Use Drafts to:

Templates help you avoid repeating setup.

Use Templates to:

Inbox shows requests where you are a signer, reviewer, or observer.

Possible actions you may see:

If Inbox says "Nothing assigned to you yet", no action is currently required from you.

When a request finishes, observer recipients are shown as Completed instead of staying Pending.

Sent shows requests you created.

After you send a request, BlindVault opens Sent and shows the new request there even if background loading from the previous screen is still finishing.

For each request, you may be able to:

If Sent is empty, you have not sent any requests yet.

If BlindVault asks for a passphrase in a modal dialog and you cancel it, BlindVault returns you to the dashboard.

Open profile from the bottom profile area in the sidebar.

On Profile data, you can update:

Click Save Profile after changes.

Open the Signature Cards tab in Profile.

You can create, edit, and manage your visual signature card.

To create one:

To edit an existing card:

Tip: Keep one default card active for faster signing.

This tab explains available signature levels.

You may see SES, AES, and QES options depending on organization policy and legal region.

This tab shows organization memberships and invitations.

From here you can:

Active members can send on behalf of the selected organization and consume that organization’s credits. Admin access is still only required for member and role management.

Open Profile > Organisations.

Team management (inviting members, role changes, and member removal) is available on Business and above plans.

If your plan does not include this feature, you will see an inline upgrade message with an Upgrade to Business button.

From this view you can:

Open Settings > Billing.

You can:

The selected module is part of the page URL as ?module=SIGN or ?module=CONVERSATIONS, so you can bookmark a direct link to either section. Stripe checkout returns to the same module when the purchase flow completes or is canceled.

Credit behavior:

Conversations is billed separately from Sign. It uses the same tier ladder (Free, Starter, Business, Enterprise) but with workspace, thread, storage, and collaboration limits instead of signature-credit limits. Conversation actions are quota-based only. Workspaces, threads, messages, attachments, and file uploads do not consume credits. Archived workspaces do not count toward the workspace cap.

Open Settings > Security, then open the API keys tab.

API key creation is available on Business and above plans.

If your plan does not include API access, the page shows an inline upgrade message with an Upgrade to Business button.

You can:

Open Settings > Webhooks.

You can:

Open Settings > Security.

You can: