/
Jira/Confluence Software Security

Jira/Confluence Software Security

Jira is the project management software Vertic use to manage projects and enhancements. Jira is broken down into projects. Often there are many projects running simultaneously for 1 client, each containing different specifications.

We manage permissions and security through Groups and Permission Schemes.

There are 3 levels of access in our Jira/Confluence environment.

  1. Administrator

    1. This provides admin access to all Vertic consultants including modification of settings and visibility of all projects

  2. Developer

    1. This provides Vertic’s technical team with access to all projects, tickets and comments, but not settings within Jira

  3. Customer

    1. This provides Customers with access only to their client project(s).

A typical project permission setup looks like this:

 

The permission settings of what Administrators, Customers and Developers can and can not see/do is configured within the Global Permissions of Jira settings. See below.

Confluence is the documentation tool we use to document our initial specifications and documentation. Only specific personnel should have access to this information and we manage this from the Jira User Record and the Confluence People settings. See below:

User record

People settings (same interface as Jira)

:

 

Related content

Vertic's Organisational Risk Register
Vertic's Organisational Risk Register
Read with this
Vertic's Organisational Change Management Process
Vertic's Organisational Change Management Process
Read with this
Quality Management System Reference Links
Quality Management System Reference Links
Read with this
Information Security Roles Responsibilities, Procedures, and Authorities
Information Security Roles Responsibilities, Procedures, and Authorities
More like this