1. SecureSafe
  2. SecureSafe Pass FAQs

SecureSafe Pass: Known Limitations in the Current Version

This article outlines the current known limitations, feature gaps, and constraints in the latest version of our product. Review these details to understand what is supported today and will be updates within the next releases.

Plan Owners Cannot Remove Users

Currently, Plan Owners cannot remove users from their team plans.

Known Issue

In version 1, Plan Owners do not have the ability to remove members from their plan. This restricts teams from managing access as roles evolve or users leave.

Impact

  • Limits team control over membership

  • Increases support requests for manual removals

  • Adds friction to access management workflows

Upcoming Improvement

Version 2 will introduce full user management capabilities for Plan Owners, including the ability to remove users directly from their plans.

 


 

Plan Owners Cannot Upgrade Plans

Plan Owners currently lack the ability to upgrade their subscription plans directly.

Known Issue

In version 1, the platform does not support in-app upgrade workflows through our shop, preventing Plan Owners from upgrading their plans.

Impact

  • Limits self-service plan management

  • Blocks potential upsell opportunities

  • Requires manual intervention via support

Upcoming Improvement

Version 2 will enable Plan Owners to upgrade their plans directly within the app, using integrated shop workflows and proper permission controls.

 


 

Only One Plan Owner Allowed

Currently, each plan can have only a single designated owner.

Known Issue

The platform supports just one Plan Owner per organization. If that person leaves or becomes unavailable, there's no built-in fallback to manage the plan.

Impact

  • Creates operational risk for teams and businesses

  • Limits continuity and shared administrative control

  • Increases dependency on support for ownership transfers

Upcoming Improvement

Version 3 will introduce support for multiple Plan Owners per organization, allowing shared administrative responsibilities and reducing operational risk.

 


 

No Grace Period or Read-Only Mode After Plan Downgrade

Users exceeding plan quotas after a downgrade are not currently restricted or warned effectively.

Known Issue

When a user downgrades to a lower-tier plan and exceeds the allowed quota, the system does not enforce limits via grace periods or read-only access. This can lead to continued overuse without appropriate billing adjustments. 

Impact

  • Users may underpay relative to actual usage

  • Lack of clear communication about quota overages

  • No enforcement mechanism to limit further consumption

Upcoming Improvement

Version 3 will introduce quota overflow handling with built-in grace periods, clear user notifications, and read-only access until usage aligns with the downgraded plan or the user upgrades again.

 


 

Account Deletion Requires Support Request

Users cannot currently delete their accounts directly through the app.

Known Issue

Account deletion is only available via manual support requests. While this process exists, it is not easily discoverable and may lead to a frustrating user experience. 

Impact

  • Increases support team workload

  • Creates friction for users trying to manage their data

  • May delay trust-building for new users evaluating the platform

Upcoming Improvement

Version 3 will include full self-service account deletion from within the app, ensuring compliance with data privacy regulations and providing a clearer, more user-friendly experience.

 


 

Incomplete Permission Enforcement in Team Safes

Team Safe actions may appear permitted in the UI but are invalidated at the backend, leading to confusion and frustration.

Known Issue

Permission enforcement for Team Safes is not fully implemented. Users with restricted roles (e.g. Viewer or Editor) may be able to initiate actions in the UI that they are not authorized to perform. These actions are blocked at the backend, but the feedback comes only after the operation is attempted.

Impact

  • Users may assume they have permissions they do not

  • Delayed feedback results in poor user experience

  • Increases confusion around access levels and expected behaviors

Upcoming Improvement

An upcoming release will enforce permission rules directly in the UI for Team Safes, based on the user's assigned role (Admin, Editor, Viewer). This will:

  • Prevent unauthorized actions from being initiated

  • Align interface behavior with the documented permission matrix

  • Reduce user frustration


 

Seat Limit Not Enforced for Professional and Business Plans

Customers can currently purchase more than the intended seat limit via self-serve.

Known Issue

The shop app does not currently enforce a maximum seat cap for Professional and Business Plans. As a result, customers can buy more than 50 seats without engaging with the sales team.

Impact

  • Bypasses intended sales-led process for larger accounts

  • Limits opportunity for tailored onboarding and upsell

  • May result in suboptimal customer experience for large teams

Upcoming Improvement

A seat cap of 50 will be enforced in the shop app for both Professional and Business Plans. Customers needing more than 50 seats will be directed to contact sales for personalized support and service.