Administration

The first account created on an instance is the reef keeper — the admin. Admin-only sections appear in Settings once you're signed in as one.

Members

Settings → Members lets you add accounts, archive members (disables sign-in, keeps their memos), restore them, or promote another admin. Archived members can't sign in until restored.

Adding a member takes a username and their email. If your reef has email set up (see Deploy → Email), leave the password blank and they'll get an invite email with a link to pick their own password. Without email, set a password for them and pass it along yourself. If someone forgets their password, they can reset it themselves from the sign-in page (email reefs) — or you can set a new one here.

Reef settings

Settings → Reef holds the instance-wide switches:

• Reef name — shown in the instance profile.
• Public mode — whether anonymous visitors can browse public memos and Explore.
• Allow sign-ups — open or close registration. (Admins can always add members manually.)
• Reactions — the emoji set members can react with.

Preferences vs. reef settings

Personal things — theme, default memo visibility, tag renames — live under Preferences and affect only you. Reef settings affect everyone.

Access tokens

Every member mints their own in Settings → Tokens; there's nothing reef-wide to configure and no admin switch to turn them off. A token acts as the member who made it and is always less powerful than signing in: it can't manage tokens, change an account's email or password, or use any admin endpoint — so a leaked token can never become a lost account. See the API reference for scopes and examples.

Archiving a member immediately stops their tokens working, and deleting the account deletes them outright.

Housekeeping

• Back up nemomemo.db and uploads/ (see Deploy).
• The Dory sweeper runs automatically every minute; nothing to configure.
• Attachments → Delete unused reclaims disk from orphaned uploads.