Sensitive data shouldn’t slow collaboration in Jira
Open up Jira to people, tickets, and use cases where you’ve been limited in the past.
Sensitive data shouldn’t slow collaboration in Jira
Open up Jira to people, tickets, and use cases where you’ve been limited in the past.
Introduction to Secure Forms
Jira is used by many cross-functional teams and employees with various seniorities. Collaboration can be limited when complex processes, involving both sensitive and nonsensitive data, cannot be run through one ticket or workflow due to certain collaborators being partially restricted from some of the ticket data.
This is where Secure Forms comes in. Set visibility and access restrictions at the individual or group level. Set them for fields and attachments. This way, collaborators who shouldn’t see this information can still collaborate on the issue.
Control Access to Sensitive Information
Set field level visibility permissions at the individual, role, or group level. You don’t need to limit collaborators based on their access to sensitive/restricted information.
External Storage for Attachments
Secure Forms lets you configure different storage locations for sensitive information. Apart from the default (Jira), you can configure AWS, Google Cloud and Azure Blob Storage with custom security parameters/requirements.
Attachment Folder Management
Sensitive data has to be kept in a
secure place, right? Set up attachment categories that you apply customized download/upload access to knowledge, along with visible access to knowledge.
