Configuration
- David Claudia
On this page
Configuring the app settings
Follow these steps to configure the app settings:
Log on to Jira as an administrator
Go to Administration > Documents
Click Settings under Documents App Configuration.
On the Settings tab, change the settings to suit your preferences. See the table below for a complete description of the available settings.
Click Save to apply the changes.
The table below shows details about the available settings.
Setting | Description |
|---|---|
Maximum file size | The maximum size allowed for an uploaded file, in MB. |
Columns displayed in list view | Choose which columns are to be displayed in the list view. These settings affect all users. The Type and Title columns are always displayed, that's why they cannot be unchecked. |
Configuring the app permissions
You can restrict access to the "Documents" tab or restrict specific privileges (create, edit, delete, move) regarding documents or folders through the app permissions configuration. Follow these steps to configure the app permissions:
Log on to Jira as an administrator
Go to Administration > Documents
Click Permissions under DOCUMENTS APP CONFIGURATION
On the Permissions tab, check the actions that you want to allow for each project role. See the table below for a complete description of the available permissions.
The table below shows details about the available permissions.
Permission | Description |
|---|---|
View | Check this option if you want the project role members to view and download the documents posted on the “Document” tab. The Documents tab will be hidden for users who do not have this permission. |
Create | Check this option if you want the project role members to be able to add documents and folders. The “Add Document” button will be hidden for users who do not have this permission. |
Edit | Check this option if you want the project role members to be able to edit documents and folders or to restore previous versions of the documents. The “Edit” option will be hidden for users who do not have this permission. |
Delete | Check this option if you want the project role members to be able to delete documents and folders. The “Delete” option will be hidden for users who do not have this permission. |
Move | Check this option if you want the project role members to be able to move documents and folders to another folder. The “Move” option will be hidden for users who do not have this permission. |
Unlock | Check this option if you want the project role members to be able to Unlock editing for specific documents and folders. The “Unlock” option will be hidden for users that do not have this permission, but it is always offered to the user who locked the document regardless of this setting. |
Set Permissions | Check this option if you want the project role members to be able to restrict access to specific documents and folders or to deny specific operations (View, Edit or Delete) for specific users or groups by setting permissions over individual documents and folders. See more about how users can set permissions over individual folders and documents in the section Setting permissions over individual folders and documents. The permissions set by the users over individual documents and folders are within the limits of the system-wide permissions that you set here. |
If you want the document creator to be able to set permissions over his/her individual documents and folders regardless of his/her project role, check The document creator can always set permissions over own documents and folders.
If you want only the document creator to be able to set permissions over documents and folders, then check Only the document creator can set permissions over documents and folders.
IMPORTANT:
When checking Only the document creator can set permissions over documents and folders, the settings from the Set Permissions column become obsolete as they are all unchecked automatically.
Click Save to apply the changes.
If a Jira user is a member of a project role that has specific permission but is also a member of another project role that does not have that permission, it is considered that the user in question has that permission.
The Project Lead has full privileges and can perform all the actions on the project's documents.