Partially Managed Accounts and Containers
Private Users - Managed Containers
In this scenario, accounts and containers are managed in a limited way. Managed containers are established by the system owner, who has read-only access without the ability to modify any content, as private keys remain entirely with the users.
This model prioritizes privacy, as the owner cannot interfere or alter content within the container.
System Roles
The table below outlines system roles in this scenario:
| Application | Application Server | PrivMX Bridge | |
|---|---|---|---|
| Generating Users' Key Pair | |||
| Storing Users' Private Keys | |||
| Storing Users' Public Keys | |||
| Registering Users' Public Keys in Bridge | |||
| Creating and managing containers | |||
| Managing System Owner's Public Key | |||
| Storing always encrypted data |
Example Applications
- Corporate Work Environment: In workplaces with strict compliance requirements, administrators may have read-only access to certain documents in exceptional circumstances, such as when HR personnel need to resolve conflicts or retrieve lost data.
- Public Institutions: In departments that manage sensitive documents, administrators can have restricted access, which preserves data integrity without allowing them to modify the content.