Enable directory restriction to members (Irreversible operation)
watermint toolbox stores credentials into the file system. That is located at below path:
%HOMEPATH%\.toolbox\secrets (e.g. C:\Users\bob.toolbox\secrets)
$HOME/.toolbox/secrets (e.g. /Users/bob/.toolbox/secrets)
$HOME/.toolbox/secrets (e.g. /home/bob/.toolbox/secrets)
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 for teams: View your team membership
|Dropbox for teams: View and manage your team membership
|Dropbox for teams: 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-2024 Takayuki Okazaki
Licensed under open source licenses. Use the `license` command for more detail.
1. Visit the URL for the auth dialogue:
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.
.\tbx.exe member update invisible -file /PATH/TO/DATA_FILE.csv
$HOME/Desktop/tbx member update invisible -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.
|Path to data file
|Custom path to auth database (default: $HOME/.toolbox/secrets/secrets.db)
|Auto open URL or artifact folder
|Bandwidth limit in K bytes per sec for upload/download content. 0 for unlimited
|Memory budget (limits some feature to reduce memory footprint)
|Storage budget (limits logs or some feature to reduce storage usage)
|Maximum concurrency for running operation
|Number of processors
|Enable debug mode
|Enable experimental feature(s).
|Extra parameter file path
|Output format (none/text/markdown/json)
|HTTP/HTTPS proxy (hostname:port). Please specify
DIRECT if you want skip setting proxy.
|Suppress non-error messages, and make output readable by a machine (JSON format)
|Job data retain policy
|Do not store tokens into a file
|Skip logging in the local storage
|Show current operations for more detail.
Member list for changing visibility
|Member email address
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 of the operation
|Reason of failure or skipped operation
|Member email address
|ID of user as a member of a team.
|Email address of user.
|Is true if the user’s email is verified to be owned by the user.
|The user’s status as a member of a specific team. (active/invited/suspended/removed)
|Also known as a first name
|Also known as a last name or family name.
|A name that can be used directly to represent the name of a user’s Dropbox account.
|An abbreviated form of the person’s name.
|The namespace id of the user’s root folder.
|External ID that a team can attach to the user.
|A user’s account identifier.
|Persistent ID that a team can attach to the user. The persistent ID is unique ID to be used for SAML authentication.
|The date and time the user joined as a member of a specific team.
|The date and time the user was invited to the team
|The user’s role in the team (team_admin, user_management_admin, support_admin, or member_only)
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.