Administrator Guide

Hub is the optional team platform for Sigilweaver Loom. It centralizes users, roles, database credentials, Servers, schedules and an audit log. This guide is for the people who deploy and run it.

Open beta

Hub is in open beta. Read Hub Open Beta before you rely on it, especially the limits on restarts and replicas.

What Hub does

• Users and roles. Four roles: Owner, Admin, Auditor and User.
• Shared connections. Connections keep database credentials in Hub, encrypted. Users can use a connection without ever seeing its password.
• Access control. Users join user groups. Groups are granted grant groups. Grant groups contain connections.
• Execution. Servers run workflows. Hub tracks their health and sends work to them.
• Scheduling and history. Users upload workflows, run them and schedule them in the Hub web app.
• Audit log. Hub records security-relevant events in a hash-chained log that auditors can verify.

The permission chain

Users -> User Groups -> Grant Groups -> Connections

A user can reach a connection only if every link exists. That gives you a single path to check when you ask why someone has access.

Set up a Hub

1. Deploy Hub, PostgreSQL and at least one Server with Docker Compose.
2. Claim the Owner account. The first person to register on a fresh Hub becomes the Owner. Do this right after the first start, before you expose Hub to others.
3. Register a Server, or configure it to register itself.
4. Create connections in Admin > Connections.
5. Create grant groups that bundle connections by purpose, such as "Production databases".
6. Create user groups for your teams and assign grant groups to them.
7. Create users and add them to groups.

Reference

Page	What is in it
Deployment Guide	Docker Compose, secrets, HTTPS, remote Servers, updates
Server Configuration	Every Server environment variable
Hub Configuration	Every Hub environment variable
Hub Open Beta	Current limitations
Security Model	How credentials, tokens and roles work