Vault Security & Access

BugShield designed the Vault so credentials do not need to be exposed in email or ordinary chat. Items are encrypted when stored and remain associated with one site. Follow Using the Password Vault to add and maintain credentials.

Who can access a Vault item

Access is limited to authorised BugShield team members when it is needed for work on the relevant site. A developer does not need credentials for unrelated sites in your account.

Access is logged

When a Vault credential is redeemed for work, BugShield records an activity event. Use the site’s Activity Log to review access alongside other operational activity.

Safer credentials to share

• Check that the login details work before saving them in the Vault.
• Include the correct sign-in URL, username and any instructions needed to access the site.
• Use a unique, strong password and do not reuse it elsewhere.
• Update the Vault item whenever the login details change.
• Do not store credentials you are not authorised to share.

After work is complete

You can review the Activity Log to see when Vault access was used. If the login details change later, update the Vault item so it remains accurate.

Account security still matters

Vault encryption does not replace protecting your BugShield login. Use a unique password, enable 2FA and sign out unfamiliar sessions. See Account Security, 2FA & Active Sessions for the complete steps.