-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
self-hosted: document the importance of
GRIST_DEFAULT_EMAIL
- Loading branch information
Showing
1 changed file
with
33 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -61,6 +61,7 @@ To try Grist out using Docker, make an empty directory for Grist to store materi | |
docker run -p 8484:8484 \ | ||
-v ~/grist:/persist \ | ||
-e GRIST_SESSION_SECRET=invent-a-secret-here \ | ||
-e [email protected] \ | ||
-it gristlabs/grist | ||
``` | ||
|
||
|
@@ -101,6 +102,22 @@ take at least the following steps: | |
|
||
You can also host Grist on AWS. Full instructions on this hosting method are available on the Grist [AWS Marketplace page](install/aws-marketplace.md). | ||
|
||
### What is the administrative account? {: .tag-core .tag-ee } | ||
|
||
On a new Grist installation, the user who logs in with the email | ||
defined by `GRIST_DEFAULT_EMAIL` is the administrator of this Grist | ||
installation. When Grist runs for the first time, it will create an | ||
account set to the value of `GRIST_DEFAULT_EMAIL`. Note that if this | ||
variable is not set, it defaults to `[email protected]`. Changing the | ||
value of `GRIST_DEFAULT_EMAIL` after the first admin user has been | ||
created will effectively revoke administrator permissions from the | ||
first user and assign them to the new email address. | ||
|
||
The administrative account has access to the admin panel where they | ||
may inspect details of the installation or toggle features such as | ||
[telemetry](self-managed.md#how-do-i-control-telemetry) or [Grist | ||
Enterprise](self-managed.md#how-do-i-enable-grist-enterprise). | ||
|
||
### How do I sandbox documents? {: .tag-core .tag-ee } | ||
|
||
Grist allows for very powerful formulas, using Python. We recommend | ||
|
@@ -237,6 +254,22 @@ The name of the team should use only the lower-case characters a-z, the digits | |
[Custom styling](self-managed.md#how-do-i-customize-styling) to hide any UI elements | ||
you don't need. | ||
|
||
|
||
#### Changing the value of `GRIST_DEFAULT_EMAIL` | ||
|
||
When [using | ||
`GRIST_SINGLE_ORG`](self-managed.md#how-do-i-set-up-a-team), the | ||
single org will also be created initially and owned by the user | ||
configured by `GRIST_DEFAULT_EMAIL`. If you change the value of | ||
`GRIST_DEFAULT_EMAIL`, [the | ||
administrator](self-managed.md#what-is-the-administrative-account) may | ||
temporarily lose access to the team site. | ||
|
||
In order to prevent this, before changing `GRIST_DEFAULT_EMAIL` use | ||
[team sharing options](../team-sharing) to add new owners to the team | ||
site, since apart from initial creation, administrators have no | ||
automatic right to team site membership. | ||
|
||
### How do I set up authentication? {: .tag-core .tag-ee } | ||
|
||
Authentication can be set up in many ways for Grist Core and Enterprise, using | ||
|