nextcloud.update #302

Merged
fede merged 12 commits from nextcloud.update into main 2024-04-15 17:33:06 +02:00
103 changed files with 617 additions and 143 deletions
Showing only changes of commit 17ddb7a788 - Show all commits

View File

@ -4,7 +4,7 @@ published: true
visible: true
indexed: true
updated:
last_modified: "December, 2023"
last_modified: "January, 2024"
app: Nextcloud
app_version: 27.10.3
taxonomy:

View File

@ -15,7 +15,7 @@ page-toc:
---
# Settings
As it was mentioned in the previous chapter, to access our settings we just click on our profile picture on the top right corner and choose **"Settings"** *(if we did not set a picture yet, we will see a round avatar with the first letter of your username inside)*.
As it was mentioned in the previous chapter, to access our settings we just click on our profile picture on the top right corner and choose **"Settings"** *(if we did not set a picture yet, we will see a round avatar with the first letter of our username inside)*.
![](en/settings.menu.gif)
@ -50,7 +50,7 @@ In this section we can:
- **the groups** we belong to (if any), by default, **Disroot** accounts are not associated with any group, and
- **the quota** of storage space we are using.
Now, you may have noticed that right next to the title, in this case of the **Profile picture**, there is a user icon. By clicking on it we can set the privacy scope we want to assign to this particular information.
Now, we may have noticed that right next to the title, in this case of the **Profile picture**, there is a user icon. By clicking on it we can set the privacy scope we want to assign to this particular information.
![](en/privacy.scope.png)
@ -96,9 +96,9 @@ All right, let's continue.
![](en/security.png?lightbox)
But before we can change anything we need two things:
But before we can change anything we need to do two things:
!! **1. pay close attention to what we are enabling or modifying**, and
!! **1. to pay close attention to what we are enabling or modifying**, and
!! **2. to fully understand how some features such as two-factor authentication work**,
!! **otherwise we may end up losing our files.**
@ -136,7 +136,7 @@ Examples of these programs are:
3. We will get a TOTP secret (to manually configure a TOTP application) and a QR code to scan with a mobile app.
4. In our application we generate the code and then fill in with it the verification field.
If all goes well, the we will see that TOTP is enabled.
If all goes well, then we will see that TOTP is enabled.
![](en/2fa.enabled.png)
@ -150,6 +150,7 @@ So once generated we should keep them in a safe place (certainly, not in our pho
Each code allows us to login once. Then, when we are in, we can reconfigure our OTP or disable the two-factor authentication.
Once enabled 2FA, every time we log in to the cloud we will be asked for
1. our Disroot credentials and
2. the temporary authentication code.
@ -177,7 +178,7 @@ A similar mechanics applies to **Passwordless Authentication**.
**How it works?**
- our client device creates a key pair—keeping the private key on the device and registering the public key with the cloud;
- Our client device creates a key pair, keeping the private key on the device and registering the public key with the cloud;
- the client device authenticates us by proving possession of the private key to the service by signing a challenge (such as scanning a finger, entering a PIN, or pressing a button);
- when we go to log in, we unlock the FIDO authenticator following the same method as when we registered it;
- the device selects the correct key and signs the services challenge based on our account identifier;
@ -193,8 +194,9 @@ Although here at **Disroot** we are very respectful of people's privacy and we a
This option is disabled by default as it enables admins of **Disroot** to decrypt our files. So it is our choice to enable it or not but it also increases our level of accountability in managing and caring our credentials.
!! **Enabling this option after our password was lost will not recover our files!** !! We must make this decision beforehand.
!! **Disroot strongly encourage us keep our password stored in a safe place.** This is the best and only way to keep our files and account safe. We really do not want to have access to it.
!! **NOTE THAT:**
!! **enabling this option after our password was lost will not recover our files!** !! We must make this decision beforehand.
!! **Disroot strongly encourage us keep our password stored in a safe place.** This is the best and only way to keep our files and account safe. We really do not want to have access to them.
## Invalid private key for encryption app
@ -211,7 +213,9 @@ If we receive a message like this when we log in to the cloud, it is because we
After login out and back into the Cloud again we should see our files and the message should have disappeared.
!! If we do not remember our old password, it is still possible to reset the account but **it will not be possible to recover any files on the cloud as they are encrypted with the old key**. What we have to do is to remove all files from the Cloud (this does not include calendars, contacts, etc., only files), and to contact Disroot support (support@disroot.org). Admins will then proceed wiping the key so the new key pair based on our current password can be re-generated automatically upon new login.
!! **NOTE THAT:**
!! if we do not remember our old password, it is still possible to reset the account but **it will not be possible to recover any files on the cloud as they are encrypted with the old key**.
!! What we have to do is to remove all files from the Cloud (this does not include calendars, contacts, etc., only files), and to contact Disroot support (support@disroot.org). Admins will then proceed wiping the key so the new key pair based on our current password can be re-generated automatically upon new login.
## Devices & sessions
@ -220,7 +224,8 @@ After login out and back into the Cloud again we should see our files and the me
Here we can see how many devices are currently connected to our account. If we do not recognize one connected device, it might mean our account has been compromised and we should proceed to change our password.
!! We need to keep in mind that every browser, mobile, computer, etc., will be shown as separate devices each time we change our network, for example. So we do not have to freak out at first. We just seriously double check everything, before we go full on paranoid mode.
!! **We need to keep in mind that:**
!! every browser, mobile, computer, etc., will be shown as separate devices each time we change our network, for example. So we do not have to freak out at first. We just seriously double check everything, before we go full on paranoid mode.
### App password
@ -228,7 +233,7 @@ Here we can see how many devices are currently connected to our account. If we d
When two-Factor authentication is enabled, third party applications (like our email or notes clients) will not be able to login our account with our user credentials only. For those devices we can create a specific password for the app.
----
---
# Notifications
@ -236,6 +241,7 @@ When two-Factor authentication is enabled, third party applications (like our em
Here we can configure whether we want to be notified or not and how when certain actions or activities take place. The configurations in this section are quite simple and straightforward.
---
# External storages
@ -244,10 +250,9 @@ Here we can configure whether we want to be notified or not and how when certain
The external storage application allows us to mount external storage services and/or devices as secondary **Nextcloud** storage devices.
## Configuring an external storage
First we need to create a folder in our **Files** where the external storage will be mounted. Then select an available option and then an authentication method.
First we need to create a folder in our Files where the external storage will be mounted. Then select an available option and then an authentication method.
![](en/external_storage_auth.gif)
![](en/external.gif)
- **Username and password**: it requires a manually-defined username and password. These get passed directly to the backend and are specified during the setup of the mount point.
@ -257,106 +262,110 @@ First we need to create a folder in our Files where the external storage will be
- **Global credentials**: it uses the general input field for “Global credentials” in the external storage settings section as source for the credentials instead of individual credentials for a mount point.
----
- **Global credentials, user entered**: similar to the previous method, but credentials need to be specified by each user individually. Before the first access to that mount point the user will be prompted to enter the credentials.
---
# Mobile & desktop
Here you'll find shortcuts to the mobile and desktop **Nextcloud** applications...
Here we will find shortcuts to the mobile and desktop **Nextcloud** applications...
![](en/mobile.png)
... as well as shortcuts to documentation about how to connect your calendar and contacts, access via WebDAV or download the configuration file for macOS/iOS...
... as well as shortcuts to documentation about how to connect our calendar and contacts, access via WebDAV or download the configuration file for macOS/iOS.
![](en/mobile_connect.png)
... the Disroot Cloud server address, in case you need it to setup a desktop or mobile client...
![](en/mobile_server.png)
... and finally links to download the Nextcloud Talk app.
![](en/mobile_app.png)
----
---
# Sharing
This is the very purpose of **Nextcloud**, to share. Here you can find your **Federated Cloud ID**, your identity in the ecosystem of platforms that use the same or similar software to store and share information.
![](en/federated_cloud.png)
## Federated cloud
Just like when you send emails to other users who have accounts on other servers, **Nextcloud** makes it possible to share files, calendars, contacts, etc., between users of different platforms that use similar software, so they can collaborate with each other regardless of the service provider. You can share your **Federated Cloud ID** with others by just sending a link or via predefined platforms (you can add your preferred ones if they are not included).
![](en/sharing_fed_cloud.png)
## Files
Here you can change the ownership of a file or folder by selecting it and entering the username of the person to whom you want to transfer ownership.
![](en/change_ownership.gif)
## Sharing
By default, you will automatically accept user and/or groups shares. You can disable that option here.
In this section we can find our **Federated Cloud ID**, our identity in the ecosystem of platforms that use the same or similar software to store and share information.
![](en/sharing.png)
## Federated cloud
**Nextcloud** allows us to share files, calendars, contacts, etc., between users of different platforms that use similar software, so we can collaborate with each other regardless of the service provider. We can share our **Federated Cloud ID** with others by just sending a link or via predefined platforms (we can add our preferred ones if they are not included).
## Files
Here we can change the ownership of a file or folder by selecting it and entering the username of the person to whom we want to transfer ownership.
![](en/tranfer.gif)
## Sharing
By default, we will automatically accept user and/or groups shares. We can disable that option here and set a default folder for accepted shares.
![](en/sharing.opt.png)
---
----
# Appeareance and accesibility
In this section you can change the default high contrast theme to the dark theme and the default cloud font to the Dyslexia font.
In this section we can change the cloud theme and the default cloud font to the Dyslexia font.
![](en/accessibility.png)
![](en/appearance.png?lightbox)
## Keyboard shortcuts
Enable/disable the cloud keyboard shortcuts.
![](en/keyboard.short.png)
## Background
To set a custom background.
![](en/background.png)
## Breeze Dark
Set the KDE Breeze Dark theme for Nextcloud.
![](en/breeze.png)
---
# Availability
Here we can configure our working hours, this way other users will see when we are out of office when they book a meeting, for example.
![](en/availability.png)
---
# Flow
Flow is an application designed to help users automate tasks. For example, if we are working in a group on a document, we can set up a flow that sends a notification to our team's chat room when someone changes the file.
Flow is an application that aims to help users automate tasks. For example, if you are working in a group on a document, you can set up a flow that sends a notification to your team's chat room when someone changes, creates or uploads files in a specific folder.
Current workflows available:
_**Write to conversation**_ is the only Flow available for the moment.
- **Write to conversation**: it writes event information into a conversation of our choice.
- **Create bookmark**: it takes a link and adds it to our collection of bookmarks.
![](en/flow.png)
## How does it work?
Suppose we create a document that requires the participation of others and for that we create a conversation with our group via NC Talk. Through Flow, we can establish that every time the document is modified the group will be notified in the conversation. We can set a number of actions and tasks not only on a document, but also on a folder or other files.
Suppose you create a document that requires the participation of others and for that you create a conversation with your group via NC Talk. Through Flow, you can establish that every time the document is modified the group will be notified in the conversation. You can set a number of actions and tasks not only on a document, but also on a folder or other files.
![](en/flow.gif)
![](en/flow_add.gif)
![](en/flow_chat.png)
![](en/flow_chat_2.png)
![](en/flow_chat_3.png)
----
---
# Privacy
This section is merely informative. Here we can find the **Nextcloud** User Data Manifesto, who has access to our data (in our case, **Disroot** admins), with whom we have shared something, how our data is encrypted and where is it located.
This section is merely informative. Here you can find the **Nextcloud** User Data Manifesto...
![](en/privacy_manifesto.png)
... who has access to your data (in our case, **Disroot** admins), with whom you have shared something, a shortcut to our **Privacy Statement**, how your data is encrypted...
![](en/privacy_access.png)
... and where the data is located.
![](en/privacy_where.png)
![](en/privacy.png)
----
---
# Custom menu
Here we can set whether or not to use our own custom menu.
Here you can check/uncheck the applications you want to appear on the top bar and change the order by dragging them to the position you want.
![](en/custom.menu.png)
![](en/app_order.gif)
Its use is quite intuitive. We can choose which applications and in which order we want them to appear in our menu.
---
------
# Connected accounts
In this section we can integrate a number of services we can access from our dashboard app.
![](en/connected.accounts.png)
---
These are our settings. Time to work with our files.

View File

@ -0,0 +1,371 @@
---
title: 'Settings'
published: true
visible: true
indexed: true
taxonomy:
category:
- docs
tags:
- cloud
- nextcloud
- settings
page-toc:
active: true
---
# Settings
As it was mentioned in the previous chapter, to access our settings we just click on our profile picture on the top right corner and choose **"Settings"** *(if we did not set a picture yet, we will see a round avatar with the first letter of our username inside)*.
![](en/settings.menu.gif)
Here is where we can manage our personal and cloud settings.
![](en/settings.png?lightbox)
Let's start with our **Personal info**.
# Personal Info
Here we can add information about ourselves, which then we can choose to share or not with others.
![](en/personal.info.png)
We can identify three "sections".
## 1. The profile section
In this section we can:
- change our **Profile picture** by uploading an image or selecting one from our files in the cloud;
![](en/profile.pic.gif)
- enable/disable our **Profile** which is a page that contains certain information we choose to share. When enabled, access to our profile appears in the user menu;
![](en/view.profile.png)
- see our cloud account **Details** which are
![](en/details.png)
- **the groups** we belong to (if any), by default, **Disroot** accounts are not associated with any group, and
- **the quota** of storage space we are using.
Now, we may have noticed that right next to the title, in this case of the **Profile picture**, there is a user icon. By clicking on it we can set the privacy scope we want to assign to this particular information.
![](en/privacy.scope.png)
And depending on the information, the scopes we can choose are:
- **Private**: this means it will be only visible to us;
- **Local**: only visible to other **Disroot Cloud** users;
- **Federated**: besides other **Disroot Cloud** users, the information will be seen by other **Nextcloud** trusted instances (those added by our cloud administrators); and
- **Published**: the information can be viewed by anyone.
## 2. The user and contact information section
Except for our full name and email (which are taken from our **Disroot** account settings), we can fill in or modify the rest of the information fields.
*To learn how to change our full name, we can check [**this tutorial**](/tutorials/user/account/administration/profile).*
![](en/user.info.png)
In this section we can also change our **Language** and the **Locale** (which defines how dates and other formats are displayed).
## 3. The profile visibility
To finish with our profile settings we have the third and last section, **the profile visibility**.
![](en/profile.visibility.png)
In the previous section we have a number of personal information that we can complete and share (or not) and on which we set a privacy parameter that we call "scope".
In this section, we can decide the visibility of that information in our profile.
![](en/visibility.info.png)
We have to keep in mind that if we set certain information as "private", for example, and its visibility as "show to everyone", the most restrictive rule is the one that will take precedence, in this case, the first one.
All right, let's continue.
---
# Security
**Security** is the place where we can review, set and revoke security settings as well as add new ones.
![](en/security.png?lightbox)
But before we can change anything we need to do two things:
!! **1. to pay close attention to what we are enabling or modifying**, and
!! **2. to fully understand how some features such as two-factor authentication work**,
!! **otherwise we may end up losing our files.**
## Two-Factor Authentication
![](en/2fa.png?lightbox)
The **two-factor authentication (2FA)** is a security process that has a two steps verification, usually the combination of two factors (hence the name):
- 1: something **we know** (like a password),
- 2: something **we have** (could be a security token, a card, a QR code, etc.) or
- 3: something **we are** (like our fingerprint).
!!! Let's take a an everyday example of its use to understand how it works:
!!! - when we go to an ATM to extract money, we need to use our bank card (something **we have**) and a PIN (something **we know**). If the combination fails, we cannot extract the money.
The two-factor authentication can be used if we want have a more secure login. When enabled, we will be asked not only for our login name and password, but also for an extra authentication like a one-time-password (OTP) or verification via a hardware device.
So first we will need a software to generate the temporary codes that we will be asked for after entering our password.
Examples of these programs are:
- [Aegis Authenticator (Android)](https://f-droid.org/en/packages/com.beemdevelopment.aegis/)
- [FreeOTP (Android)](https://f-droid.org/en/packages/org.fedorahosted.freeotp/)
- [FreeOTP+ (Android)](https://f-droid.org/en/packages/org.liberty.android.freeotpplus/)
- [KeePassXC (desktop)](https://keepassxc.org/download/)
### Enabling 2FA
![](en/2fa.gif)
1. We enable TOTP (Time-based One-Time Password)
2. Enter our Disroot password (if requested)
3. We will get a TOTP secret (to manually configure a TOTP application) and a QR code to scan with a mobile app.
4. In our application we generate the code and then fill in with it the verification field.
If all goes well, then we will see that TOTP is enabled.
![](en/2fa.enabled.png)
### 2FA Backup codes
Next step is to generate backup codes. These codes are useful in case, for some reason, our TOTP application does not work (e.g. we lost our phone). With them we can still log in again.
![](en/2fa.backup.gif)
So once generated we should keep them in a safe place (certainly, not in our phone!).
Each code allows us to login once. Then, when we are in, we can reconfigure our OTP or disable the two-factor authentication.
Once enabled 2FA, every time we log in to the cloud we will be asked for
1. our Disroot credentials and
2. the temporary authentication code.
![](en/2fa.login.png)
## Security key
![](en/2fa.security.keys.png)
Besides the TOTP (Time-based One-Time-Password) method we have just seen, **Disroot** offers another one based on hardware tokens like USB keys.
![](en/u2f.png)
The **U2F (Universal 2nd Factor)** is an open standard that simplifies 2FA by using a hardware device like the USB [YubiKey](https://en.wikipedia.org/wiki/YubiKey).
All we need to do is plug the device into our computer or laptop and press the device button to authorize it. After adding it, the browser will communicate with the U2F device to authorize us to log in.
A similar mechanics applies to **Passwordless Authentication**.
![](en/webauthn.png)
**WebAuthn** is a standard web API that enables users to sign in with a cryptographic key pair.
**How it works?**
- Our client device creates a key pair, keeping the private key on the device and registering the public key with the cloud;
- the client device authenticates us by proving possession of the private key to the service by signing a challenge (such as scanning a finger, entering a PIN, or pressing a button);
- when we go to log in, we unlock the FIDO authenticator following the same method as when we registered it;
- the device selects the correct key and signs the services challenge based on our account identifier;
- the service verifies the signed challenge with the stored public key and signs in us.
## Basic encryption module
![](en/basic.encrypt.png)
Here we can decide whether or not an administrator will be able to recover our files in case we lose our password.
Although here at **Disroot** we are very respectful of people's privacy and we are committed to it, the whole thing, of course, comes down to a matter of trust.
This option is disabled by default as it enables admins of **Disroot** to decrypt our files. So it is our choice to enable it or not but it also increases our level of accountability in managing and caring our credentials.
!! **NOTE THAT:**
!! **enabling this option after our password was lost will not recover our files!** !! We must make this decision beforehand.
!! **Disroot strongly encourage us keep our password stored in a safe place.** This is the best and only way to keep our files and account safe. We really do not want to have access to them.
## Invalid private key for encryption app
![](en/invalid.encrypt.key.png)
If we receive a message like this when we log in to the cloud, it is because we have probably changed our password recently. Since **Nextcloud** uses our user password to generate the encryption keys, it is necessary to regenerate them from our new password. To do so, we must:
- go to the Settings menu and then to **Security**;
- scroll down to the **Basic encryption module**;
- type in our old password, then the new one;
- click **Update Private Key Password**
![](en/invalid.mp4?resize=1024,492&loop)
After login out and back into the Cloud again we should see our files and the message should have disappeared.
!! **NOTE THAT:**
!! if we do not remember our old password, it is still possible to reset the account but **it will not be possible to recover any files on the cloud as they are encrypted with the old key**.
!! What we have to do is to remove all files from the Cloud (this does not include calendars, contacts, etc., only files), and to contact Disroot support (support@disroot.org). Admins will then proceed wiping the key so the new key pair based on our current password can be re-generated automatically upon new login.
## Devices & sessions
![](en/devices.png)
Here we can see how many devices are currently connected to our account. If we do not recognize one connected device, it might mean our account has been compromised and we should proceed to change our password.
!! **We need to keep in mind that:**
!! every browser, mobile, computer, etc., will be shown as separate devices each time we change our network, for example. So we do not have to freak out at first. We just seriously double check everything, before we go full on paranoid mode.
### App password
![](en/app.pass.png)
When two-Factor authentication is enabled, third party applications (like our email or notes clients) will not be able to login our account with our user credentials only. For those devices we can create a specific password for the app.
---
# Notifications
![](en/notifications.png?lightbox)
Here we can configure whether we want to be notified or not and how when certain actions or activities take place. The configurations in this section are quite simple and straightforward.
---
# External storages
![](en/external.storage.png)
The external storage application allows us to mount external storage services and/or devices as secondary **Nextcloud** storage devices.
## Configuring an external storage
First we need to create a folder in our **Files** where the external storage will be mounted. Then select an available option and then an authentication method.
![](en/external.gif)
- **Username and password**: it requires a manually-defined username and password. These get passed directly to the backend and are specified during the setup of the mount point.
- **Log-in credentials, save in session**: it uses our **Cloud** login credentials to connect to the storage. These are not stored anywhere on the server, but rather in the user session, giving increased security. Although sharing is disabled when using this method, since **Nextcloud** has no access to the storage credentials.
- **Log-in credentials, save in database**: as the previous method, it uses your login credentials to connect to the storage, but these are stored in the database encrypted. This allows to share files from within this mount point.
- **Global credentials**: it uses the general input field for “Global credentials” in the external storage settings section as source for the credentials instead of individual credentials for a mount point.
- **Global credentials, user entered**: similar to the previous method, but credentials need to be specified by each user individually. Before the first access to that mount point the user will be prompted to enter the credentials.
---
# Mobile & desktop
Here we will find shortcuts to the mobile and desktop **Nextcloud** applications...
![](en/mobile.png)
... as well as shortcuts to documentation about how to connect our calendar and contacts, access via WebDAV or download the configuration file for macOS/iOS.
---
# Sharing
In this section we can find our **Federated Cloud ID**, our identity in the ecosystem of platforms that use the same or similar software to store and share information.
![](en/sharing.png)
## Federated cloud
**Nextcloud** allows us to share files, calendars, contacts, etc., between users of different platforms that use similar software, so we can collaborate with each other regardless of the service provider. We can share our **Federated Cloud ID** with others by just sending a link or via predefined platforms (we can add our preferred ones if they are not included).
## Files
Here we can change the ownership of a file or folder by selecting it and entering the username of the person to whom we want to transfer ownership.
![](en/tranfer.gif)
## Sharing
By default, we will automatically accept user and/or groups shares. We can disable that option here and set a default folder for accepted shares.
![](en/sharing.opt.png)
---
# Appeareance and accesibility
In this section we can change the cloud theme and the default cloud font to the Dyslexia font.
![](en/appearance.png?lightbox)
## Keyboard shortcuts
Enable/disable the cloud keyboard shortcuts.
![](en/keyboard.short.png)
## Background
To set a custom background.
![](en/background.png)
## Breeze Dark
Set the KDE Breeze Dark theme for Nextcloud.
![](en/breeze.png)
---
# Availability
Here we can configure our working hours, this way other users will see when we are out of office when they book a meeting, for example.
![](en/availability.png)
---
# Flow
Flow is an application designed to help users automate tasks. For example, if we are working in a group on a document, we can set up a flow that sends a notification to our team's chat room when someone changes the file.
Current workflows available:
- **Write to conversation**: it writes event information into a conversation of our choice.
- **Create bookmark**: it takes a link and adds it to our collection of bookmarks.
![](en/flow.png)
## How does it work?
Suppose we create a document that requires the participation of others and for that we create a conversation with our group via NC Talk. Through Flow, we can establish that every time the document is modified the group will be notified in the conversation. We can set a number of actions and tasks not only on a document, but also on a folder or other files.
![](en/flow.gif)
---
# Privacy
This section is merely informative. Here we can find the **Nextcloud** User Data Manifesto, who has access to our data (in our case, **Disroot** admins), with whom we have shared something, how our data is encrypted and where is it located.
![](en/privacy.png)
---
# Custom menu
Here we can set whether or not to use our own custom menu.
![](en/custom.menu.png)
Its use is quite intuitive. We can choose which applications and in which order we want them to appear in our menu.
---
# Connected accounts
In this section we can integrate a number of services we can access from our dashboard app.
![](en/connected.accounts.png)
---
These are our settings. Time to work with our files.

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.0 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 66 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 647 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 47 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 210 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 77 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 144 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 17 KiB

After

Width:  |  Height:  |  Size: 77 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 68 KiB

After

Width:  |  Height:  |  Size: 146 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 234 KiB

After

Width:  |  Height:  |  Size: 275 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 5.2 KiB

After

Width:  |  Height:  |  Size: 87 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 467 KiB

View File

@ -1,5 +1,5 @@
---
title: "Files management"
title: "Files"
published: true
indexed: true
taxonomy:
@ -16,124 +16,213 @@ page-toc:
The main task of **Nextcloud** is file management. Below is an overview of the main window, which we will divide in two sections:
![](en/main.png)
![](en/files.png)
- The **left sidebar** let's you filter files based on certain criteria (recents, favorites, shared, by tags, shared with circles or from external storages).
- The **left sidebar** let's us filter files based on certain criteria (recents, favorites, shared, by tags, shared with circles or from external storages).
- The **main window** is your file-browser and workspace. in addition to information about your files, from here you can perform a number of operations, such as commenting, tagging or sharing them.
- The **main window** is our file-browser and workspace. In addition to information about our files, from here we can perform a number of operations, such as commenting, tagging or sharing them.
# File management
At the top of the main window we have four general options:
![](en/workspace.png)
![](en/topbar.png)
We already mentioned the first three functions in the introduction, but it is worth reviewing them.
- 1. The **open/close navigation** button (we already saw it in a previous chapter).
#### 1. Home button
It leads you back to the root folder (the home folder) when you navigate through your files or folders.
![](en/navigation.gif)
![](en/home_btn.gif)
- 2. The **home button**, which leads us back to the root folder (the home folder) when we navigate through our files or folders.
#### 2. New button
It enables you to upload a file and create new folders, text files or pads. Click on it and choose an action from the list.
![](en/home.gif)
![](en/new_button.gif)
- 3. The **New** button which allows us not only to upload a file or create new folders, but also text files, pads, add descriptions and set a folder as a templates directory. We click on it and choose an action from the list.
#### 3. Workspace
It allows you to bring context to your folders by adding notes, todo lists and links to files on top.
![](en/new.gif)
![](en/workspace.gif)
- 4. The **grid view** button, to toggle between the list and the grid view of our files and folders.
Rich workspace can be enabled/disabled by clicking the settings icon at the bottom of the left sidebar.
![](en/grid.gif)
![](en/workspace_set.gif)
#### 4. Recent files
Here you can see the last modified files or folders.
At the bottom of the left sidebar we can:
- access our **Deleted files** (if any). When we delete a file or folder, these go to this kind of trash bin where we can recover them or delete them definitively;
- check our **storage** quota;
- and open our **Files settings**, where we can set to show or not hidden files, to crop image previews and to show rich workspaces and recommendations. Additionally, here we can copy our **WebDAV** address to remotely access our files.
![](en/recent.png)
![](en/files.settings.png)
#### 5. File manager
From this section you can do a number of operations on files or folders.
---
##### 5.1 Upload files
In addition to the option in the **New** menu (+), you can upload your files directly by dragging them from your computer to here.
# Files management
File management within the cloud is similar to how we would do it on our computer, with the advantage of being able to perform a lot more operations, especially those related to the collective management of files that would otherwise be more laborious.
Next we will look at the basic operations of file management in the cloud.
## Uploading files
We have already seen that from the "**New**" button we can create folders, and create or upload files. But we can also upload them directly by dragging them from our desktop computer to the files main window.
![](en/upload.gif)
##### 5.2 Basic files and folders actions
By clicking on the **"three dots"** icon next to the filename or directory you can access to some extra options. Those options are self explanatory. You can "Add to favorites", see the "Details", "Rename", "Move or copy", "Download" or "Delete" the file or directory.
## Sharing files
By clicking on the **"three dots"** icon next to the filename or directory we access the main actions we can perform on a given file or folder.
![](en/file_options.gif)
![](en/files_options.png)
##### 5.3 Sharing files
Sharing files and directories is an essential part of any cloud storage service. You can choose to share files with other Disroot users, an entire group or even with other users using OwnCloud/Nextcloud on different platforms. You can also share with anyone out there through the public link option.
The first one we are going to learn is **Details**. This is because **Sharing** is one of the core features of the cloud and it is also the default tab/option that is displayed first when opening **Details** where we have another set of options.
![](en/sharing.gif)
![](en/files.sharing.png)
To share a file or directory just click the *share icon* ![](en/share_icon.png) right next to the name of the item you want to share. A right-bar popup will show up with all the sharing options for you to choose from.
![](en/sharing.png)
### Share link
We can share a file or folder in several ways. The first one we will see is through a link.
You might share with other users, groups, or users on different cloud servers using the federation address. To do so, you will have to type their entire usernames because **we don't provide autocompletion for privacy reasons**.
![](en/share.link.gif)
![](en/sharing_id.png)
1. Clicking on the **+** (plus) icon will generate a link.
When sharing with other users or groups, you can choose if they have rights to edit and/or re-share the shared file. You can also set an expiration date for it and send a note to the recipients.
2. Once the link is created, we can set it to:
- **View only**: to allow viewing and downloading but not editing;
- **Can edit**: to allow other people edit what was shared;
- **File drop (in case of folders)**: to allow uploading files only to a folder without seeing the files that are already in that folder.
- **Custom permissions**:
- **Read**: set as default in case of files.
- **Create (in case of folders)**: to allow creating files and folders within the shared folder.
- **Update**: to allow updating the file/folder content.
- **Delete**: to allow deletion of a file/folder.
![](en/sharing_opt.png)
![](en/permissions.png)
_**1**: file's custom permissions. **2**: folder's custom permissions_
You can also share a file or directory with anyone by using the **Share link** option. It allows you to copy/paste a link and share it. Any person who knows the address (url) will be able to access the file. They don't need to have an account. This option enables you to set editing permissions as well as hide the download, protect the link with a password, set an expiration date, send a note to the recipient, send the link via email, unshare the file and add another link to it.
3. Access more customizations of the link by clicking on the **three-dots** icon on the right and select **Customize link**. We can also **Add another link**, to create multiple links with different rights, or **Unshare** it, both from this menu.
![](en/share_link.gif)
![](en/custom.link.png)
##### 5.4 Additional file operations
Here we can see and set permissions and also:
- **Set password** for the link we are sharing;
- **Set expiration date** after which the shared item becomes inaccessible;
- **Hide download** to disable downloading option;
- **Note to recipient** to send a comment to the person or persons who will receive the link.
![](en/other_op.png)
![](en/custom.link.opt.png)
As you may have noticed when setting up sharing, there are more options in the sidebar.
### Internal share
Another way of sharing a file or folder is via an internal link we can share with other users, groups, circles or people in a Talk conversation.
- **Tags**
Type the name, email or Federated Cloud ID of the person with whom we are going to share the file/folder in the search field. When we find it, we select it and check the permissions we want to grant.
![](en/tags.png)
![](en/internal.gif)
Tagging files can be very useful to find them more easily. To assign a tag, go to the three-point menu to the left of the file name and select **Tags**. Type in a tag or browse through the ones already created and press Enter. You can assign as many tags as you like or need.
Just as when we share a link, we can adjust the permissions and options from the drop-down menu under the user name or from the three dots icon on the right.
![](en/tagging.gif)
#### Other with access
This option allows to find out if a file or folder is accessible to other people through a shared folder at a higher hierarchical level.
Once you have assigned the tags, you can go to the **Tags** filter option and search for files by the tags associated with them.
![](en/others.png)
![](en/tag_filter.gif)
The list shows all users, groups, chats, etc., that a given item has been given access to through sharing of a superior folder in the hierarchy.
Keep in mind that they will all be system tags, so they will be shared with the rest of the users on the server.
![](en/others.opt.png)
- **Activity**
Clicking on the three-dots menu we can
- see who initiated the share;
- see where the share was initiated (we can click to navigate to the folder, as far as we have access there);
- and unshare the initial share (share owner only)
![](en/activity.png)
It gives you an overview of all events with the file. The time it was created, when it was shared, removed, edited, commented on, etc.
#### Internal link
An internal link will only works for users who already have access to the file or folder. We just click on the clipboard icon to copy the link and share it.
- **Chat**
![](en/internal.link.png)
![](en/chat.png)
### Other share options
In this same **Details** panel there are other options we can access from the three-dot menu to the right of a file or folder.
You can start a call or chat with the users you've shared a file or directory.
![](en/details.png)
- **Checksum**
- **Activity**: here we can see a log of all the operations performed on a file or folder.
![](en/checksum.png)
![](en/details.activity.png)
It allows you to create a hash checksum of a file. Select an algorithm and it will try to generate a hash.
- **Chat**: we can start a conversation or a call with the people to whom we share a file or folder.
- **Comments**
![](en/details.chat.png)
![](en/comment.png)
- **Checksum**: it is a mathematical function whose main objective is to detect changes (accidental or malicious) in a data transmission in order to protect the integrity of the information. A checksum is intended to protect three fundamental aspects of the information exchanged between users: data integrity, authenticity of the origin and confidentiality of the information.
This is a very useful feature when you're working on a file with other users. Everyone you've shared the file with can read and add comments. By clicking on the three dots icons right next to your username, you can edit your comment.
![](en/checksum.gif)
![](en/comment_edit.png)
We simply select an algorithm, it will generate a checksum for a file, copy the generated value and share it along with the file. Whoever downloads it can verify the integrity of the data and check that it is the same file.
- **Versions**
![](en/checksum.verification.png)
![](en/versions.png)
- **Comments**: here we can add and read comments on any file or folder. Comments are visible to everyone who has access to the file.
It lets you view all the changes done to a file. You can download previous revisions of a file as well as restore it to previous revision (deleting all changes done after).
![](en/details.comment.gif)
- **Versions**: this tab contains the changes history of a file or folder where we can roll back any of them to any previous version.
![](en/details.versions.gif)
We can restore, rename, compare, download or delete a specific version of a file by clicking on the three-dots icon at the right and selecting an option.
#### Tags
![](en/tags.gif)
We can assign tags to files. The **Tags** option is in the **Details** view, at the top right, we click on it to create or assign tags. Then type our tags. To enter more than one tag we press the return key after creating each tag. All tags are system tags, and are shared by all users on our Nextcloud server.
Let's see the rest of the options and actions we can do.
## Other file operations
In addition to **Details**, the following options can be found in this same menu.
### Add to favorites
![](en/favorites.gif)
By adding a file or folder to favorites, we can quickly find all of them with the **Favorites** filter on the left sidebar.
### Rename
![](en/rename.gif)
Click this option to change the name of a file or folder. If what we modify is shared, those with access will be notified of it.
### Move or copy
![](en/copy.move.gif)
We can copy or move any file or folder by clicking this option. We just select the target folder and click on the action.
![](en/move.drag.gif)
We can also move a file or directory in the traditional way, by dragging and dropping them to the place we want.
### Set reminder
![](en/reminder.png)
To remember something related to the file or folder we can set a reminder. Just click on this option and enter the date and time we want to be reminded.
### Edit locally
![](en/edit.locally.png)
By clicking on this option the browser will try to open the file with a program installed on our device to edit it.
### Download
![](en/download.png)
To download a file or zipped folder to our device.
### Delete
![](en/delete.png)
To remove a file or folder. The files are not immediately deleted permanently, only moved into the trash bin. It is not permanently deleted until we manually do it, or when the Deleted Files app deletes it to make room for new files.
We can access our deleted files by clicking the **Deleted files** option in the left sidebar.
---
OK, so far we have seen the basics of the interface, personal settings and file management. Let's move on to the next chapters to learn about the rest of the cloud applications and functionalities.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 176 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 25 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 5.8 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 167 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 36 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 171 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 167 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 279 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 82 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 228 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 122 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.8 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 590 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.2 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 80 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 131 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 103 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 18 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 154 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 394 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 8.5 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 360 B

Binary file not shown.

Before

Width:  |  Height:  |  Size: 426 B

Binary file not shown.

Before

Width:  |  Height:  |  Size: 343 B

Binary file not shown.

Before

Width:  |  Height:  |  Size: 238 B

Binary file not shown.

Before

Width:  |  Height:  |  Size: 326 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 150 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 81 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 106 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 7.6 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 4.4 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 44 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.1 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 76 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 205 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 198 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 593 B

Binary file not shown.

Before

Width:  |  Height:  |  Size: 153 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 19 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 210 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 174 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 185 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 196 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.4 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 126 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 150 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 179 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 32 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 204 KiB

After

Width:  |  Height:  |  Size: 140 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 162 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 8.1 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

Some files were not shown because too many files have changed in this diff Show More