Skip to content

File Upload ๐Ÿ“’ โ€‹

File upload allows you to upload digital files to Jamku server. \

Use Case for "File Upload" module โ€‹

  1. Permatently store final documents. ๐Ÿ’ก File archiving solution.
  2. Knowledge Base. ๐Ÿ’ก Team members can refer to the previous documents as and when required in a centralised.
  3. Share documents with Clients. ๐Ÿ’ก Clients can download documents using Client Portal.
  4. Backup Solution. ๐Ÿ’ก At end of the client engagement (completing task), upload all documents in Jamku.
  5. Proof of delivery/execution. ๐Ÿ’ก You may be required by law to store and preserve your working papers.

Features โ€‹

  1. There are 3 ways to upload files:
    • Drag & Drop
    • Select File/s
    • Camera (On mobile device only)
  2. Drag & drop supports folder & sub folders. All the files inside the folder is uploaded.
  3. Automatic verisoning System. If the file name matches with the existing file, the new file is condiered next verison of the previous file.
  4. Preview files directly in Jamku, without the need to download files
    Currently supported extentions: xls, xlsx, ppt, pptx, doc, docx,png, jpeg, jpg, gif, webp
  5. Uploaded documents can be categorised using file category.
  6. Clients "can" be provided access to download the files. ๐Ÿ‘ท Currenty clients can only download files uploaded at Task Level.

Technicals โ€‹

  1. Max file upload size for a single file is 100 Mb.
  2. All file extentions supported except exe, bat, msi, cmd. However a file without extention is now allowed.
  3. Images uploaded are automatically resized to 1080 X 1080, preserving the aspect ratio. This is done to save storage cost & improve preview time.
  4. There is no limit on total number of files or total storage used. See pricing for details on how it's billed.
  5. AWS is used to store all the files uploaded through Jamku. Superfast uploads and downloads; utilising maximum available bandwidth.

File Permissions โ€‹

File Upload permission โ€‹

The file upload permission is dependent on "where" you are uploding the document

  1. Client
    Requires File AND Master permission
    ๐Ÿ‘‰ File:Yes AND Master:Yes - Allowed to upload for all clients
    ๐Ÿ‘‰ File:Self AND Master:Self - Allowed to upload for "assigned" clients
    ๐Ÿ‘‰ File:No OR Master:No - Not allowed

  2. Task
    Requires File AND TaskEdit permission
    ๐Ÿ‘‰ File:Yes AND TaskEdit:Yes - Allowed to upload for all Tasks
    ๐Ÿ‘‰ File:Self AND TaskEdit:Self - Allowed to upload for "assigned" Tasks
    ๐Ÿ‘‰ File:No OR TaskEdit:No - Not allowed

  3. Sub Task
    Requires File AND SubTaskEdit permission
    ๐Ÿ‘‰ File:Yes AND SubTaskEdit:Yes - Allowed to upload for all SubTasks
    ๐Ÿ‘‰ File:Self AND SubTaskEdit:Self - Allowed to upload for "assigned" SubTasks
    ๐Ÿ‘‰ File:No OR SubTaskEdit:No - Not allowed

  4. Service
    Requires File AND Admin permission
    ๐Ÿ‘‰ File:Yes AND Admin:Yes - Allowed to upload
    ๐Ÿ‘‰ File:No OR Admin:No - Not allowed

File View/ Preview/ Download permission โ€‹

The file upload permission is dependent on "where" you are uploding the document

  1. Client
    Requires File permission
    ๐Ÿ‘‰ File:Yes - Allowed for all clients
    ๐Ÿ‘‰ File:Self - Allowed for "assigned" clients
    ๐Ÿ‘‰ File:No - Not allowed

  2. Task
    Requires File permission
    ๐Ÿ‘‰ File:Yes - Allowed for all tasks
    ๐Ÿ‘‰ File:Self - Allowed for "assigned" tasks
    ๐Ÿ‘‰ File:No - Not allowed

  3. Sub Task
    Requires File permission
    ๐Ÿ‘‰ File:Yes - Allowed for all subtasks
    ๐Ÿ‘‰ File:Self - Allowed for "assigned" subtasks
    ๐Ÿ‘‰ File:No - Not allowed

  4. Service
    Does not require any permission - Allowed for all services

File Delete permission โ€‹

Deleting any files requires Delete:Yes permission.