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.
| Choice | Options |
|---|---|
| What to keep from a sign-in provider | Name 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 online | Everyone (the default), admins only, or nobody: the server stops recording it and clears what it had. |
| How members sign in | Through 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
- Owner is a flag above every role. Owners have every permission everywhere. There can be several; the last one cannot be demoted, kicked or banned. Only owners make owners.
- Roles carry permissions and an order. Everyone has @everyone. A member’s permissions are those of @everyone and every role they hold, together.
- Rank is the highest role a member holds. Kicking, banning, timing out, giving roles, and muting, moving or disconnecting someone all need that person’s rank below yours. You can create, edit and give only roles below your own.
- Someone who is not an owner cannot grant a permission they do not have themself.
- A room or a text channel can allow or deny permissions per role. Among a member’s roles, an allow beats a deny.
| Permission | Lets a member | Per room or channel |
|---|---|---|
| View channel | See the room or channel, and read it | Yes |
| Connect | Join a room’s call | Yes |
| Speak | Be heard in a call. In a text channel: post, react and upload. | Yes |
| Video, Share screen | Send a camera or a screen share. Honoured by the app; the server does not enforce these two. | Yes |
| Voice activity | Talk without push to talk | Yes |
| Priority speaker | Be heard over others, whose volume drops while they talk | Yes |
| Create invites, Manage invites | Make invites; see and revoke other people’s | |
| Manage channels | Add, edit, order and remove rooms, channels and categories | Yes |
| Manage roles | Make and edit roles below their own, and give them | |
| Kick, Ban, Timeout members | Remove someone, keep them out, or silence them for a while | |
| Mute, Deafen, Move, Disconnect members | Moderate people in a call | Yes |
| View audit log | Read the audit log | |
| Manage server | Change the server’s name, icon, welcome and upload limits, and manage bots. It implies no other permission. | |
| Manage reports | Read 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.
- A room has a name, a topic, a user limit, a bitrate, push to talk only, video on or off, and whether end-to-end encryption is required. Calls and media has the ranges.
- A text channel has a name, up to 80 characters, and a topic. Deleting one deletes its messages and their files.
- A direct conversation is between two members. One pair has one conversation.
- The server’s own page, Overview, sets its name, icon, description, welcome text, the room people land in, and an away room with its timeout.
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.
- Left alone, an invite is one use and lasts 7 days. Uses go from 1 to 1,000, or unlimited. An expiry runs from a minute to 30 days; only an owner or someone with Manage server can make one that never expires.
- The invite is shown once, as a
https://tinyclient.io/invite#…link. The server keeps only a hash. The link holds the server’s address, so the person has nothing else to type. - The link’s secret sits after the
#, which a browser does not send, so tinyclient.io never receives it. That page only opens the app. - An invite can give only roles below the rank of whoever made it.
- Revoke one at any time. Invites that were accepted stay in the list.
Moderation
Right-click a person. What the menu offers depends on your permissions and on their rank being below yours.
| Action | Effect |
|---|---|
| Server mute, server deafen | In a call. The person cannot undo it themself. |
| Move, disconnect | To another room, or out of the call |
| Timeout | For up to 28 days. Ends their call. They can still read, and cannot post, react, upload or join a call. |
| Kick | The membership and every session go. They can come back with a new invite. |
| Ban | The 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.
- Only holders of Manage reports see reports, and never one about themselves.
- The person reported never learns who reported. Moderators do see the reporter. The reporter cannot read their report back.
- Reporting a message records which message it was, not its text. Text is in a report only if the reporter chose to send it as evidence. The server cannot check that evidence is genuine, least of all from an encrypted conversation, and marks it unverified.
- A moderator moves a report between open, reviewing, actioned and dismissed, adds notes, and can link the kick, ban or timeout that answered it.
- A resolved report is deleted after 90 days unless the operator set otherwise. An owner can put a hold on one, which is the only thing that stops that.
- One member can file 10 reports an hour and 50 a day.
Uploads and scanning
- Images and GIFs may be up to 8 MiB and other files up to 25 MiB. Someone with Manage server can raise either, up to 100 MiB.
- A file is scanned by ClamAV and three built-in rules before anyone can fetch it. If the scanner is down, the upload is refused, not let through.
- PNG, JPEG, WebP and GIF images are re-encoded before they are stored, so nothing hidden after the image reaches the disk.
- Always refused: programs and scripts (
exe,dll,msi,bat,ps1,js,jarand the like), shortcuts and disk images, HTML and SVG, Office files with macros, and any file whose name, declared type and contents disagree. - Archives are refused unless someone with Manage server allows them. Zip files are then still checked for size and for tricks such as nested archives and escaping paths.
- Files sealed for an encrypted conversation are not scanned: the server has only ciphertext.
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.
| Scope | Lets the bot |
|---|---|
rooms.read | List rooms, and hear room changes and who joins and leaves calls |
rooms.write | Create a room, change its settings, and delete it |
members.read | List 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.