Volume Console Guide

This type creates a brand new storage volume that Namirasoft hosts for you on its own servers. Namirasoft sets aside a fixed amount of disk space and gives you a volume that is ready to use right away, with that space reserved and available whenever you need it. This option uses fixed pricing, and you can see the details on the Pricing page.

• Size (Integer) : Size is the amount of space you set aside for the volume, measured in gigabytes (GB). You type a number, for example 50 for 50 GB or 500 for half a terabyte. You choose the size that fits what you plan to store, and you can create a larger volume later whenever you need more room.

This type creates a brand new storage volume that Namirasoft hosts for you on its own servers. The volume grows to fit your data, so the space it uses expands as your files grow, up to a limit you set. You choose this when your storage needs change over time and you want the volume to scale with them. This option uses usage based pricing, and you can see the details on the Pricing page.

• Size (Integer) : Size is the upper limit you set for the volume, measured in gigabytes (GB). You type a number, for example 100 for 100 GB. Your files can grow up to this limit, so you set it high enough to give your data room to expand.

This type gives you object storage that Namirasoft creates and hosts for you, reached through the same tools you would use for Amazon S3. Object storage keeps your files as objects in a bucket, which suits backups, uploads from an application, and large collections of files. Namirasoft provides the access details you enter below when your bucket is set up, so you do not bring them from another provider.

• Provider (Enum) : This tells the system which service runs the bucket. You select the Namirasoft option, since Namirasoft hosts this bucket for you.
• Access Key ID (String) : This is the public part of the key pair that identifies your bucket, much like a username. Namirasoft provides it when your bucket storage is set up, and you enter it here.
• Secret Access Key (String) : This is the private part of the key pair that authorizes access, much like a password. Namirasoft provides it when your bucket storage is set up. You enter it here and keep it private.
• Region (Enum) : This is the location where Namirasoft stores the bucket. Namirasoft provides the region value with your bucket details, and you enter it here.

This type connects a storage bucket you already have on Amazon S3, the cloud storage service from Amazon. Namirasoft NWS Volume does not create the bucket. It connects to the bucket you already own and reads and writes files in it for you, so your data stays in your own AWS account.

• Credential (Namirasoft Credential’s ID) : A saved AWS credential that holds your AWS access keys and lets Namirasoft NWS Volume sign in to your AWS account.
  1. In the AWS Console, open IAM, then Users, and select your user
  2. On the Security credentials tab, under Access keys, click Create access key
  3. Copy the Access key ID and the Secret access key, because the secret is shown only once
  4. In Namirasoft Credential, create an AWS credential with those two values
  5. Come back here and pick that saved credential
• Provider (String) : This is the S3 service your storage runs on, which you type in. You enter aws for Amazon S3. The same type also works with other S3 compatible services, so you type the matching name, such as Wasabi, Minio, or DigitalOcean, when your storage is on one of them.
• Region (String) : This is the region where your bucket was created, written as a short code such as us-east-1 for North Virginia or eu-central-1 for Frankfurt. You open your bucket in the AWS S3 console, read the region beside it, and type the same code here. It has to match the bucket exactly, otherwise the connection fails.

This type connects a bucket on any storage service that follows the Amazon S3 standard but does not have its own entry in this list. Many providers offer S3 compatible storage, for example Wasabi, MinIO, and DigitalOcean Spaces. You connect with an access key pair from that provider.

• Provider (String) : This is the S3 compatible service your storage runs on, which you type in. You enter the name that matches your storage, for example Wasabi, Minio, or Ceph. When your provider is not one of the known names, you enter Other.
• Access Key ID (String) : The public part of your key pair, much like a username. One access key gives you both the Access Key ID and the Secret Access Key. The steps depend on your provider:
  Wasabi
  1. In the Wasabi console, click Access Keys
  2. Click Create Access Key, choose Root User or Sub User, then click Create
  3. Copy the access key; click Show to reveal the secret key
  DigitalOcean Spaces
  1. In the DigitalOcean Control Panel, click Spaces Object Storage
  2. Open the Access Keys tab, then click Create Access Key
  3. Name it and click Create Access Key, then copy the access key and its secret (the secret is shown only once)
  MinIO
  1. In the MinIO Console, click Access Keys
  2. Click Create access key, then Create
  3. Copy the access key and the secret key (the secret is shown only once)
  Other providers
  Open your provider’s access keys area, create a key, and copy the access key and secret. On Ceph, an administrator runs radosgw-admin user create and gives you the pair.
• Secret Access Key (String) : The private part of your key pair, much like a password. It is shown together with the Access Key ID when you create the access key above, usually only once, so copy it then and keep it private.
• Region (String) : The region where your bucket lives, written as a short code that your provider defines, for example us-east-1.
  1. Open your bucket in your provider’s console
  2. Copy the region shown next to it, for example us-east-1

This type connects a bucket you already have in Google Cloud Storage, the object storage service from Google. You sign in with your Google account through OAuth, so Namirasoft NWS Volume can reach the bucket for you. The bucket stays in your own Google Cloud project.

• Project Number (Integer) : The unique number Google gives the project that owns your bucket, for example 415104041262.
  1. Open the Google Cloud console
  2. On the dashboard, find the Project info card
  3. Copy the Project number
• Credential (Namirasoft Credential’s ID) : This is the Google sign in you saved in the Namirasoft Credential app, which lets Namirasoft NWS Volume reach your bucket. You select it here from your saved credentials. How to get a Google Cloud Storage credential?
• Location (String) : Where your bucket is stored, written as a Google region or multi region code, for example us-central1 or eu.
  1. Open Cloud Storage buckets and open your bucket
  2. Copy the Location shown on the bucket page, for example us-central1

