Administer sealfix¶
Edition: Community and Enterprise Offering: Self-managed
Everything an administrator does, from an empty host to a running installation.
flowchart LR
A["Architecture"] --> I["Install"] --> S["First-time setup"] --> U["Users and roles"] --> T["Targets"] --> P["Policies"] --> O["Run it:<br/>health, backup, upgrade"]
classDef step fill:#E9EEF6,stroke:#23407A,color:#13202D
class A,I,S,U,T,P,O step
| Task | Page |
|---|---|
| Understand what runs where, and why | Architecture |
| Install offline with Docker Compose | Install |
| Walk the setup wizard | First-time setup |
| Connect LDAP, Active Directory or single sign-on; give roles | Users, roles and sign-in |
| Add a database for sealfix to change | Targets |
| Decide who approves what, and when changes may run | Environment policies |
| Notifications, SIEM, Git, metrics | Integrations |
| Read System health and its warnings | Health and warnings |
| Back up, restore, upgrade, look after the keys | Backup, upgrade and keys |
An administrator never approves
Setting sealfix up needs no access to the content of any change. An administrator can see each request's target, state and counts, never its template or values, and can never hold an approving role.