Giving access to my DS for family members_

HomeLab
1

Hi spacerex followers, and admins-mods.

I need a favor or at least support.

I have the DS1522+ i belive, do not remember the version anymore.
My goal is to setup the machine so that i can add relatives, familymembers that can access it but safely.

For the moment, only within my network via wifi internal people can get access to my DS and for example having their pictures backupped.

Now i want to go a step further, and allow them from home to access the DS.
Quickconnect should be a good thing, but i will need a lot of links in order to give them out.

Is there a good solution for this_ also VPN is for me the best common sense, keep in mind that my family members are not that smart.

1 Like
2

At the NAS, you create a user account for each family member. Assuming that you have the User Home service enabled, each user will automatically have its home folder for files and images.

Regarding external access, if you use Synology apps you use QuickConnect. There are several ways to optimize QuickConnect. For example, in its advanced settings, disable DSM access and allow mobile apps.

And by the way, there is a dedicated Synology forum here. You get a better response when you post there instead of posting in the HomeLab forum.

1 Like
3

Go with what Paul wrote.

Assuming your DSM version supports it, DSM will auto-create a “Home Folders” folder for the admin containing an individual “Home” folder for each user who has a login, i.e., each family member. Also, the Home feature isolates each user to their own folder, e.g., Bob can only use his “Bob” folder and can’t even see Sally’s folder, nor can Sally see Bob’s.

Using Homes with QuickConnect (QC) is definitely the simplest and arguably the best way to go. Also, QC has other very distinct advantages:

  1. It does not require an always-open port;
  2. It’s secure using various random relay servers versus a static route and (assuming you set it to) secures your data at the source and only decodes at the final destination so it’s secure at all steps in transit;
  3. It defults to the fastest connection only using relays as a last resort for the final connection, e…g, local LAN first, then DDNS if not on the LAN, and finally random relay last; and
  4. It’s very simplistic: the users click the link, and everything else “just works”.

QC beats a VPN for most, if not all purposes and creates an ad hoc VPN on-the-fly when connecting via DDNS without your users having to learn how to use a VPN nor you having to manage it.