This type connects a bucket in Google Cloud Storage using a service account, which is a robot account made for servers and automation rather than a person signing in. You give Namirasoft NWS Volume a key file for that service account, and it reaches your bucket with no one logging in.

• Service Account File (String) : The complete JSON content of the service account key file that Google Cloud creates. Keep this content confidential.
  1. Open the Google Cloud console and select the project that owns your bucket
  2. Go to IAM & Admin, then Service Accounts
  3. Click Create Service Account, enter a name, and create it
  4. Grant it access to your bucket, for example the Storage Object Admin role
  5. Open the service account and go to the Keys tab
  6. Click Add Key, then Create new key, choose JSON, and click Create
  7. Open the downloaded JSON file in a text editor, copy the entire content, and paste it here
• Project Number (Integer) : The unique number Google gives the project that owns your bucket, for example 415104041262.
  1. Open the Google Cloud console
  2. On the dashboard, find the Project info card
  3. Copy the Project number
• Location (String) : Where your bucket is stored, written as a Google region or multi region code, for example us-central1 or eu.
  1. Open Cloud Storage buckets and open your bucket
  2. Copy the Location shown on the bucket page, for example us-central1

This type connects a container in Azure Blob Storage, the object storage service from Microsoft Azure. It uses the simplest sign in: the storage account name plus one of its access keys.

• Storage Account (String) : The name of the Azure storage account that holds your data, for example mycompanydata.
  1. Open your storage account in the Azure portal
  2. Copy its name, shown at the top of the page
• Account Key (String) : A long secret string that unlocks the storage account, much like a master password. Keep it private.
  1. Open your storage account in the Azure portal
  2. Go to Security + networking, then Access keys
  3. Click Show keys, then copy key1

This type connects Azure Blob Storage with a registered application and a client certificate. Your organization registers an app in Microsoft Entra ID, the Microsoft identity service, and adds a certificate to it, and Namirasoft NWS Volume signs in as that app.

• Tenant (String) : The id of your organization’s Microsoft Entra directory, a long code of letters and numbers.
  1. In the Azure portal, search for Microsoft Entra ID and open it
  2. On the Overview page, copy the Tenant ID
• Client ID (String) : The id of the application you registered in Microsoft Entra ID, also a long code.
  1. In the Azure portal, open Microsoft Entra ID, then App registrations
  2. Open your application, or click New registration to create one
  3. On the Overview page, copy the Application (client) ID
• Client Certificate Path (String) : The location of the certificate file on the machine that runs the connection, entered as a full path so the connection can read the certificate.
  1. In the Azure portal, open your app registration and go to Certificates & secrets
  2. On the Certificates tab, click Upload certificate and upload the public certificate
  3. Keep the certificate file on the machine that runs the connection and enter its full path here, for example /etc/certs/azure.pem
• Client Certificate Password (String) : This is the password that protects the certificate file, if you set one when you created it. You enter that password here, or you leave it empty when the certificate has none.
• Send Certificate Chain (Boolean) : This setting decides whether the connection also sends the certificate’s full chain of trust during sign in. You turn it on when your Entra app requires the chain, and you leave it off otherwise.

This type connects Azure Blob Storage with a registered application together with a username and password. Your organization registers an app in Microsoft Entra ID, and Namirasoft NWS Volume signs in with that app and a saved user credential.

• Tenant (String) : The id of your organization’s Microsoft Entra directory, a long code of letters and numbers.
  1. In the Azure portal, search for Microsoft Entra ID and open it
  2. On the Overview page, copy the Tenant ID
• Client ID (String) : The id of the application you registered in Microsoft Entra ID, also a long code.
  1. In the Azure portal, open Microsoft Entra ID, then App registrations
  2. Open your application, or click New registration to create one
  3. On the Overview page, copy the Application (client) ID
• Credential (Namirasoft Credential’s ID) : A saved sign in that holds the username and password Namirasoft NWS Volume uses to sign in to your Azure account.
  1. In Namirasoft Credential, create a Basic Auth credential with your Azure account username and password
  2. Come back here and pick that saved credential

This type connects a bucket in Oracle Cloud Infrastructure Object Storage. The bucket stays in your own Oracle Cloud tenancy, and Namirasoft NWS Volume reaches it using details you read from the Oracle Cloud console.

• Provider (String) : This is the provider value for the connection, which you type in. For Oracle Cloud Object Storage you enter the standard Oracle value shown in the field help.
• Namespace (String) : A unique name Oracle gives your Object Storage, a short string of letters and numbers such as axh5sf3abc12.
  1. In the Oracle Cloud console, open the Profile menu at the top right and click Tenancy
  2. Copy the Object storage namespace shown on the tenancy page
• Compartment (String) : The folder like area in Oracle Cloud that holds your bucket.
  1. In the Oracle Cloud console, open the navigation menu and go to Identity & Security, then Compartments
  2. Copy the name of the compartment your bucket lives in
• Region (String) : The Oracle Cloud region where your bucket lives, written as a code such as us-ashburn-1 or eu-frankfurt-1.
  1. Open your bucket under Storage, then Buckets in the Oracle Cloud console
  2. Copy the region code shown for it, for example us-ashburn-1

This type connects a bucket in Backblaze B2, a cloud storage service. The bucket stays in your own Backblaze account, and Namirasoft NWS Volume reaches it with an application key you create in Backblaze.

• Account ID (String) : The public part of your Backblaze application key, which Backblaze also calls the key id, a short string of letters and numbers.
  1. Sign in to Backblaze and open Application Keys under B2 Cloud Storage
  2. Click Add a New Application Key and create the key
  3. Copy the keyID it shows
