Using Grist with Multi-User Operation

Developers
,
1

Greetings, fellow Grist-ers,

Just installed Grist using Docker in my Synology DS220+.

Super impressed by what Grist can do and the potential it has.

I tried creating new users to test in Grist but there is no response.

Upon digging, I found that it requires a SSO server.

I got two requests:

#1 Create a simple login and password menu for multi-user operation

#2 Can admin create users without the need of sending an invitation link? Direct use of Grist upon creation of new user.

2

@Express_Grist have you checked those two threads ?

1 Like
3

Maybe also Making Grist easier to self-host

4

Yes, I did saw these two post.

I don’t know how to link the SSO with Grist

5

This is only for self use for now.

I need it for multi user use

6

Hi @Express_Grist, Grist Omnibus should work out of the box with multiple users, if you set EMAIL/PASSWORD, EMAIL2/PASSWORD2, EMAIL3/PASSWORD3 or better still hook up an SSO (but it sounds like you are having trouble with that).

The omnibus doesn’t have a user interface for user management. You need email or sms support for verifying accounts and resetting passwords etc, and that becomes a whole adventure in itself - not something a standalone image can do without a lot of configuration or access to some external services. And if you need external services anyway, it makes more sense to use an SSO.

For example, if you were willing to use Google, you’d just need to set these two lines in dex.yaml:

There are lots of tutorials for how to get a google client id and secret for logins. Dex supports other SSOs also - if there’s one that would be convenient for you, I could try and help set you up.

1 Like
7

Unfortunately, I’m a newbie in coding.

I shall await future updates.

8

Hello everyone. A few years later, I’m still struggling a bit and all help is appreciated! I am trying to deploy grist-omnibus in my synology NAS using portainer as configuration tool. I would like it to be accessible under my ip:port since I handle HTTPS other way via Synology.

I’m setting the ENV variable “HTTPS” to “manual” but still getting this error:

info [grist-omnibus] Calling traefik [
‘–providers.file.filename=/settings/traefik.yaml’,
‘–entryPoints.web.address=:80’,
‘–entrypoints.websecure.address=:443’,
‘–entrypoints.web.http.redirections.entrypoint.scheme=https’,
‘–entrypoints.web.http.redirections.entrypoint.to=websecure’
]
2025/06/28 16:25:04 Starting up on port 17102
info [grist-omnibus] No /custom/dex.yaml
info [grist-omnibus] Checking dex… at http://localhost:9999/dex/.well-known/openid-configuration
debug [grist-omnibus] not ready: TypeError [ERR_INVALID_PROTOCOL]: Protocol “http:” not supported. Expected “https:”
info [grist-omnibus] Checking dex… at http://localhost:9999/dex/.well-known/openid-configuration
debug [grist-omnibus] not ready: TypeError [ERR_INVALID_PROTOCOL]: Protocol “http:” not supported. Expected “https:”
info [grist-omnibus] Checking dex… at http://localhost:9999/dex/.well-known/openid-configuration
debug [grist-omnibus] not ready: TypeError [ERR_INVALID_PROTOCOL]: Protocol “http:” not supported. Expected “https:”
info [grist-omnibus] Checking dex… at http://localhost:9999/dex/.well-known/openid-configuration
debug [grist-omnibus] not ready: TypeError [ERR_INVALID_PROTOCOL]: Protocol “http:” not supported. Expected “https:”
creating container: waiting for sandbox to start: EOF
gvisor check failed (flags: -unprivileged -ignore-cgroups); consider different GVISOR_FLAGS or GRIST_SANDBOX_FLAVOR
error [grist-omnibus] grist failed: exited with 1