Reseller / multi-tenant management

Resellers and MSPs managing multiple client environments have no way to operate from a single parent account. They currently need separate logins and billing relationships for each client org, making it impractical to scale across their client base. There is no hierarchical account structure, no consolidated billing, and no per-user pricing model suited to reseller economics. Proposed Solution: Introduce a reseller/MSP tier with: 1. A parent account that can provision and manage child (client) organisations from a single dashboard. 2. Role-based access scoping — reseller admins can switch between client orgs without separate credentials. 3. Consolidated billing across all child orgs with per-user or per-org pricing. 4. Client-level isolation — each child org's data, users, and configurations are fully separated. 5. Optional white-labelling so the reseller can present the platform under their own brand. Acceptance Criteria: 1. A reseller can create and manage multiple client orgs from one parent account. 2. Switching between client orgs does not require separate login. 3. Billing is consolidated under the parent account. 4. Client data is fully isolated between orgs. 5. Per-user pricing is configurable at the reseller tier.

Integration Request: Framer

Tenable (Nessus) Vulnerability Scanner Integration

Request for native integration with Tenable vulnerability management platform (Tenable.io, Tenable.sc, Nessus) to automatically import vulnerability findings as detections and evidence. This would enable: - Automated vulnerability data sync from Tenable platforms - Vulnerability findings mapped to compliance controls - Asset discovery from Tenable scans - Risk scoring based on CVSS and business context - Automated evidence collection for audit readiness - Integration with existing task management and remediation workflows Tenable is a widely-used enterprise vulnerability management solution and this integration would significantly enhance OneClickComply's vulnerability management capabilities for organisations already invested in the Tenable ecosystem.

Integration Request: Confluence

Integration Request: Jira

Whitelist/Enable Sender from Quarantine

I want to be able to "enable" or whitelist a sender directly from the quarantined email view. Currently, I have to manually release (Restore) the same senders repeatedly, which is inefficient. It would be great to have a way to mark a sender as trusted so their future emails bypass quarantine.

Integration Request: Xero

Integration Request: GitHub

Integration Request: Bitbucket

Integration Request: Atlassian

OCT(OneClick Template) AI-Generated Task Templates (NDAs, Logs, Agendas) via OCS Context

Context & Problem Statement Currently, when users are assigned a task like "Prepare Management Review Agenda" or "Maintain Deletion Logs," they are left to create these documents from scratch. This causes friction and delays. We need to provide starting templates for common compliance tasks. Instead of static, one-size-fits-all files, we will leverage our OCS engine. By adding a "Generate Template" button to tasks, OCS can combine the specific requirements of the task with the organization's unique ISMS profile to instantly generate a highly tailored, draft-ready template. Acceptance Criteria (AC) Task UI Integration: Add a "Generate Template with AI" button (or similar Call To Action) on the Task Detail pane. Contextual Prompting (Backend): When clicked, trigger an OCS prompt that injects two key pieces of context: The specific Task metadata (Name, Description, Control framework). The Organization's ISMS data (to ensure the tone, scope, and specific technologies match the company profile). Generation Output: Display the OCS-generated template in an in-app rich text or markdown editor. Editing & Saving: Allow the user to edit the generated template directly in the platform and save it as "Draft Evidence" or immediately attach it to the task to mark it as complete. Supported Task Types: Ensure the prompt handles a wide variety of template requests gracefully, including but not limited to: Employee Onboarding/Offboarding Checklists NDAs Data Deletion Logs Security Testing/Pen-Test Records Management Review Agendas

Unified Notification Center and Automated Task Reminder Emails

Context & Problem Statement Currently, users have to manually hunt through the platform (Controls, Policies, ISMS) to figure out what tasks are assigned to them or what is blocking their compliance progress. This friction leads to stalled onboarding and missed deadlines. We need a dual-channel notification system—an in-app hub and automated push emails—to clearly list out their pending action items. Acceptance Criteria (AC) In-App Notification Center: Add a "Bell" icon to the global navigation bar with an unread badge counter. Clicking the bell opens a dropdown pane (or navigates to a dedicated page) listing all pending action items assigned to the user. Each notification must be actionable (clicking it routes the user directly to the specific Task, Policy, or Control). Automated Email Engine: —ALREADY HAVE THIS FEATURE— Implement a "Daily/Weekly Digest" email that summarizes overdue and upcoming tasks for each user. Implement event-driven emails (e.g., "You have been assigned a new Task by [Admin Name]"). Notification Preferences: Add a tab in the User Settings profile allowing users to toggle email notifications on/off or change their frequency (Daily vs. Weekly digest). State Management: When a task is completed in the platform, the associated notification must automatically be marked as "Read" or removed from the pending list.

Automated Reminders for Periodic Reviews (Policies, ISMS)

Context & Problem Statement Currently, users have to rely on external calendars to track recurring compliance obligations. Aqovia has explicitly requested the ability to schedule and receive in-platform reminders for recurring events, such as 6-month policy reviews and periodic ISMS data reviews. To keep customers engaged and compliant year-round, the platform needs a notification engine that prompts them to log in and perform these administrative reviews before they become overdue. Acceptance Criteria (AC) Reminder Configuration: Users must be able to set a "Next Review Date" or schedule a reminder directly on key platform modules (e.g., specific Policies, the ISMS Dashboard, or a general "Meetings/Events" tracker). Custom Intervals: Support standard compliance intervals for reminders (e.g., 1 month, 3 months, 6 months, Annually). Notification Delivery: * Generate an in-app notification when the reminder triggers. Send an automated email to the assigned owner(s) or Organization Admins (e.g., "Action Required: 6-Month ISMS Review"). Lead Time Triggers: Allow the reminder to trigger before the actual deadline (e.g., notify the user 2 weeks before the 6-month mark) so they have time to prepare. Acknowledgement / Reset: Once a review is completed, the user must be able to click a button to "Acknowledge" the reminder, which then resets the clock for the next interval.