• Application Key (String) : The secret part of the pair, much like a password. Backblaze shows it only once.
  1. Sign in to Backblaze and open Application Keys under B2 Cloud Storage
  2. Click Add a New Application Key and create the key
  3. Copy the applicationKey right away, because Backblaze shows it only once
• Hard Delete (Boolean) : This setting decides what happens when you delete a file. You turn it on to remove files permanently. You leave it off to keep earlier versions available, so you can recover them later.

This type connects a bucket in QingStor object storage. The bucket stays in your own QingStor account, and you connect with an access key pair from the QingStor console.

• Access Key ID (String) : This is the public part of your key pair, much like a username. You create an API key in the QingStor console, and it shows the access key id. You copy it and enter it here. Where do I find my QingStor keys?
• Secret Access Key (String) : This is the private part of the pair, much like a password. QingStor shows it when you create the key, so you copy it then, paste it in the Secret Access Key field, and keep it private. Where do I find my QingStor keys?
• Endpoint (String) : The web address of the QingStor service for your zone. Leave it empty to use the default, or set the address that matches your zone.
  1. Leave it empty to use the default https://qingstor.com:443
  2. Or enter the address for your zone, for example https://s3.pek3b.qingstor.com
• Zone (String) : The QingStor data center where your bucket lives, written as a short code, for example pek3a (Beijing), sh1a (Shanghai), or gd2a (Guangdong).
  1. Open your bucket in the QingStor console
  2. Copy the zone code shown next to it, for example pek3a

This type connects container storage that runs on OpenStack Swift, the object storage part of OpenStack clouds. You choose it when your storage comes from an OpenStack based cloud, and you connect with the user details that cloud gives you.

• User (String) : The OpenStack username for your account, which on some clouds looks like project:username.
  1. In your OpenStack dashboard, click your user name at the top right and choose OpenStack RC File to download it
  2. Open the file and copy the value of OS_USERNAME
• Key (String) : The password for that OpenStack user, the same one you use to sign in to OpenStack. Keep it private.
  1. Use your OpenStack account password here
  2. If your provider issues a separate API key or password for storage, use that instead
• Auth URL (String) : The web address where OpenStack checks your sign in, for example https://auth.example.com/v3.
  1. In your OpenStack dashboard, download the OpenStack RC File from the user menu at the top right
  2. Open the file and copy the value of OS_AUTH_URL

This type connects a bucket on Storj, a storage network that spreads your files across many computers for durability. The bucket stays in your own Storj account, and you connect with a single access grant that you create in Storj.

• Access Grant (String) : One long text string that bundles everything Namirasoft NWS Volume needs to reach your bucket: the location, the permissions, and the encryption key.
  1. In the Storj console, click Access Keys
  2. Click New Access Key, name it, and choose Access Grant for the type
  3. Set the permissions and passphrase, then click Create Access
  4. Copy the access grant it shows, because it is not shown again

This type connects storage on Akamai NetStorage, the storage that pairs with the Akamai content delivery network. You choose it when your files live on Akamai, and you connect with the upload account details from the Akamai Control Center.

• Host (String) : The web address of your NetStorage storage group, for example yourgroup-nsu.akamaihd.net.
  1. In Akamai Control Center, go to Content delivery, then NetStorage, and open Storage Groups
  2. Open your storage group and copy the HTTP Domain Name shown in its details
• Account (String) : The upload account name that has access to the storage group.
  1. In Akamai Control Center, open Upload Accounts
  2. Copy the name of the upload account for your storage group, or click Add New Upload Account to create one
• Secret (String) : The key tied to the upload account that signs each request, much like a password.
  1. In Akamai Control Center, open your upload account and select the NetStorage HTTP CMS API tab
  2. Click Add HTTP API Key, then click Copy Key

This type connects your items on the Internet Archive, the nonprofit digital library at archive.org. You choose it to manage items you store there, and you connect with the S3 like keys from your Internet Archive account.

• Access Key ID (String) : The public part of your Internet Archive key pair.
  1. Open archive.org/account/s3.php and sign in
  2. Copy your access key
• Secret Access Key (String) : The private part of the pair, shown on the same S3 API keys page. Keep it private.
  1. Open archive.org/account/s3.php and sign in
  2. Copy your secret key
• Item Derive (Boolean) : This setting decides whether the Internet Archive runs its derive process after you upload a file. The derive process builds extra versions, such as thumbnails or alternate formats. You turn it on to let those build automatically, or off to skip them.

This type connects a file share in Azure Files, the file sharing service from Microsoft Azure that works like a shared network drive. It uses the simplest sign in: the storage account name plus one of its access keys. You choose this when you can get the storage account keys directly.

• Storage Account (String) : The name of the Azure account that holds your share, for example mycompanydata.
  1. Open your storage account in the Azure portal
  2. Copy its name, shown at the top of the page
• Account Key (String) : A long secret string that unlocks the storage account, much like a master password. Keep it private.
  1. Open your storage account in the Azure portal
  2. Go to Security + networking, then Access keys
  3. Click Show keys, then copy key1
• Share Name (String) : The name of the specific file share inside the storage account, for example documents or backups.
  1. In the Azure portal, open your storage account and go to Data storage, then File shares
  2. Copy the name of the share you want

This type connects a file share in Azure Files using a connection string, which is a single line of text that already holds the account name and key together. You choose this when you were given a connection string and prefer to paste one value instead of two.

• Connection String (String) : One line that holds the account name and key together. It begins with DefaultEndpointsProtocol=https and lists the AccountName and AccountKey values.
  1. Open your storage account in the Azure portal
  2. Go to Security + networking, then Access keys
  3. Click Show keys, then copy the Connection string under key1
• Share Name (String) : The name of the specific file share inside the storage account, for example documents or backups.
  1. In the Azure portal, open your storage account and go to Data storage, then File shares
  2. Copy the name of the share you want

