StatsRaven

People and sign-in

Roles

RoleCan
AdminEverything, Settings too
EditorAsk, pin charts and name patterns
ViewerLook and ask

The person who sets StatsRaven up is the first admin. There is always at least one admin. There is no limit on the number of people.

Invites

In Settings, People, invite someone by email and pick a role. You get a link to send them. It works once and for seven days; they choose a password when they open it. Passwords need at least 12 characters.

Sign in with Google, Microsoft or OpenID

In Settings, People, add a sign-in provider: Google, Microsoft, Keycloak, or any other OpenID Connect provider. Register this redirect address with the provider:

https://stats.example.com/auth/oidc/callback

Then enter the issuer address (Check confirms it), the client ID and, unless it is a public client, the secret. For Microsoft, put your tenant ID in place of organizations to allow only your company. A person signs in as the member with the same email, or takes up an invite for it. You can also name email domains whose people may join without an invite, and the role they get. Passwords keep working next to it. Outside localhost, the provider needs HTTPS.

Sensitive fields

In Settings, Privacy, choose what editors and viewers must not see: page paths, referrers, city and region, network names, browser details, log text or event properties. They then see a code such as hidden 3fa2c1 in its place, in screens, chat and SQL. The same value always gets the same code, so counting and grouping still work. Admins and tokens see real values. Email addresses and IP addresses in log text are always hidden from editors and viewers.

Change log

Settings, Change log lists changes to settings, tokens, people and the license, sign-ins, SQL API and MCP calls, and CSV downloads, with who did each and when. Lines are kept for 180 days. Keys, passwords and token values are never written there.