Isolation
Every MGA is its own tenant. Isolation is enforced in the database with row-level security, so one tenant's data is never readable from another's session even if the interface had a bug. A session for one tenant is never valid on another tenant's address.
Multi-factor authentication
- 1Open Settings → Security and choose Set up authenticator.
- 2Scan the code with an authenticator app and enter the six-digit code to confirm.
- 3As an administrator, switch on Require MFA for the team. From then on every user is asked to set it up at their next sign-in.
Administrators always need an authenticator to make changes: the database itself refuses every write of an administrator session without a verified second factor, so an administrator who has not set one up yet can read the workspace but not change a client, a colleague, a product or a setting until they do. With Require MFA for the team on, the same rule applies to every underwriter. Reading is never blocked, so the page where you enrol is always reachable.
Permissions are database rules too. A colleague without the invoicing permission cannot mark an invoice paid, change its amount or delete it by any route — not from the screen and not against the database directly; the same holds for products, binding, claims handling and bordereaux.
Lost phone: an administrator opens the member in Settings → Team and chooses Reset authenticator. The enrolled authenticators are removed, the member signs in with their password and enrols a new one (immediately, when MFA is required). The password is never changed by someone else; forgot password on the sign-in page is the member's own route. Both are logged. Only when every administrator of the environment is locked out does Soldek step in, after identity verification.
Roles and permissions
Access is by role (administrator, underwriter, claims handler, finance, custom) and per permission within the role. Brokers and policyholders have their own portals and can only reach their own records.
Audit trail
Every quote, bind, endorsement, claim, invoice and settings change is recorded with who did it and when. The trail is visible on each record and is included in exports. A change to a colleague's role or permissions names that colleague and lists which permissions went on and off, so the trail answers whose rights changed, to what, and who did it.
As an administrator you read the whole trail in one place: Settings → Activity log shows every event in your workspace — by your team, by brokers and policyholders in their portals, by the platform's own automation (shown as System) and by platform support on your grant (shown with the name of the person at Soldek) — plus the raw row changes the database records itself. Filter by member (Team → Activity opens a member's trail directly), by kind, by record and by period, search in the action, and download the filtered set as a spreadsheet; the download is itself logged.
The trail cannot be edited. The database refuses every change or deletion of a log line that comes through the application — from your team, from the connection that runs your automation and from Soldek's own service key alike; a line is never rewritten, only followed by a new one. The only way log lines leave is together with the whole workspace, after its book is gone (a reset of an environment that never went live), and even then one line remains that records how many entries went.
The trail is never skipped either. When a log line cannot be written, the action stops instead of going ahead unlogged: the screen tells you the log could not be written and the platform team is alerted. The database applies the same rule to every row change in your workspace — quotes, clients, products, rate tables, binders, bank links, API keys, your team and your settings — by writing the log line inside the same transaction as the change, so a change without its line cannot exist. Those database lines name which columns changed, never the values.
Records that take more than one step are written in one go. Binding a quote, a broker's application with its insured persons, a renewal with its roster and conditions, an endorsement with its roster change and premium, and a decision on a bind condition each land as a single database transaction: either everything is saved, or nothing is and the screen tells you why. An insured person that cannot be saved is never silently dropped — the whole application or renewal is refused until it can be.
Support access
Soldek cannot open your workspace on its own. When you want help, an administrator opens a time-boxed support grant under Settings → Security, with a reason; only while it is open can the platform reset an account or the workspace, and only when every administrator is locked out does the platform step in without one. Every such access appears in your platform access log with the name of the person at Soldek who performed it and the grant it was done on, and every administrator receives an e-mail about it at that moment — you never have to open the log to find out.
When the platform issues a sign-in link for a member, the link is e-mailed to that member, never shown to Soldek, and every existing session of the account ends; a temporary password (for test accounts without a mailbox) must be replaced at the first sign-in. The moment the account chooses its own password is logged as well, so the trail reads: credential issued → used → whatever the account did afterwards under its own name.
Keys and sessions
- Client API keys are per tenant, shown once, hashed at rest, rate-limited and revocable.
- Sign-in, MFA and public endpoints are rate-limited against brute force.
- Data is encrypted in transit and at rest; customer-facing quote links are signed.