This type connects a file share in Azure Files using a shared access signature, called a SAS, which is a special link that grants limited, time bound access without sharing your account key. You choose this when you want access that can expire or stay restricted.

• SAS URL (String) : A web address with a long token at the end that grants the access.
  1. Open your storage account in the Azure portal
  2. Go to Security + networking, then Shared access signature
  3. Allow the File service, choose the permissions and the expiry, then click Generate SAS and connection string
  4. Copy the File service SAS URL
• Share Name (String) : The name of the specific file share inside the storage account, for example documents or backups.
  1. In the Azure portal, open your storage account and go to Data storage, then File shares
  2. Copy the name of the share you want

This type connects a file share in Azure Files with a registered application together with a username and password. Your organization registers an app in Microsoft Entra ID, and Namirasoft NWS Volume signs in with that app plus a saved user credential. You choose this when you sign in with a user account rather than a key or a certificate.

• Tenant (String) : The id of the Microsoft Entra directory for your organization, a long code of letters and numbers.
  1. In the Azure portal, search for Microsoft Entra ID and open it
  2. On the Overview page, copy the Tenant ID
• Client ID (String) : The id of the application you registered in Microsoft Entra ID, also a long code.
  1. In the Azure portal, open Microsoft Entra ID, then App registrations
  2. Open your application, or click New registration to create one
  3. On the Overview page, copy the Application (client) ID
• Credential (Namirasoft Credential’s ID) : A saved sign in that holds the username and password that sign in to your Azure account, so you do not type the password on this page.
  1. In Namirasoft Credential, create a Basic Auth credential with your Azure account username and password
  2. Come back here and pick that saved credential
• Share Name (String) : The name of the specific file share inside the storage account, for example documents or backups.
  1. In the Azure portal, open your storage account and go to Data storage, then File shares
  2. Copy the name of the share you want

This type connects a file share in Azure Files with a registered application and a certificate instead of a key. Your organization registers an app in Microsoft Entra ID and adds a certificate to it, and Namirasoft NWS Volume signs in as that app. You choose this when your company requires certificate based sign in.

• Tenant (String) : The id of the Microsoft Entra directory for your organization, a long code of letters and numbers.
  1. In the Azure portal, search for Microsoft Entra ID and open it
  2. On the Overview page, copy the Tenant ID
• Client ID (String) : The id of the application you registered in Microsoft Entra ID, also a long code.
  1. In the Azure portal, open Microsoft Entra ID, then App registrations
  2. Open your application, or click New registration to create one
  3. On the Overview page, copy the Application (client) ID
• Client Certificate Path (String) : The location of the certificate file on the machine that runs the connection, entered as a full path so the connection can read the certificate.
  1. In the Azure portal, open your app registration and go to Certificates & secrets
  2. On the Certificates tab, click Upload certificate and upload the public certificate
  3. Keep the certificate file on the machine that runs the connection and enter its full path here, for example /etc/certs/azure.pem
• Client Certificate Password (String) : This is the password that protects the certificate file, if you set one when you created it. You enter that password here, or you leave it empty when the certificate has none.
• Send Certificate Chain (Boolean) : This setting decides whether the connection also sends the full chain of trust for the certificate during sign in. You turn it on when your Entra app requires the chain, and you leave it off otherwise.
• Share Name (String) : The name of the specific file share inside the storage account, for example documents or backups.
  1. In the Azure portal, open your storage account and go to Data storage, then File shares
  2. Copy the name of the share you want

This type connects a server over SFTP, which moves files securely over an SSH connection. You choose it for any server you can reach with SFTP, such as a Linux server or a managed file transfer service, and you sign in with either a password or a private key.

• Host (String) : The address of the server, written as a domain name such as files.example.com or an IP address such as 203.0.113.10.
  1. Ask your server administrator or hosting provider for the server address
  2. Copy it, for example files.example.com
• Port (Integer) : The port is the door on the server that accepts SFTP connections, written as a number. You enter 22, the standard SFTP port, unless your administrator told you to use a different one.
• Credential (Namirasoft Credential’s ID) : A saved sign in that holds the username and password for the server. Use this when the server signs you in with a password.
  1. In Namirasoft Credential, create a Basic Auth credential with the server username and password from your administrator
  2. Come back here and pick that saved credential
• Key PEM (String) : A private key in PEM format is a block of text that starts with a line reading BEGIN OPENSSH PRIVATE KEY and ends with a matching END line, and it proves who you are without a password. Use it when the server is set up for key based sign in.
  1. On your computer, open a terminal and run ssh-keygen, accepting or choosing a file location
  2. Add the public key, the file ending in .pub, to the server’s ~/.ssh/authorized_keys, or ask your administrator to add it
  3. Open the private key file in a text editor and paste its entire content here
• Key File (String) : Instead of pasting the key, you can point to a private key file that already sits on the machine running the connection, for example /home/user/.ssh/id_rsa. You enter the full path to that file here.
• Key File Password (String) : If your private key is protected by a passphrase, you enter that passphrase here so the key can be used. You leave it empty when the key has no passphrase.

This type connects a server over FTP, a widely supported file transfer method, with the option to add TLS encryption. You choose it for servers that use FTP, and you turn on TLS to protect the connection.

• Host (String) : The address of the FTP server, written as a domain name such as ftp.example.com or an IP address such as 203.0.113.10.
  1. Ask your administrator or hosting provider for the FTP server address
  2. Copy it, for example ftp.example.com
• Port (Integer) : The port is the door on the server that accepts FTP connections, written as a number. You enter 21, the standard FTP port, unless your administrator told you to use a different one.
• Credential (Namirasoft Credential’s ID) : A saved sign in that holds the username and password for the FTP server.
  1. In Namirasoft Credential, create a Basic Auth credential with the server username and password from your administrator
  2. Come back here and pick that saved credential
