VaultGuard Sync (Cloud): getting started

This is the default setup path for teams using the managed VaultGuard service. There is no server to deploy, no AWS account to configure, and no Terraform or terminal command to run.

What you need

• An Obsidian desktop installation supported by VaultGuard Sync.
• An email address you can verify.
• If you are joining an existing team, the organization slug and invitation sent by your administrator.
• If you are creating a team, an organization name and a password that meets the policy shown during signup.

Choose your starting point

Create a new organization

1. Open VaultGuard Cloud signup.
2. Enter the organization name, organization slug, administrator details, and password.
3. Complete email or human verification when prompted.
4. Sign in to the web admin panel.
5. Complete the managed-plan activation shown in the panel. The current 14-day Pro trial requires a payment method at checkout.

Signup creates the organization and its first vault. You do not create or configure any cloud infrastructure.

Join an existing organization

1. Open the invitation from your VaultGuard administrator.
2. Follow the password-setup or Obsidian invitation link.
3. Complete two-factor enrollment when the organization requires it.
4. Save recovery codes in a password manager. Do not place them in the vault they protect.

VaultGuard never emails a password. Treat any message containing one as suspicious.

Install VaultGuard Sync in Obsidian

1. Open Settings → Community plugins.
2. Choose Browse.
3. Search for VaultGuard Sync.
4. Choose Install, then Enable.
5. Confirm that the VaultGuard shield appears in the left ribbon.

If you previously installed VaultGuard manually, keep one plugin directory only. Disable or remove the older copy before enabling the Community plugins version.

Sign in from the VaultGuard shield

1. Select the new VaultGuard shield in the left ribbon.
2. Choose Log in or Log in again.
3. Enter the organization slug, email, and password.
4. Complete two-factor authentication when prompted.
5. Allow VaultGuard to bind this local Obsidian folder to an eligible cloud vault.

When one eligible vault exists, VaultGuard can select it automatically. When several exist, choose the intended vault. If none appears, ask an administrator to grant you vault membership.

Verify the connection safely

Use a disposable note before adding real company knowledge:

1. Create a note named VaultGuard test.
2. Add a short, non-sensitive line and save it.
3. Open the VaultGuard shield and run Sync now.
4. Confirm the connection status reports that the vault is connected.
5. Ask a teammate with a different role to open the same note.
6. Confirm their visible actions match the access you intended.
7. Delete the disposable note after the test.

VaultGuard synchronizes while Obsidian is active. It is not a live co-editing engine, and a suspended or closed Obsidian app does not continuously sync in the background.

Next steps for organization owners

Continue with Cloud administration to invite users, grant vault membership, define folder or file rules, review audit activity, and configure recovery. Cloud administrators use the web panel; they do not use deployment commands.

Next steps for members

• Using VaultGuard in Obsidian
• Permissions and share links
• AI Chat and agent access
• Cloud security and privacy

Common problems

Problem	What to check
The shield is missing	Confirm VaultGuard Sync is enabled under Community plugins, then restart Obsidian.
Organization not found	Re-enter the lowercase organization slug supplied by your administrator.
Invalid email or password	Use Forgot password? or ask the administrator to confirm the invited email address.
No vault is available	The account exists, but it has not been added to an active vault. Ask a vault administrator for membership.
The wrong vault opened	Run VaultGuard Sync: Pick or switch server vault and select the intended vault.
Changes have not appeared	Keep Obsidian open, check the connection status, then run Sync now. Do not edit the same note concurrently during the test.
Access is denied	The connection is working, but the vault role or a path-specific permission does not allow that action.

If the problem persists, contact support@vaultguard.cloud without sending passwords, recovery codes, note contents, payment details, or unredacted audit screenshots.