Thanks, it meet not look like it but I am new to Linux, so I just need some explanation to understand it correctly.

No problems, but if you're new to all this, I'd strongly suggest doing things correctly to start with, and learning to work WITH systems/network security, rather than working around it.

You said "I am well aware that ftp isen't secure", indicating you have at least some knowledge of things. But multi-user access to a website directory via FTP, and then asking about root access to that same directory, isn't good at all. If you want to do website updates, SVN is by far the better/more secure way to go. Since you're also implying that there is more than one user, we can only assume it's a company network, rather than just you at home. That said...what are you going to do when someone overwrites someone elses work via FTP? There's no locking/checking/versioning. Or if you have to add more users? You're just adding more you have to keep track of as the administrator, and more to do with each new user.

It's your system and network, we can only suggest; good luck to you.

I never said that I have multiple user access to the website directory, I nearly asked about permissions for groups and users on a directory. I only want one user to have access to that directory.
I am familier with IT, working as a support for 7 years but but only in a Windows based environment, I have just decided that I would like to some Linux to see how it Works and get to know it.
This is done on my home Network.

That's not portable, Windows is the odd man out, however GNU/Linux, BSD, OS X, or just about anything else have a lot of overlap.

( I've seen Windows and almost admire your persistence in trying to get any work done in that kind of environment. Almost. There are just so many tools missing, the UI so awkward, and it is so illogically arranged. However, all that also makes it hard to get out, so I can appreciate the barrier you might be seeing. I'd highly recommend moving to a desktop GNU/Linux distro, even if only in a VM. You'll be less constrained by the limitations of Windows and save time and effort -- if you can get past the initial difference. Plus you'll get up to speed faster, which seems to be your goal. There is no substitute for hands-on experience.)

Putting FTP loose on the net hurts us too, not just you. Considering that home networks are usually staging areas for deployment elsewhere, interest in FTP daemons will be met with frowns or stronger. We're happy to help point in the right direction, but FTP is a foot gun and not just for you.

That said, to reiterate what has been posted before:

• Abandon FTP, it is 2017 and I'd say there is a strong case to remove it even from the repositories.
• Install SSH via OpenSSH-server. It is the well-established, industry-wide best practice for remote access. It will also be the vehicle over which many other services operate. It provides SFTP out of the box and so you can connect graphically via your file manager to transfer files seamlessly.
• Set permissions for your web server's document root. If it is just you by yourself then chown is enough. If it is for a group set up SVN or Git for version control.

If you are looking for even more background about the file permissions, try this one on file permissions and attributes. These systems come with built-in reference documents for each utility, for this one see "chown":

Manual pages do vary in scope and quality but are always worth reviewing.