• TLS (Boolean) : This setting turns on implicit TLS, where the whole connection is encrypted from the start. You turn it on when your server expects FTP over TLS on a dedicated port, and you leave it off for plain FTP.
• Explicit TLS (Boolean) : This setting turns on explicit TLS, where the connection starts plain and then upgrades to encryption. You turn it on when your server supports FTPS on the normal FTP port, and you leave it off otherwise.

This type connects a shared folder over SMB, the protocol that Windows and Samba use for network file sharing. You choose it to reach a shared drive on a Windows server, a NAS device, or a Samba server on your network.

• Host (String) : The address of the server that hosts the share, written as a name such as fileserver or an IP address such as 192.168.1.20.
  1. Ask your administrator for the server address
  2. Copy it, for example fileserver
• Port (Integer) : The port is the door on the server that accepts SMB connections, written as a number. You enter 445, the standard SMB port, unless your administrator told you to use a different one.
• Credential (Namirasoft Credential’s ID) : A saved sign in that holds the username and password that open the share. On a Windows domain the username often looks like DOMAIN\username.
  1. In Namirasoft Credential, create a Basic Auth credential with the share username and password from your administrator
  2. Come back here and pick that saved credential

This type connects a WebDAV server, which shares files over the web, using a username and password. Many services, such as Nextcloud and ownCloud, offer a WebDAV address. You choose this when your WebDAV server signs you in with credentials.

• URL (String) : The WebDAV address of your server, for example https://cloud.example.com/remote.php/dav/files/username/.
  1. Open your service settings, or its WebDAV help page
  2. Copy the WebDAV address it shows
• Vendor (Enum) : The vendor is the kind of WebDAV server you are connecting to, picked from a list, for example Nextcloud, ownCloud, or Other. You choose the one that matches your server so the connection behaves correctly, and you choose Other when you are not sure.
• Credential (Namirasoft Credential’s ID) : A saved sign in that holds the username and password for the WebDAV server. Some services ask you to create a separate app password instead of your main password.
  1. In Namirasoft Credential, create a Basic Auth credential with your WebDAV username and password
  2. Come back here and pick that saved credential

This type connects a WebDAV server using a bearer token instead of a username and password. A bearer token is a long string that the server issues to grant access. You choose this when your WebDAV server uses token based sign in.

• URL (String) : The WebDAV address of your server, for example https://cloud.example.com/remote.php/dav/files/username/.
  1. Open your service settings, or its WebDAV help page
  2. Copy the WebDAV address it shows
• Vendor (Enum) : The vendor is the kind of WebDAV server you are connecting to, picked from a list, for example Nextcloud, ownCloud, or Other. You choose the one that matches your server, and you choose Other when you are not sure.
• Bearer Token (String) : A long string the server gives you to prove your access, used in place of a password. How you create one depends on your WebDAV service.
  1. In your WebDAV service, open its access or token settings
  2. Generate a token, then copy it and keep it private

This type reads files that are published on a website over HTTP. It is read only, so you browse and download the files that are published there. You choose it to pull files from a public web address or a static file server.

• URL (String) : The URL is the web address of the folder that lists your files, for example https://example.com/files/. You enter the address whose page shows the files you want to read.

This type connects a Hadoop Distributed File System, known as HDFS, which stores very large data sets across a cluster of machines. You choose it to reach data kept in a Hadoop cluster.

• Namenode (String) : The main server that tracks where files live in the cluster, written as an address such as namenode.example.com:8020.
  1. Ask your Hadoop administrator for the namenode address
  2. Copy it, for example namenode.example.com:8020
• Username (String) : The Hadoop account that the connection acts as, which controls what it may read and write, for example hdfs or your own user name.
  1. Ask your Hadoop administrator which user to use
  2. Enter that user name, for example hdfs

This type connects a Google Drive account so you can work with the files in it. You sign in with your Google account through OAuth, which lets Namirasoft NWS Volume reach your Drive on your behalf without you sharing a password. The files stay in your own Google Drive.

• Credential (Namirasoft Credential’s ID) : A credential is the Google sign in that lets Namirasoft NWS Volume open your Drive. You create it once by signing in with your Google account in the Namirasoft Credential app, then pick that saved credential here from a list, so you never enter a Google password on this page. How to get a Google Drive token auth credential?

This type connects Google Drive using a service account, which is a robot account meant for servers and automation rather than a person signing in. You give Namirasoft NWS Volume a key file for that service account, and it uses the file to reach the Drive on its own. You choose this for unattended or production use.

• Scope (Enum) : The scope sets how much access the service account has, picked from a list. You choose full access to read and write files, or read only when you want the connection to view files and leave them unchanged. You pick the one that matches what you need.
• Service Account File (String) : The complete JSON content of the service account key file that Google Cloud creates. Keep this content confidential.
  1. Open the Google Cloud console and select your project, or create a new one
  2. Go to APIs & Services, then Library, search for Google Drive API, and enable it
  3. Go to IAM & Admin, then Service Accounts
  4. Click Create Service Account, enter a name, and create it
  5. Open the service account and go to the Keys tab
  6. Click Add Key, then Create new key, choose JSON, and click Create
  7. Open the downloaded JSON file in a text editor, copy the entire content, and paste it here
  8. Share the Google Drive folder you want to connect with the service account email address

This type connects a Google Photos library so you can work with its photos and albums. You sign in with your Google account through OAuth, which lets Namirasoft NWS Volume reach your library on your behalf.

