Manage a community

First-run setup, roles, channels and rooms, invites, moderation, reports, uploads and bots.

All of it is done in tinyclient, in Server Settings and the menus on people, rooms and channels. A page shows only to someone whose permissions allow it. The API behind each is in docs/server.md.

First-run setup

A new server has an owner and nobody else. The first time the owner opens it, tinyclient asks what the community keeps about its members: three choices, or a preset that makes all three. Only an owner can read or change them, later too, at Server Settings › Privacy. Every member can see the choices in force.

ChoiceOptions
What to keep from a sign-in providerName and email (the default), name only, or neither: the account starts as “Member” and the person chooses a name. It applies to accounts made from then on, and has nothing to act on without a provider.
Who sees when members were last onlineEveryone (the default), admins only, or nobody: the server stops recording it and clears what it had.
How members sign inThrough the provider only (the default), passkeys or the provider, or passkeys only. Sign-in and passkeys.

The Convenience preset is the three defaults. The Privacy preset keeps neither name nor email from a provider, records nobody’s last-online time, and accepts passkeys only. Either can be adjusted one choice at a time.

Setup is not a gate: the owner can invite people before answering. Two things in it are one-way, and each happens only when asked for: erasing every member’s stored email address, and clearing last-online times by choosing nobody.

Setup does not turn message encryption on or off, does not change what the audit log or the operator can see, and does not reach backups. It does not make anyone anonymous to the owner, who knows whom they invited.

Owners, roles and permissions

PermissionLets a memberPer room or channel
View channelSee the room or channel, and read itYes
ConnectJoin a room’s callYes
SpeakBe heard in a call. In a text channel: post, react and upload.Yes
Video, Share screenSend a camera or a screen share. Honoured by the app; the server does not enforce these two.Yes
Voice activityTalk without push to talkYes
Priority speakerBe heard over others, whose volume drops while they talkYes
Create invites, Manage invitesMake invites; see and revoke other people’s
Manage channelsAdd, edit, order and remove rooms, channels and categoriesYes
Manage rolesMake and edit roles below their own, and give them
Kick, Ban, Timeout membersRemove someone, keep them out, or silence them for a while
Mute, Deafen, Move, Disconnect membersModerate people in a callYes
View audit logRead the audit log
Manage serverChange the server’s name, icon, welcome and upload limits, and manage bots. It implies no other permission.
Manage reportsRead and handle abuse reports

On a new server, @everyone can view, connect, speak, send video, share a screen and use voice activity. The database enforces permissions and rank itself, not only the API in front of it.

Rooms, channels and categories

A room is a voice channel. A text channel is separate. Both can sit in categories, which someone with Manage channels orders by dragging. A member sees only the rooms and channels they may view.

Invites

Membership is by invite, unless the operator lets a provider’s groups join. An invite carries a label, the roles it gives, a number of uses and an expiry.

Moderation

Right-click a person. What the menu offers depends on your permissions and on their rank being below yours.

ActionEffect
Server mute, server deafenIn a call. The person cannot undo it themself.
Move, disconnectTo another room, or out of the call
TimeoutFor up to 28 days. Ends their call. They can still read, and cannot post, react, upload or join a call.
KickThe membership and every session go. They can come back with a new invite.
BanThe same, and every sign-in identity of that person is held, so a new invite or a fresh sign-in is refused. A ban can have an expiry. Someone who already left can be banned too.

Each of these is written to the audit log with who did it and the reason they gave. Only a message’s author can edit or delete it.

The audit log

Someone with View audit log reads who did what, to whom and why, newest first, filtered by person or by kind of action. It covers rooms, channels, roles, invites, members, bans, timeouts, call moderation, bots, server settings, first-run setup and sign-out everywhere. It never holds message text.

Abuse reports

A member can report a message, a member or a channel to the people who run the community, under a category and with a note. A report stays inside that one server.

Server side only, so far. Reports are built in the server and its API. tinyclient 0.2.71 has no screen for filing or reading them yet.

Uploads and scanning

Bots

Someone with Manage server makes a bot with a name and a few scopes, and is shown its token once. A bot is not a member and does not appear as a person online.

ScopeLets the bot
rooms.readList rooms, and hear room changes and who joins and leaves calls
rooms.writeCreate a room, change its settings, and delete it
members.readList people, and hear member changes and presence

A bot cannot join or change a call, and cannot read or post messages. Revoking it ends its connection within a minute. It sends Authorization: Bot <token>; the routes are in docs/server.md.

Edit this page on GitHub