How Siambr handles access and records
What a council’s information governance and security teams ask about, answered from what Siambr does.
Signing in
- Passwords
- The council sets the length of a password, the lock-out after failed attempts and how long a session lasts.
- Two-step sign-in
- Codes from an authenticator app, to RFC 6238, with recovery codes that are shown once and work once. An administrator can require two-step sign-in for chosen roles.
- Single sign-on
- Through OpenID Connect with Microsoft Entra, using the authorisation code flow with PKCE. Password sign-in can be turned off for the council’s own email domains.
- Repeated attempts
- Too many failed sign-ins from one address are held back without locking anyone out of their account.
Roles and what each one sees
- Roles
- A role is a named set of permissions, and one account can hold several roles.
- Rights on fields
- A role can hide named fields or make them read-only. A hidden field is never sent to the browser.
- The public site
- The council chooses which councillor details the public site shows. A detail switched off stays visible to officers and councillors after they sign in.
Restricted business
- Exempt information
- A restricted report states which category of exempt information it falls under and goes only into the restricted pack.
- Who can read it
- Committee Members and the officers allowed to read restricted business can open it.
- Each opening recorded
- The audit trail records who opened each restricted pack, document, annex or slide, and when. The meeting lists them.
Records and retention
- The audit trail
- Siambr records who did what and when, including what was done with an API key. The trail exports as CSV.
- Retention
- Meeting papers stay open to inspection for six years under section 100C of the Local Government Act 1972 and are then archived. The council sets how long petition signatures and consultation responses are kept.
- The email log
- Every email Siambr sends is kept in one log, from which it can be sent again.
API keys and webhooks
- API keys
- An administrator makes a key that acts with exactly the roles it is given, from the network ranges named for it. Its secret is shown once, and the key can be revoked.
- Webhooks
- Each delivery comes in one signed envelope, and goes only to the destination ranges the council allows.
Accessibility
- The standard
- Siambr aims to meet WCAG 2.2 at level AA. It has not yet been audited by an independent assessor, and its accessibility statement lists what does not meet the standard yet.
- How it is checked
- Its pages are checked against the WCAG 2.2 level A and AA rules with axe on every change, in the light theme and the dark theme.
See Siambr with a meeting of your own
We take a meeting from the first draft of its agenda to the published decision and answer your team’s questions on the way. Write to us to arrange a time.