Skip to content

Commit 345e70b

Browse files
authored
Remove instructions no longer relevant in current version. (#41)
1 parent ddf5956 commit 345e70b

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

docs/administration/owner.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ Before you can start using Gramps Web, you need to create an account for the tre
66

77
On a server with single-tree setup, when no user account exists yet, opening Gramps Web shows a form to create an admin account. The admin user will be both the owner of the (single) tree and the administrator of the installation. The form also allows setting the e-mail configuration needed for e-mail notifications (e.g. resetting a user password). If the e-mail configuration has already been added via a configuration file or environment variables on the server, this part of the form can be left empty.
88

9-
The form also allows to import genealogical data by uploading a file. This can also be done later from the "Import" page in Gramps Web (see [Import data](import.md)).
10-
119
## Multi-tree setup: create admin account
1210

1311
In a multi-tree setup, the same form to create an admin account will be shown if no users exists *in any tree*, i.e. when the server has just been created.
@@ -23,4 +21,4 @@ A possible workflow for a site administrator to create a new tree is to
2321
- Create a tree via the REST API, obtaining the tree ID of the new tree
2422
- Share the link to the owner creation form with the appropriate tree ID with the prospective tree owner
2523

26-
The tree owner creation form is analogous to the admin creation form described above, except that it does not allow to change the e-mail configuration (which is only allowed for admins).
24+
The tree owner creation form is analogous to the admin creation form described above, except that it does not allow to change the e-mail configuration (which is only allowed for admins).

0 commit comments

Comments
 (0)