First steps as the Owner

The server runs. Before the crew arrives, take ten minutes as the Owner: name the place, make invites, give moderators their roles and decide what stays private.

The Owner

The Owner is the account the setup assistant created (ADMIN_USERNAME, default admin). The Owner has every permission, always: no role, channel setting or other admin can restrict, demote or kick it. Some powers belong to the Owner alone, such as the System tab with updates and the storage dashboard. Ownership is not transferable in the interface, so guard this account: change the initial password, remove ADMIN_INITIAL_PASSWORD from .env, and switch on two-factor sign-in under Settings.

The Get started list

The first sign-in shows a Get started list under the channel header: name the community, invite people (a button creates and copies a 7-day link), review the channels, set up voice, check the status page and, if you like, write rules. The steps tick themselves as you go. Close the list with the cross; the server menu brings it back.

Invites

Mnema Talk is invite-only: there is no public sign-up. Create invites under Admin console > Invites. Each invite can expire and have a use limit, and you can revoke it.

A vanity link gives the community one short address, such as https://chat.example.com/join/night-owls (Admin console > Invites > Vanity link). While its switch Link active is on, the link is a permanent public invite: anyone who has it can sign up, with no use limit and no expiry. Switched off, the link is closed and the name stays reserved. Only the Owner can switch it on; do that only when you want anyone with the link to join.

Roles for your moderators

A fresh server has @everyone with what members can usually do, plus built-in roles. Create your own under Admin console > Roles: a name, a colour, a position and the permissions. A member's permissions are @everyone plus all their roles; a higher position outranks a lower one.

  • Moderation needs to be granted. Manage reports (the Reports tab) and Kick members are off for @everyone and for every role until you give them out.
  • Administrator grants every permission and skips channel overwrites, but the hierarchy still applies and the Owner-only powers stay with the Owner.
  • View community as in the role editor shows exactly what a role sees, before you hand it out.

Channels, categories and private places

Review the default channels and categories and rename them to fit your crew. Categories and channels allow or deny permissions per role or member, which is how private channels and Talks are made: deny View channels for @everyone on an "Officers" category and allow it for the Officers role. Changes apply at once, also in a running call.

Settings worth a look

  • Welcome & rules: the community name and the rules new members accept before they write.
  • Sign-in & messages: whether direct messages are on (default) and after how many days of inactivity a session signs out (default 7).
  • Raid protection and automod are on by default with careful rules; the word and link lists are optional.
  • Optional features, each off until configured: e-mail and password reset (SMTP_* in .env), the API reference page, a separate TURN relay and the Update now button.

Before you send the first invite

  • Backups run and have been restored once as a test.
  • Admin > Status shows no red items, and Test my connection from a phone on mobile data passes.
  • You know how to update.

Something wrong on this page? Tell us.