cryptomator / cryptomator/hub

Hub Vault management Policies

Open
#198 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
80
Forks
15
PR merge metrics
No merged PRs in 30d

Description

### Please agree to the following

- [X] I have searched [existing issues](https://github.com/cryptomator/hub/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/hub/blob/develop/.github/CODE_OF_CONDUCT.md)

### Summary

Admins in the enterprise likes to have the ability to control the cryptomator settings globally.

### Motivation

o use a unified configuration, an admin should have options to administer and set policies.
There are two components, w: a vault on itself and the cryptomator client.

I will give a few examples:
- fixed drive letter per vault
- fixed inactivity time
- maxium file path

The conecpt of a policy would be to set a desired configuration, which the user shoulnd't be able to alter due security and compliance reasons.

### Considered Alternatives

_No response_

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.