• Credential (Namirasoft Credential’s ID) : A credential is the Google sign in that lets Namirasoft NWS Volume open your photo library. You create it once by signing in with your Google account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a Google Photos token auth credential?
• Read Only (Boolean) : This setting keeps the connection focused on viewing. You turn it on so the connection reads and downloads your photos and leaves them unchanged. You leave it off to also let it upload new photos.

This type connects a Dropbox account so you can work with the files in it. You sign in with your Dropbox account through OAuth, which lets Namirasoft NWS Volume reach your Dropbox on your behalf.

• Credential (Namirasoft Credential’s ID) : A credential is the Dropbox sign in that lets Namirasoft NWS Volume open your Dropbox. You create it once by signing in with your Dropbox account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a Dropbox token auth credential?

This type connects a Microsoft OneDrive account so you can work with the files in it. It works with both a personal OneDrive and the OneDrive that comes with a Microsoft 365 work or school account. You sign in through OAuth.

• Credential (Namirasoft Credential’s ID) : A credential is the Microsoft sign in that lets Namirasoft NWS Volume open your OneDrive. You create it once by signing in with your Microsoft account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a OneDrive token auth credential?
• Tenant (String) : The tenant tells the connection which Microsoft organization your account belongs to. For a personal OneDrive, leave it at the default. For a work or school account, enter your organization tenant id.
  1. In the Azure portal, search for Microsoft Entra ID and open it
  2. On the Overview page, copy the Tenant ID, or ask your IT team for it

This type connects a Box account so you can work with the files in it. You sign in with your Box account through OAuth, which lets Namirasoft NWS Volume reach your Box on your behalf.

• Credential (Namirasoft Credential’s ID) : A credential is the Box sign in that lets Namirasoft NWS Volume open your Box. You create it once by signing in with your Box account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a Box token auth credential?

This type connects an iCloud Drive account so you can work with the files in it. You sign in with your Apple ID, the same account you use for other Apple services.

• Apple ID (String) : The Apple ID is the email address you use to sign in to Apple services, for example yourname@icloud.com. You enter that email address here.
• Password (String) : Because Apple protects accounts with two factor verification, you create an app specific password just for this connection rather than using your main password.
  1. Sign in at account.apple.com
  2. In Sign-In and Security, select App-Specific Passwords
  3. Click Generate an app-specific password, give it a name, and follow the prompts
  4. Copy the password

This type connects a pCloud account so you can work with the files in it. You sign in with your pCloud account through OAuth, which lets Namirasoft NWS Volume reach your pCloud on your behalf.

• Credential (Namirasoft Credential’s ID) : A credential is the pCloud sign in that lets Namirasoft NWS Volume open your pCloud. You create it once by signing in with your pCloud account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a pCloud token auth credential?

This type connects a pCloud account using your username and password. You choose it when you prefer to sign in with your account details rather than through OAuth.

• Hostname (String) : pCloud keeps accounts in two regions, and the hostname tells the connection which one yours is in.
  1. Check your region in your pCloud account settings
  2. Enter api.pcloud.com for a United States account, or eapi.pcloud.com for a Europe account
• Credential (Namirasoft Credential’s ID) : A saved pCloud sign in that lets Namirasoft NWS Volume open your account.
  1. In Namirasoft Credential, create a Basic Auth credential with your pCloud email and password
  2. Come back here and pick that saved credential

This type connects a MEGA account so you can work with the files in it. You sign in with your MEGA email and password.

• Basic Auth (String) : This holds the email and password for your MEGA account. You enter your MEGA email address and its password here so the connection can open your account.
• Two Factor Code (String) : If you protect your MEGA account with two factor verification, you enter the current six digit code from your authenticator app here. You leave it empty for accounts that do not use two factor verification.

This type connects a Proton Drive account so you can work with the files in it. You sign in with your Proton email and password.

• Basic Auth (String) : This holds the email and password for your Proton account. You enter your Proton email address and its password here so the connection can open your account.
• Two Factor Code (String) : If you protect your Proton account with two factor verification, you enter the current six digit code from your authenticator app here. You leave it empty for accounts that do not use two factor verification.

This type connects a Yandex Disk account so you can work with the files in it. You sign in with your Yandex account through OAuth, which lets Namirasoft NWS Volume reach your Yandex Disk on your behalf.

• Credential (Namirasoft Credential’s ID) : A credential is the Yandex sign in that lets Namirasoft NWS Volume open your Yandex Disk. You create it once by signing in with your Yandex account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a Yandex Disk token auth credential?

This type connects a Zoho WorkDrive account so you can work with the files in it. You sign in with your Zoho account through OAuth, which lets Namirasoft NWS Volume reach your WorkDrive on your behalf.

• Region (Enum) : Zoho keeps accounts in several regions, and the region tells the connection where yours lives.
  1. Look at the web address you use to open Zoho, which shows your region
  2. Pick the matching region, for example com (United States), eu (Europe), in (India), or com.au (Australia)
• Credential (Namirasoft Credential’s ID) : A credential is the Zoho sign in that lets Namirasoft NWS Volume open your WorkDrive. You create it once by signing in with your Zoho account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a Zoho token auth credential?

This type connects a Jottacloud account so you can work with the files in it. You sign in with your Jottacloud account through OAuth, which lets Namirasoft NWS Volume reach your Jottacloud on your behalf.

• Token URL (String) : A personal login token that Jottacloud generates for you, which lets the connection sign in to your account.
  1. Open jottacloud.com/web/secure and sign in
  2. Under Personal login token, click Generate
  3. Copy the token
• Credential (Namirasoft Credential’s ID) : A saved Jottacloud sign in that lets Namirasoft NWS Volume open your account. You create it once from a Jottacloud personal login token.
  1. Open jottacloud.com/web/secure and sign in
  2. Under Personal login token, click Generate and copy the token
  3. In Namirasoft Credential, create a Token Auth credential, paste the token, and give it a name
  4. Come back here and pick that saved credential

