You choose!
Flusk Vault is able to function without any collaborator access. However, monitoring won't be available and some security points won't be checked without a collaborator's access. You can find the exact list here.
Did you know? In all cases, Flusk never requires database access.
Possible Configurations
Below is the permissions we recommend giving Flusk in order for the tool to function at its best.
1. Security + Monitoring (recommended)
This is the recommended configuration. It allows:
π Monitoring features (as available, based on plan)
π‘οΈ Security features
Permission settings
βοΈ Admin | App | Data | Logs | βοΈ Only dev. version |
No
| View and edit | No permission | View and query | No
|
Alternative configurations
Below are some alternative configurations if you wish to give Flusk limited access to your app.
View only
access for theApp
setting.
βThis will prevent some features such as scheduling deployments from working.
βNo permission
access for theLogs
setting.
βThis will prevent most monitoring features (such as the Log Explorer or Error Explorer) from working.
βChecked
Only dev. version
βThis will prevent security testing and monitoring on your live version and some features such as scheduling deployments from working.
βNo collaborator access
βThis will prevent monitoring features from working. Security features will be slightly limited (see details here)
β
β