What Is a Document Vault? Definition and Jira Context
A document vault is a storage area whose access list is managed separately from the system around it. That separation is the whole idea. Being able to see the container does not mean being able to see what is inside it.
That is what distinguishes a vault from a folder. A shared folder is visible to everyone who has the link or sits in the right part of the tree. A vault has its own list, and being outside that list means the contents are not merely locked, they are not visible at all.
What the term means in Jira
Inside Jira the term has a specific meaning: a second attachment area on an issue or work item, visible only to a configured group.
This exists because of how Jira handles files natively. A normal Jira attachment inherits the permissions of the item it is attached to. If you can see the item, you can see and download every file on it. There is no per-attachment permission and no way to separate the two.
That model is fine for screenshots on a bug report. It becomes a problem when the file is a contract, a candidate’s salary expectations, an invoice, or anything containing personal data, and the item needs to stay visible to a wider team.
A document vault splits those two things apart:
- The item stays open to everyone who needs to track the work.
- The files stay closed to everyone outside the vault’s access list.
People outside the list see no panel, no files, and no file names. That last part matters more than it first appears, because a file called redundancy-consultation-notes.docx communicates the situation whether or not anyone can open it.
What a document vault is not
It is not a document management system. A DMS is a platform: libraries, retention policies, approval workflow, full version control, records management. A vault is narrower, and mostly about access control. What a vault inside Jira does that a DMS cannot is keep documents attached to the work item they belong to, so the file and its context stay together.
It is not encryption. Encryption protects data from someone who gets hold of the underlying storage. A vault controls which logged-in users can see files through the application. They solve different problems and are often used together. Most teams searching for a vault need the access control.
It is not per-file permissions. This is the most common misunderstanding, so it is worth being blunt: in the Jira implementations available today, the access list applies to the vault as a whole, not to individual files inside it. You are separating “who sees the work” from “who sees the documents”. You are not giving each document a different audience.
How access is usually configured
In Document Vault for Jira, access is granted to:
- Specific user groups
- Specific project roles
- Users named in single or multi-user custom fields
- Users in single or multi-group custom fields
- The item’s Reporter, Assignee, or Creator
Each of those can be granted full access (view, upload, edit, delete) or read-only. The custom field options are the ones people tend to overlook, and they are useful: they let access follow the work rather than a static list. If the item names a specific legal reviewer in a user field, that reviewer gets access to that item’s vault without anyone updating a group.
When you actually need one
You need this if the people who should see the work and the people who should see the files are different groups.
Some concrete cases:
- Hiring. The recruitment team and hiring manager see the candidate documents; interviewers see the process but not the salary expectations or reference checks.
- Legal. A matter is tracked by a wider team; the contract itself is visible only to legal.
- Finance. A procurement request is visible to the requester and approvers; the bank details and signed agreements are not.
- Support. A customer ticket is visible to the whole support team; files containing that customer’s personal data are restricted.
- Regulated industries, where “who could have accessed this file” is a question that gets asked during an audit, and “everyone who could see the ticket” is not a comfortable answer.
If those two groups are the same in your case, you do not need a vault. Put the sensitive work in its own project with a tight permission scheme and stop there.
Frequently asked questions
What is a document vault? A document vault is a storage area whose access list is managed separately from the surrounding system. The defining characteristic is that being able to see the container does not mean being able to see the contents. A shared folder gives access to everyone with the link; a vault requires you to be on its list.
What is a document vault in Jira? In Jira it means a second attachment area on an issue or work item, visible only to a configured group. Everyone on the team can see and work the item, while the files inside the vault are visible only to the people on its access list. Native Jira attachments do not work this way: they are visible to everyone who can see the item.
How is a document vault different from a document management system? A DMS is a full platform with libraries, workflow, retention policies, and version control. A document vault is narrower: it is about access control on a set of files. A vault inside Jira keeps documents next to the work they belong to, which a separate DMS cannot do.
Is a document vault the same as encryption? No, though the two are often combined. Encryption protects data from someone who obtains the underlying storage. A vault controls which logged-in users can see the files through the application. You can have either without the other, and most teams asking about vaults need the access control.
Do I need a document vault? If the people who need to see your work and the people who should see the attached files are the same group, no. If they differ, and the files contain personal, financial, or contractual information, then yes, because native Jira attachment visibility follows item visibility with no way to separate them.
See also: Jira document management · Jira attachment permissions explained · How to restrict Jira attachments to specific users · Attachment in the Jira glossary.