This type connects a HiDrive account, the cloud storage from Strato, so you can work with the files in it. You sign in with your HiDrive account through OAuth, which lets Namirasoft NWS Volume reach your HiDrive on your behalf.

• Scope Access (Enum) : The scope access sets how much the connection can do, picked from a list. You choose read write to view and change files, or read only to view and download files and leave them unchanged. You pick the one that matches what you need.
• Credential (Namirasoft Credential’s ID) : A credential is the HiDrive sign in that lets Namirasoft NWS Volume open your HiDrive. You create it once by signing in with your HiDrive account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a HiDrive token auth credential?

This type connects a Koofr account so you can work with the files in it. You sign in with an application password that you create in Koofr.

• Provider (Enum) : The provider tells the connection which Koofr based service you use, picked from a list. You choose Koofr for a standard Koofr account. Some other services run on Koofr technology, so you pick that name if your account is with one of them, or you choose the self hosted option for your own Koofr server.
• Endpoint (String) : The endpoint is the web address of your Koofr service. For a standard Koofr account you use https://app.koofr.net. You change it only when you connect to a different or self hosted Koofr server, and you enter that address here.
• Credential (Namirasoft Credential’s ID) : A saved Koofr sign in that lets Namirasoft NWS Volume open your account. Koofr needs an application password, not your main password.
  1. In Koofr, click your profile picture, open Preferences, then Password
  2. Under App passwords, type a name and click Generate, then copy the password
  3. In Namirasoft Credential, create a Basic Auth credential with your Koofr email and this app password
  4. Come back here and pick that saved credential

This type connects a Mail.ru Cloud account so you can work with the files in it. You sign in with your Mail.ru email and an application password that you create for the account.

• Credential (Namirasoft Credential’s ID) : A saved Mail.ru sign in that lets Namirasoft NWS Volume open your account. Mail.ru needs an application password, not your main password.
  1. In Mail.ru, click your user icon and open Security
  2. Open Passwords for external applications, add one, give it a name, and copy it
  3. In Namirasoft Credential, create a Basic Auth credential with your Mail.ru email and this app password
  4. Come back here and pick that saved credential

This type connects an OpenDrive account so you can work with the files in it. You sign in with the email and password for your OpenDrive account.

• Credential (Namirasoft Credential’s ID) : A saved OpenDrive sign in that lets Namirasoft NWS Volume open your account.
  1. In Namirasoft Credential, create a Basic Auth credential with your OpenDrive email and password
  2. Come back here and pick that saved credential

This type connects a PikPak account so you can work with the files in it. You sign in with the username and password for your PikPak account.

• Credential (Namirasoft Credential’s ID) : A saved PikPak sign in that lets Namirasoft NWS Volume open your account.
  1. In Namirasoft Credential, create a Basic Auth credential with your PikPak username and password
  2. Come back here and pick that saved credential

This type connects a Put.io account so you can work with the files in it. You sign in with your Put.io account through OAuth, which lets Namirasoft NWS Volume reach your Put.io on your behalf.

• Credential (Namirasoft Credential’s ID) : A saved Put.io sign in that lets Namirasoft NWS Volume open your Put.io. You create it once from a Put.io token.
  1. Open app.put.io/oauth
  2. Click Create App and give it a unique name
  3. Click the key icon next to your app to open its Secrets page, then copy the token
  4. In Namirasoft Credential, create a Token Auth credential and paste the token
  5. Come back here and pick that saved credential

This type connects a Linkbox account so you can work with the files in it. You sign in with your Linkbox account through OAuth, which lets Namirasoft NWS Volume reach your Linkbox on your behalf.

• Credential (Namirasoft Credential’s ID) : A saved Linkbox sign in that lets Namirasoft NWS Volume open your Linkbox. You create it once from a Linkbox token.
  1. Open linkbox.to/admin/account and sign in
  2. Copy the token shown on your account page
  3. In Namirasoft Credential, create a Token Auth credential and paste the token
  4. Come back here and pick that saved credential

This type connects a library on a Seafile server, an open source file sharing platform that teams often run themselves. You sign in with your Seafile account and choose the library you want to work with.

• URL (String) : The web address of your Seafile server, for example https://seafile.example.com.
  1. Open Seafile in your browser, or ask your administrator for the address
  2. Copy the web address, for example https://seafile.example.com
• Basic Auth (String) : This holds the email and password you use to sign in to Seafile. You enter your Seafile email address and its password here.
• Two Factor Code (String) : If your Seafile account uses two factor verification, you enter the current six digit code from your authenticator app here. You leave it empty for accounts that do not use two factor verification.
• Library (String) : A library in Seafile is a top level folder that holds a set of files, much like a drive.
  1. Open Seafile in your browser
  2. Copy the name of the library you want to connect
• Library Key (String) : If the library you chose is encrypted, you enter its password here so the connection can open it. You leave it empty for a library that is not encrypted.

This type connects a Gofile account so you can work with the files in it. You sign in with an API token from your Gofile account.

• Credential (Namirasoft Credential’s ID) : A saved Gofile sign in that lets Namirasoft NWS Volume open your account. You create it once from your Gofile API token, then pick it here.
  1. Sign in at gofile.io and open My Profile
  2. Copy your Account API token
  3. In Namirasoft Credential, create a Token Auth credential, paste the token, and give it a name
  4. Come back here and pick that saved credential from the list

This type connects a Premiumize.me account so you can work with the files in it. You sign in with an API key from your Premiumize.me account.

• API Key (String) : An API key lets the connection sign in to your Premiumize.me account in place of a password.
  1. Open premiumize.me/account
  2. Click Show API Key
  3. Copy the key that appears above the button

