Batch share folders for members
watermint toolbox stores credentials into the file system. That is located at below path:
Please do not share those files to anyone including Dropbox support. You can delete those files after use if you want to remove it. If you want to make sure removal of credentials, revoke application access from setting or the admin console.
Please see below help article for more detail:
|Dropbox Business: View content of your Dropbox files and folders|
|Dropbox Business: View your team membership|
|Dropbox Business: View your Dropbox sharing settings and collaborators|
|Dropbox Business: View and manage your Dropbox sharing settings and collaborators|
|Dropbox Business: View structure of your team’s and members’ folders|
|Dropbox Business: View basic information about your team including names, user count, and team settings|
For the first run,
tbx will ask you an authentication with your Dropbox account.
Please copy the link and paste it into your browser. Then proceed to authorization. After authorization, Dropbox will show you an authorization code. Please copy that code and paste it to the
watermint toolbox xx.x.xxx ========================== © 2016-2023 Takayuki Okazaki Licensed under open source licenses. Use the `license` command for more detail. 1. Visit the URL for the auth dialogue: https://www.dropbox.com/oauth2/authorize?client_id=xxxxxxxxxxxxxxx&response_type=code&state=xxxxxxxx 2. Click 'Allow' (you might have to login first): 3. Copy the authorisation code: Enter the authorisation code
Please download the pre-compiled binary from Latest Release. If you are using Windows, please download the zip file like
tbx-xx.x.xxx-win.zip. Then, extract the archive and place
tbx.exe on the Desktop folder.
The watermint toolbox can run from any path in the system if allowed by the system. But the instruction samples are using the Desktop folder. Please replace the path if you placed the binary other than the Desktop folder.
This document uses the Desktop folder for command example.
cd $HOME\Desktop .\tbx.exe team runas sharedfolder batch share -file /PATH/TO/DATA_FILE.csv
$HOME/Desktop/tbx team runas sharedfolder batch share -file /PATH/TO/DATA_FILE.csv
Note for macOS Catalina 10.15 or above: macOS verifies Developer identity. Currently,
tbx is not ready for it. Please select “Cancel” on the first dialogue. Then please proceed “System Preference”, then open “Security & Privacy”, select “General” tab.
You may find the message like:
“tbx” was blocked from use because it is not from an identified developer.
And you may find the button “Allow Anyway”. Please hit the button with your risk. At second run, please hit button “Open” on the dialogue.
||Who can add and remove members of this shared folder.||owner|
||Path to data file|
||Who can be a member of this shared folder.||anyone|
||The policy to apply to shared links created for content inside this shared folder.||anyone|
||Custom path to auth database (default: $HOME/.toolbox/secrets/secrets.db)|
||Auto open URL or artifact folder||false|
||Bandwidth limit in K bytes per sec for upload/download content. 0 for unlimited||0|
||Memory budget (limits some feature to reduce memory footprint)||normal|
||Storage budget (limits logs or some feature to reduce storage usage)||normal|
||Maximum concurrency for running operation||Number of processors|
||Enable debug mode||false|
||Enable experimental feature(s).|
||Extra parameter file path|
||Output format (none/text/markdown/json)||text|
||HTTP/HTTPS proxy (hostname:port). Please specify
||Suppress non-error messages, and make output readable by a machine (JSON format)||false|
||Job data retain policy||default|
||Do not store tokens into a file||false|
||Skip logging in the local storage||false|
||Show current operations for more detail.||false|
Member folder data
|member_email||Member email firstname.lastname@example.org|
|path||Path to share||/projects/my_project|
The first line is a header line. The program will accept a file without the header.
Report file path will be displayed last line of the command line output. If you missed command line output, please see path below. [job-id] will be the date/time of the run. Please see the latest job-id.
This report shows the transaction result.
The command will generate a report in three different formats.
|status||Status of the operation|
|reason||Reason of failure or skipped operation|
|input.member_email||Member email address|
|input.path||Path to share|
|result.shared_folder_id||The ID of the shared folder.|
|result.parent_shared_folder_id||The ID of the parent shared folder. This field is present only if the folder is contained within another shared folder.|
|result.name||The name of the this shared folder.|
|result.access_type||The current user’s access level for this shared file/folder (owner, editor, viewer, or viewer_no_comment)|
|result.path_lower||The lower-cased full path of this shared folder.|
|result.is_inside_team_folder||Whether this folder is inside of a team folder.|
|result.is_team_folder||Whether this folder is a team folder.|
|result.policy_manage_access||Who can add and remove members from this shared folder.|
|result.policy_shared_link||Who links can be shared with.|
|result.policy_member||Who can be a member of this shared folder, as set on the folder itself (team, or anyone)|
|result.policy_viewer_info||Who can enable/disable viewer info for this shared folder.|
|result.owner_team_id||Team ID of the folder owner team|
|result.owner_team_name||Team name of the team that owns the folder|
|result.access_inheritance||Access inheritance type|
If you run with
-budget-memory low option, the command will generate only JSON format report.
In case of a report become large, a report in
.xlsx format will be split into several chunks like follows;
The executable automatically detects your proxy configuration from the environment. However, if you got an error or you want to specify explicitly, please add -proxy option, like -proxy hostname:port. Currently, the executable doesn’t support proxies which require authentication.