Skip to main content

Feature Requests

Help shape the future of Torvus Security by suggesting and voting on new features.

How to Submit a Feature Request​

1. Search Existing Requests​

Before submitting, check if your idea already exists:

= Public Roadmap: View and vote on feature requests

Benefits of voting:

  • We prioritize features with most votes
  • Get notified when feature ships
  • Join discussion with other users

2. Submit Your Idea​

Email: feedback@torvussecurity.com

Include:

  • Feature Name: Short, descriptive title
  • Problem: What problem does this solve?
  • Proposed Solution: How should it work?
  • Use Case: Real-world example
  • Priority: How important is this to you? (Critical / High / Nice-to-have)

Example Feature Request:

Feature Name: Vault Templates

Problem:
Creating multiple vaults with similar structure is time-consuming.
I have to manually configure recipients, policies, and folders
for each new vault.

Proposed Solution:
Allow users to save vault configurations as templates.
When creating a new vault, option to "Use Template" to
pre-populate recipients, policies, and folder structure.

Use Case:
As an attorney, I create a new case vault for each client.
Each vault needs the same recipients (paralegal, client,
court reporter) and same folder structure (Pleadings,
Discovery, Correspondence). A template would save 10+ minutes
per vault.

Priority: High (would save hours per week)

3. Track Your Request​

We'll respond within 7 days with:

  • Acknowledgment and tracking ID
  • Initial assessment (under consideration / planned / declined)
  • Estimated timeline (if planned)

Feature Request Lifecycle​

1. Submitted​

Your request is received and assigned a tracking ID.

2. Under Review​

Product team reviews feasibility and impact. Timeline: 7-14 days

3. Status Update​

  • Planned: Feature added to roadmap with estimated quarter
  • Under Consideration: Interesting but needs more research
  • Declined: Doesn't align with product vision (explanation provided)

4. In Development​

Feature is actively being built. Updates: Monthly progress updates via email

5. Beta (Optional)​

Selected users invited to test feature. Sign up: beta@torvussecurity.com

6. Shipped​

Feature released to production! Notification: Email announcement when live

What Makes a Good Feature Request?​

 Good Examples​

Example 1: Specific Problem

Feature: Email Notification Customization

Problem: I receive too many check-in reminders (3, 2, 1 day before).
I only want one reminder 1 day before.

Solution: Allow users to customize reminder frequency in
Settings � Notifications � Check-in Reminders.

Use Case: I check my email daily, so 3 reminders are excessive.

Example 2: Clear Use Case

Feature: Vault Sharing with Expiration

Problem: I want to share a vault temporarily with my accountant
during tax season, but don't want to manually remove them later.

Solution: When adding a collaborator, option to set expiration
date. Access automatically revoked after date.

Use Case: Share tax documents Jan-Apr, auto-remove access May 1.

L Vague Examples​

Too Vague:

"Make the app better"
"Add more features"
"Improve security"

Too Broad:

"Add AI to everything"
"Build a mobile app" (we need specifics: what features?)

Feature Categories​

Security Features​

  • Enhanced encryption options
  • Additional MFA methods
  • Security audit improvements

User Experience​

  • UI/UX improvements
  • Mobile responsiveness
  • Accessibility enhancements

Vault Management​

  • Advanced organization features
  • Batch operations
  • Templates and presets

Policy Features​

  • New release policy types
  • Policy scheduling
  • Conditional policies

API & Integrations​

  • New API endpoints
  • Third-party integrations
  • Webhook enhancements

Enterprise Features​

  • SSO integrations
  • Advanced admin controls
  • Compliance features

Current Roadmap​

Q4 2025 (Oct-Dec)​

Planned:

  •  Enhanced security documentation (shipped Oct 8)
  • � WebAuthn (hardware security keys)
  • � Mobile app (iOS beta)

Under Consideration:

  • Vault templates
  • Advanced search
  • Bulk document upload

Q1 2026 (Jan-Mar)​

Planned:

  • Bug bounty program launch
  • SOC 2 Type II certification
  • API v2 (breaking changes)

Under Consideration:

  • Android mobile app
  • Two-person approval (4-eyes principle)
  • Vault audit reports

Q2 2026 (Apr-Jun)​

Planned:

  • ISO 27001 certification
  • Enterprise SSO (Okta, Azure AD)
  • Advanced analytics dashboard

Future / No Timeline:

  • Blockchain integration
  • End-to-end encrypted group chat
  • AI-powered document analysis

View full roadmap: roadmap.torvussecurity.com

Voting on Features​

How Voting Works​

  1. Visit Public Roadmap
  2. Browse features or search
  3. Click "Upvote" on features you want
  4. Add comments with additional context

Voting Weight​

Account TypeVotes
Free5 votes
Pro10 votes
Business20 votes per user
EnterpriseUnlimited

Pro Tip: Use votes strategically on features that matter most to you.

Feature Request FAQ​

How long does it take to build a feature?​

Depends on complexity:

  • Small: 1-2 weeks (UI tweaks, settings additions)
  • Medium: 1-3 months (new policy types, integrations)
  • Large: 3-12 months (mobile app, major infrastructure)

Will my feature definitely be built?​

Not guaranteed. We prioritize based on:

  • Number of votes
  • Strategic alignment
  • Technical feasibility
  • Resource availability
  • Security implications

Can I sponsor a feature?​

Enterprise customers: Yes! Contact sales@torvussecurity.com to discuss custom feature development.

Other plans: Features are prioritized by community votes.

Why was my request declined?​

Common reasons:

  • Security risk: Feature would compromise security
  • Out of scope: Doesn't align with product vision
  • Technical limitation: Not currently feasible
  • Low demand: Very few users would benefit

We always provide explanation for declined requests.

Can I help build a feature?​

Open source contributions: Some components are open source. Check github.com/torvus-security.

Beta testing: Sign up at beta@torvussecurity.com to test new features early.

Feature Request Examples (Shipped)​

Recently Shipped (2025)​

Q3 2025:

  •  Bulk recipient management (requested by 127 users)
  •  Dark mode (requested by 89 users)
  •  API rate limit increases for Business plan (requested by 45 users)

Q2 2025:

  •  Vault pause during travel (requested by 203 users)
  •  Multi-language support (ES, FR, DE) (requested by 156 users)
  •  Audit log export (requested by 78 users)

Q1 2025:

  •  Two-factor authentication required (requested by 312 users)
  •  Vault folders and organization (requested by 234 users)
  •  Email notification customization (requested by 167 users)

Alternative Feedback Channels​

Product Feedback Survey​

Quarterly survey: We send product feedback surveys every quarter.

  • Takes 5-10 minutes
  • Directly influences roadmap
  • $50 Amazon gift card raffle

User Interviews​

30-minute video call with product team:

  • Share your use case and needs
  • Provide early feedback on prototypes
  • $100 compensation for your time

Sign up: research@torvussecurity.com

Community Forum (Coming Soon)​

Launching Q1 2026:

  • Discuss features with other users
  • Share tips and best practices
  • Vote and comment on requests
  • Connect with Torvus team

Contact​

Feature Requests: feedback@torvussecurity.com Roadmap: roadmap.torvussecurity.com Beta Program: beta@torvussecurity.com User Research: research@torvussecurity.com

Last Updated: October 8, 2025