This type connects an Uloz.to account so you can work with the files in it. You sign in with your Uloz.to account, and the connection uses a saved sign in together with your account details.

• Credential (Namirasoft Credential’s ID) : A credential is the Uloz.to sign in that lets Namirasoft NWS Volume open your account. You create it once in the Namirasoft Credential app, then pick that saved credential here from a list. How to get an Uloz.to token auth credential?
• Basic Auth (String) : This holds the username and password for your Uloz.to account. You enter your Uloz.to username and its password here.

This type connects a FileLU account so you can work with the files in it. You sign in with an API key from your FileLU account.

• Key (String) : Your FileLU API key, which lets the connection sign in to your account in place of a password.
  1. Open filelu.com/account/
  2. Find Rclone and switch it on
  3. Copy the key, which begins with RC_

This type connects a Storage Made Easy File Fabric server, a platform that brings several storage services together behind one address. You sign in with your File Fabric account and reach the storage it manages.

• URL (String) : The web address of your File Fabric server, for example https://yourcompany.storagemadeeasy.com.
  1. Open File Fabric in your browser, or ask your administrator for the address
  2. Copy the web address, for example https://yourcompany.storagemadeeasy.com
• Root Folder ID (String) : The root folder id tells the connection which folder to treat as the starting point. Most connections leave this empty to start at the top of your File Fabric. File Fabric does not show folder ids in its web interface, so set this only if your administrator gives you a specific folder id to use.
• Credential (Namirasoft Credential’s ID) : A saved File Fabric sign in that lets Namirasoft NWS Volume open your account. You create it once from a File Fabric authentication token.
  1. In File Fabric, open your Dashboard and go to Security
  2. Under My Authentication Tokens, click Manage and create a token
  3. Copy the token
  4. In Namirasoft Credential, create a Token Auth credential and paste the token
  5. Come back here and pick that saved credential

This type connects a Citrix ShareFile account so you can work with the files in it. You sign in with your ShareFile account through OAuth, which lets Namirasoft NWS Volume reach your ShareFile on your behalf.

• Credential (Namirasoft Credential’s ID) : A credential is the ShareFile sign in that lets Namirasoft NWS Volume open your ShareFile. You create it once by signing in with your ShareFile account in the Namirasoft Credential app, then pick that saved credential here from a list. How to get a Citrix ShareFile token auth credential?

This type connects a Quatrix account, a managed file transfer service from Maytech, so you can work with the files in it. You sign in with an API key and your account address.

• API Key (String) : An API key lets the connection sign in to your Quatrix account in place of a password.
  1. In Quatrix, open your profile and go to API Keys
  2. Enter a title, then click Generate key
  3. Copy the key right away, because Quatrix shows it only once
• Host (String) : The web address of your Quatrix account, for example yourcompany.quatrix.it.
  1. Open Quatrix in your browser
  2. Copy the address shown in the address bar, for example yourcompany.quatrix.it

This type connects a 1Fichier account so you can work with the files in it. You sign in with an API key from your 1Fichier account.

• API Key (String) : An API key lets the connection sign in to your 1Fichier account in place of a password.
  1. Open 1fichier.com/console/params.pl
  2. Scroll to API Key, click Get my API key, then copy it

This type connects storage on Sia, a network that spreads your files across many independent hosts for privacy and durability. You connect to a Sia program, called a daemon, that you or your provider runs, and Namirasoft NWS Volume talks to it through its local interface.

• API URL (String) : The address where your Sia daemon listens for commands. Use http://127.0.0.1:9980 when the daemon runs on the same machine, or http://your-server:9980 for a remote daemon.
• API Password (String) : The password that protects your Sia daemon’s API. Keep it confidential.
  1. Open the apipassword file: ~/.sia/ on Linux or macOS, or C:\Users\<you>\AppData\Local\Sia\ on Windows
  2. Copy the value

This type connects a Cloudinary account, a service for storing and delivering images and videos, so you can work with the media in it. You sign in with the three values Cloudinary shows on your dashboard.

• Cloud Name (String) : Your Cloudinary account’s unique name, for example my-company.
  1. Open the Cloudinary console at console.cloudinary.com
  2. On the Dashboard, under Product Environment, copy your Cloud name
• API Key (String) : The public part of your Cloudinary credentials.
  1. In the Cloudinary console, open Settings and select API Keys
  2. Copy the API Key from the table
• API Secret (String) : The secret part of your Cloudinary credentials. Keep it confidential.
  1. In the Cloudinary console, open Settings and select API Keys
  2. Reveal and copy the API Secret from the table

This type connects an ImageKit account, a service for storing, optimizing, and delivering images, so you can work with the media in it. You sign in with the endpoint and keys ImageKit shows in your dashboard.

• URL Endpoint (String) : The web address ImageKit serves your media from, for example https://ik.imagekit.io/your_imagekit_id.
  1. Open imagekit.io/dashboard/url-endpoints
  2. Copy your Default URL endpoint
• Public Key (String) : The shareable part of your ImageKit API credentials.
  1. Open imagekit.io/dashboard/developer/api-keys
  2. Under Standard keys, copy your Public Key
• Private Key (String) : The secret part of your ImageKit API credentials. Keep it confidential.
  1. Open imagekit.io/dashboard/developer/api-keys
  2. Under Standard keys, click the eye icon to reveal your Private Key, then copy it

This type connects a Pixeldrain account, a simple file sharing service, so you can work with the files in it. You sign in with an API key from your Pixeldrain account.

• API Key (String) : An API key lets the connection sign in to your Pixeldrain account in place of a password.
  1. Open pixeldrain.com/user/api_keys
  2. Click Show API key
  3. Copy the key