{"_id":"5a8df903407060001213d23f","project":"55d535ca988e130d000b3f5c","version":{"_id":"55d535cb988e130d000b3f5f","__v":13,"project":"55d535ca988e130d000b3f5c","hasDoc":true,"hasReference":false,"createdAt":"2015-08-20T02:04:59.052Z","releaseDate":"2015-08-20T02:04:59.052Z","categories":["55d535cc988e130d000b3f60","55d6b238d2a8eb1900109eef","55d6b4f3250d7d0d004274cd","55d7967960fc730d00fc2852","55da9804e835f20d009fc5d0","55e75b1de06f4b190080dbfd","55e75b39e06f4b190080dbfe","55e75b7ae06f4b190080dbff","564f5a4e33082f0d001bb709","570fb64aa38d470e0060cbff","586d0dd89a854123001acd65","586d0e3b9a854123001acd66","5a613b28da07540012e8ca4a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"55e75b7ae06f4b190080dbff","__v":10,"project":"55d535ca988e130d000b3f5c","version":"55d535cb988e130d000b3f5f","pages":["5637e17197666c0d008656a5","569591a4fcb1032d0089e037","569622eafe18811700c9c19b","5696c9588560a60d00e2c1e0","569709ca0b09a41900b2442b","5697129ac8ded91700307b77","5697190a59a6692d003fad6a","5697192969393517000c8280","569f11908f6d4b0d00f13bb2","56a0030b5b981c2b00383df0"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-02T20:26:34.258Z","from_sync":false,"order":4,"slug":"frame-platform","title":"Frame Platform"},"user":"55d535835082980d0009c965","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-02-21T22:56:03.407Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":27,"body":"This article covers how you can set up a shared storage space on Frame that lets users collaborate on the same set of files. Beyond storing shared data on Frame, there are several additional options for this use case that rely on 3rd party cloud storage services. For more information about all the storage solutions you can integrate with Frame, see our Storage Solution Guide [here](https://fra.me/solutionguides/storage-solution-guide.pdf). \n\nWith a shared drive for teams, each user in an account will see a mounted network drive, that shows up as the \"T:\" drive. The drive is mounted to the users' stateless instances upon session start, and unmounted at session end. All users see all of the files in the shared drive and can thereby collaborate on projects. Note that simultaneous access to files will be dependent on the software applications used. For example, most programs will \"lock\" a file when it is in use by another user. The shared team drive will reside within the same VPC (or VNet) as all of our production instances. \n\nThe specific implementation of the shared drive depends on which IaaS provider you've chosen. We'll outline the differences below:\n\n\n###Azure\nFrame leverages Azure Files when setting up network drives for team collaboration. Since Azure Files is built specifically for these kinds of applications, you will likely notice the added bonus of impressive data transfer speeds. Admins can access their Azure Files file share through their Sandbox. \n\nCustomers using Azure are not limited to Azure Files for their team's storage solution. Depending on their preference, some admins may prefer to use [Frame's Utility Server](https://docs.fra.me/v1.0/docs/utility-server) and manage it as a shared network drive. For more information, reference the section below as the utility server is the only option for a shared drive for teams on AWS.\n\n### AWS\nOrganizations that would like to set up a team network drive can leverage Frame's Utility Server and map a shared folder for their team to use. Frame's Utility Server is stateful, which means that content persists on the VM just like an on-premises file server. It's also permanently powered on so users can access their data at any time. Once the Utility Server is provisioned, the file share can be created by following the step-by-step documentation [here](https://support.fra.me/s/article/How-to-Create-a-Shared-Folder-in-Windows-Server-2012R2). \n \n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/c5c6ff1-Copy_of_Simple_Frame_Topology.png\",\n        \"Copy of Simple Frame Topology.png\",\n        691,\n        461,\n        \"#ecf0f0\"\n      ],\n      \"caption\": \"A simple network topology of a Frame account with a Utility Server.\"\n    }\n  ]\n}\n[/block]","excerpt":"Collaborate with team members in a shared storage space on Frame","slug":"shared-storage-for-teams","type":"basic","title":"Shared storage for teams"}

Shared storage for teams

Collaborate with team members in a shared storage space on Frame

This article covers how you can set up a shared storage space on Frame that lets users collaborate on the same set of files. Beyond storing shared data on Frame, there are several additional options for this use case that rely on 3rd party cloud storage services. For more information about all the storage solutions you can integrate with Frame, see our Storage Solution Guide [here](https://fra.me/solutionguides/storage-solution-guide.pdf). With a shared drive for teams, each user in an account will see a mounted network drive, that shows up as the "T:" drive. The drive is mounted to the users' stateless instances upon session start, and unmounted at session end. All users see all of the files in the shared drive and can thereby collaborate on projects. Note that simultaneous access to files will be dependent on the software applications used. For example, most programs will "lock" a file when it is in use by another user. The shared team drive will reside within the same VPC (or VNet) as all of our production instances. The specific implementation of the shared drive depends on which IaaS provider you've chosen. We'll outline the differences below: ###Azure Frame leverages Azure Files when setting up network drives for team collaboration. Since Azure Files is built specifically for these kinds of applications, you will likely notice the added bonus of impressive data transfer speeds. Admins can access their Azure Files file share through their Sandbox. Customers using Azure are not limited to Azure Files for their team's storage solution. Depending on their preference, some admins may prefer to use [Frame's Utility Server](https://docs.fra.me/v1.0/docs/utility-server) and manage it as a shared network drive. For more information, reference the section below as the utility server is the only option for a shared drive for teams on AWS. ### AWS Organizations that would like to set up a team network drive can leverage Frame's Utility Server and map a shared folder for their team to use. Frame's Utility Server is stateful, which means that content persists on the VM just like an on-premises file server. It's also permanently powered on so users can access their data at any time. Once the Utility Server is provisioned, the file share can be created by following the step-by-step documentation [here](https://support.fra.me/s/article/How-to-Create-a-Shared-Folder-in-Windows-Server-2012R2). [block:image] { "images": [ { "image": [ "https://files.readme.io/c5c6ff1-Copy_of_Simple_Frame_Topology.png", "Copy of Simple Frame Topology.png", 691, 461, "#ecf0f0" ], "caption": "A simple network topology of a Frame account with a Utility Server." } ] } [/block]