i am integrating a simple web to box and having a bit of trouble.
i have folder hierarchy of structure like this
music 1 folder
- artist1 folder
- artist2 folder
music 2 folder
- artist1 folder
- artist2 folder
i have added a collaboration to share artist1 folder (from music 1 folder) and artist1 folder(from music 2 folder) to a test account and when i call the box api from test account it all lists the folder on to test account's root folder.
my question is, is there way to retain the hierarchy of folder list such that when i get on test account the folder would only show the collaborated items like this
music 1 folder
- artist1 folder
music 2 folder
- artist1 folder
or is there way i can exclude the items that are not collaborated from showing.
Currently, Box uses a "waterfall" permission model, where the permissions for folders trickle down the folder structure, but do not go up. That means that if a user is added as a collaborator on a sub-folder, they will only be able to see that subfolder in their root directory, but not any folders above it (nor would they have an indication that the folder has anything above it).
Because these permissions trickle down, it means that you also cannot hide specific folders that are lower on the folder tree than the item that the user was originally collaborated on.
Related
Can we link html pages in 2 different folders located in different drives (Say one in Drive:C and another in Drive:E) in same computer?
I can go up multiple directories and to different folders or subfolders using internal links, but am not able to navigate to another drive, max can go up to root directory in same drive.
Yes you can, but why do you need that?
What language do you use for your server?
I'm googling and debugging for days now, and did not find a solution, how to access all files on google drive in the folder created by my application.
I'm using v3 API with non sensitive permission drive.file. This means I can create folders, and create and list files in it. But I only see (list) files which were created by the application. If the user copies some other file into the folder created by the application, it is invisible for the application, and I did not manage to set permission either on the web client, nor in the application.
I don't want to set all files permission to my app, since I don't want to access anything in the user's drive, just in my folder, but there I would like to see also files, the user copied there.
The files are settings/schema export of my application, which the user might move between users with different google account.
Is it possible? How could I list all files in the app data folder? Is there a way to share a file with an application on google drive? Can the user do it manually (like copy the file there, and then set some kind of permission to the application, so it can list/download that file)
Thanks!
Do we have any V2 APIs for box.com which will allow me to upload a folder structure?
I have a folder with the below structure:
main_folder
sub1_folder (Has sub1_file1 and sub1_file2)
sub2_folder (Has sub2_file1 and sub2_file2)
I want to upload 'main_folder'. main_folder has been created on my computer.
Unfortunately, there isn't a way of uploading an entire folder. You will need to recursively walk through "main_folder" and manually create child folders and upload files as you go.
My question concerns Google Drive.
I would like to know how to maintain the same tree structure for all my users accross the organization when I share it. While keeping advanced and customizable ACL permissions for folders and sub-folders.
I am the admin of my Google Business Apps and my Drive folder tree is very well organized and structured. I want some users of my organization to be added to a folder "A" so they can access a sub-folder "A.1", but not the other sub-folders "A.2" and "A.3".
Right now it is pretty messy and hectic if I want to save my tree structure. Indeed, if I want to save my tree structures in my users' Drive, I have to give them access to the main folder "A" so they will be able to access sub-folder "A.1". However, if I do it, my users will be automatically able to access the other sub-folders 1.2. and 1.3. (because the person has access to the main folder "A"). Therefore, I have to manually restrict the access to the sub-folder "A.1" only. That's a pain.
When I give to my users access to the folder "A.1" only, the folder is shared individually and my users' Drive tree structure is no more organized. After sharing 20 folders, my users' Drive becomes pretty messy, while mine remains completely clean (since I created the tree structure and I have all the permissions).
Does anyone know how to efficiently share an identically Drive tree structure among the whole organization, without compromizing on the ACL?
Thanks,
B.
PS: The only post related to this problem is here but it doesn't answer my question: Google Drive - Change owner on folder, sub-folders and content, while saving tree structure
Regrettably, Google Team drive does not currently allow assigning permissions to team drive sub-folders or sharing symlinks across team folders. :(
As a result, our organization ended up creating dozens of team folders each based on role access. This approach solved several problems but created others and makes it hard to share content between roles.
Ideally... GOOGLE should update Team drive to allow permissions to be managed at the drive as well as subfolder level. Until they do the only way to share content within a team drive across roles is one file at a time.
I had my website hosted on a Google Drive public folder based on the following post: http://googleappsdeveloper.blogspot.com/2012/11/announcing-google-drive-site-publishing.html
Sample website:
https://googledrive.com/host/0B716ywBKT84AcHZfMWgtNk5aeXM
Now the problem is a link to the root folder displays all the files on my public folder. I know I can prevent it by adding an index.html file to my public folder to replace the listing, but my folder contents are still accessible through the following URL:
https://drive.google.com/folderview?id=FOLDER-ID&usp=sharing
You can even access them by signing in to your own Google account and navigating to the following page:
https://drive.google.com/#folders/FOLDER-ID
In comparison, on a public folder/subfolder on Dropbox each individual file is publicly available, but the root directory listing is denied.
Examples:
Folder: https://dl.dropboxusercontent.com/u/4017788/logo.png
Subfolder: https://dl.dropboxusercontent.com/u/4017788/Labs/image1.jpg
How can I achieve the same functionality on a Google Drive public folder?
Thanks!
The ACL semantics of Drive is quite different than Dropbox's sharing. In order to make a folder publishable you need to at least give read access to public, meaning once your directory ID is known, it could be listed via the front-end and the API.
In the longer term, we can restrict the listings by not listing children files shared with public but only with those who knows the link.