6
6clicks Roadmap & Feature Requests
6
6clicks Roadmap & Feature Requests

Create a Post

Feature Name
Description (optional)
Powered by Noora
1
Assessment Pre-fill from last year for 3rd Parties

Our poor 3rd parties are sick of doing Vendor Risk Assessments annually and having to re-key all the data in (via 6Clicks Assessment), and in 6Clicks the ability for by default the form to be pre-filled from previous vendor response would make it a much easier sell to get their current status. Allow for select fields to be excluded where we want a new response (I wouldn't use this, but some clients may). It would also mean we could analyse quickly were a vendor response has changed from last year and just look at the exceptions!

1
1
Issue/Incident Workflow Enhancement

Add the stage access and stage requirements from risk workflows to the issue/incident workflow (and other workflows that are added in future).

This would add more options to incident management and allow for mandating certain fields be completed before stage change (e.g. closure).

1
1
Distinguish Users and Groups in Custom Fields

While system fields such as “Risk owners” and “Access members” effectively differentiate between users and groups, custom fields currently lack this functionality.

To enhance user experience and reduce confusion, it would be beneficial to implement a clear indication of whether a selected value from the dropdown menu is a user or a group. This improvement would align custom fields with the existing system fields’ practice and provide a more intuitive interface.

1
2
Unified spoke user management (Hub)
Planned for next quarter (tentative)
1
2
Unified task management
Planned for next quarter (tentative)
1
1
CCM Integrations - Lacework
Planned for next quarter (tentative)
1
1
CCM Integrations - AWS
Planned for next quarter (tentative)
1
1
Pixel perfect reporting - Skipped questions (Assessments)
Planned for this quarter
1
1
Language support - Arabic
Planned for this quarter
1
1
Language support - German
Planned for this quarter
1
1
Language support - Japanese
Planned for this quarter
1
1
Permission to only view Project & Playbook tasks
Planned for this quarter

Similar to Risk Treatment Plan permissions, Admins will have an ability to grant permissions to only view Project & Playbook tasks

1
2
Automation: Assigning Controls to Risks upon RTP closure
Planned for this quarter
1
2
Hailey RBA response recommendations
Planned for this quarter
1
4
Hailey QBA response from uploaded documentation
Planned for this quarter
1
2
Hailey: Task generation for custom registers
Planned for this quarter
1
2
My task view

We need to see all the assign and completed task by default as well small dashboard when its show by stage like new, completec and open.

0
1
Ability to customise the Risk ID

Hi Team, it would be very helpful to be able to customise the Risk ID. Keeping the current option as well where it is generated by the system.

Regards,
Joe

1
1
Add additional actions to Zapier

Currently the 6Clicks Zapier integration has limited actions available.

  • Create Issue or Incident - This is available as an action in Zapier but the response returned is limited. I can see that the issues-api/1.0/issues can return more things after creation

  • Get/Update Issue or Incident - Currently there isn't a way to get or update an existing Issue or Incident in Zapier

  • Custom API Request - Some Zapier integrations have this option like Slack and Atlassian. It allows API request to any of the rest endpoint with the authentication already handled by the Integration. For example this could open up all of the 6Click Developer API endpoints to Zapier.

0
1
Bulk Delete Users

From the Users list, ability to select multiple users and delete all at once. Currently, users can only be deleted one-by-one.

2
4
QBA generation

Create QBA based on authority/control sets. Option to create question per provision/control or per short text custom field for large authorities (i.e. category)

1
2
Risk control linkages

Suggests controls from any control sets to link

0
4
Functionality that users, when generating reports, can only see the records they are allowed to access in access members and not...

Have the ability to limit the users what they could view in analytics.
For instance, if I don’t want all users to see all the risks and issues if they generate a report, it would be great for users to be able to see only the risks/ issues that they are allowed to see.
Currently, I am denying analytics for all users except administrators. But would highly appreciate to have this functioning as above.

1
1
Jira integration - control responsibilities

Just as the integration with Jira for action tracking, integrating control responsibilities into Jira would provide similar benefits in terms of efficiency and visibility.

1
3
Move Custom Fields

Can we move Custom Fields to sit between default fields, as per customer requirements?

Right now, all custom fields sit below default fields.

3