Team Share Folders and Collaboration in CentreStack
To accomplish this, I will be using three virtual machines for various access demos.
Find out more at https://centrestack.com/Tour/.
See below for the textual description of the video's content.
Then I jump over to a Windows Server 2016 where I have installed our Server Agent (SA). This is a virtual machine in my network and I am connecting with an IP address, but it could be located anywhere, and the Server Agent client allows it to connect with little effort, to the CentreStack server.
Logging in as the Tenant Admin, I can migrate a share from my local file server. This share has subfolders which are set up to restrict access based on the user’s credentials. When I access the Client Management Console, it shows me the CIFS shares that are available on my system. So, I migrate the ProjectFolderShareSA folder. This migration also includes the user permissions that have been applied to the folder.
So I jump over to the Windows 10 machine, where one of those users is going to use the Windows Client to access the share I just added to CentreStack.
Now logged in as User1, I can see that the ProjectFolderShare is visible.
Jumping inside, there are three folders. As a user I cannot access forAdmins. Looking at the forAllReadOnly folder, I can read anything in here but when I attempt to create a new file, that action is denied. If I back out and go into forUsers, I can now create a new file with no problem.
Now let’s minimize the Web Portal.
You can see that as a User with no admin privileges, I cannot access the Admin folder, but I have no difficulty looking entering the ReadOnly folder. However, just like in the Web Portal, I cannot drop a file into this folder because I don’t have write permissions.
Now as one final test, I jump into the Users folder where I can easily create a new file.
So that covers collaborative team folders and shares.
As you can see CentreStack has created a suite of tools that allow you to access your shares easily from anywhere while maintaining the permissions and security settings established at the Active Directory level.