Administration
For instance and organization admins: managing people, access, authentication, and accountability. Everything here lives under Settings, whose left nav is grouped by why you can see each section — Account (everyone), Organization (you administer an org), Instance admin (you run the instance).
Instance admin
Visible only to instance admins, under Settings → Instance admin:
| Section | What it's for |
|---|---|
| Insights | The instance-analytics dashboard: active users (DAU/WAU/MAU), growth, activity trends, top pages / contributors / spaces, AI answer-rate, and knowledge-health signals — over the last 30 days. |
| Users | Every account on the instance, newest signups first. Search; filter by role / status / whether they've connected an agent (MCP). Per row: plan tier (set inline — no self-serve billing), usage vs. plan limits, last-active, and a detail sheet (spaces, orgs, AI calls/mo, MCP status, recent edits). Create users, reset passwords, grant/revoke instance-admin, deactivate. |
| Organizations | Index of all orgs (create new, open one to manage) plus the instance-wide auto-join domain map. See Organizations below. |
| Usage | Instance-wide overview: totals (users, orgs, spaces, pages, attachments, AI calls/mo, asks/mo, answer rate), top AI consumers this month, and top unanswered questions over 30 days — each with a Draft page action that turns the gap into a new page. |
| Feedback | Inbox for feedback users send via the in-app form or an agent's submit_feedback tool. Emails admins and shows an unread badge. |
| Events | The firehose — every sign-in (and failed sign-in), page view, edit, access change, ask, and API request, newest first. Filter by type, search, scope to a date. |
| Errors | Errors reported from users' browsers, grouped by signature with a count, affected-user count, and recent occurrences — the triage companion to Events. |
| Audit | The focused access-control slice of Events: org membership, grants, domain mappings. Kept indefinitely. |
| Instance | Instance-wide runtime config. See [[Self-Hosting]]. |
[!NOTE] Admin activity is hidden by default. Insights, Events, Errors, and Audit exclude actions by instance admins out of the box — an operator's own views, edits, asks, and error reports would otherwise drown the real signal. Flip Include admins on any of those screens to fold it back in. (System actions and anonymous activity are always shown.)
[!NOTE] AI kill-switch & maintenance notice — under Settings → Instance admin → Instance, you can pause every AI feature (Ask, semantic search, and background indexing) with one switch while the embedder/LLM is under maintenance, and post an instance-wide maintenance banner. tela also flips Ask to "AI temporarily unavailable" on its own when the model is unreachable (see [[Search & ask your docs]]) — the switch is the manual override for a planned window.
Users & registration
tela is email-first: open self-registration with email confirmation, then login by email or username. Close self-registration from the Instance settings. New sign-ups whose verified email domain matches an auto-join domain are enrolled into that org as a member automatically.
Organizations
Organizations group people so a whole team can be granted access to a space at once. Each org is managed on its own page (a left-nav with room to grow), reached from Settings → Organizations → Manage:
- Overview — plan tier + live usage (members, AI calls/mo, attachments, spaces) against the org plan's caps.
- Members — add or remove people and set admin/member role, and invite teammates by email: they get a link to join and land in the org once they accept or sign up — even without an existing tela account. Pending invites are listed until accepted, and can be revoked.
- Groups — sub-teams within the org; share a space with a group to grant just part of the org.
- Single sign-on (instance admin only) — connect the org's OIDC provider. See [[Single Sign-On (SSO)]].
- Custom domains (org admin too) — serve the app on your own address with your branding + login methods. See [[Custom domains]].
- Activity — this org's access-change history (the audit log, scoped to the org). Available to org admins.
[!NOTE] Auto-join domains (mapped in Settings → Organizations) map an email domain like
acme.comto an org for automatic membership and to route those users to the org's SSO. Don't confuse them with [[Custom domains]] — a web address the app is served on. Different things.
On telawiki.com anyone can create a team themselves — Settings → Plan & Usage → Create a team — become its admin, invite teammates by email, and upgrade to the Team plan in place (see [[How to upgrade]]). A self-hosted instance keeps org creation to instance admins by default; an operator can enable self-serve. An org admin who isn't an instance admin sees a scoped Settings → Organization section: only the orgs they administer, with no instance-wide domain mapping.
Authentication
- Passwords — the default, with email verification and self-service reset.
- [[Single Sign-On (SSO)]] — connect a company OIDC provider (Microsoft Entra, Okta, Google Workspace, …) so people sign in with their work account; optionally enforce it per org.
- Social login — instance-wide Google / Microsoft / GitHub buttons (configured by the operator — see [[Self-Hosting]]).
Accountability
- Events and Audit — see Instance admin above. Events is the firehose; Audit is the access-control slice (also surfaced per-org as Activity). Both hide instance-admin activity by default — use Include admins to see it.
- Access model — space membership, organizations, and groups combine to decide who sees what.
- Plans & usage — every account (personal and each org) carries a plan tier. See your own under Settings → Account → Plan & Usage; admins see every account's usage in Users and per-org usage in an org's Overview.
[!NOTE] Page views and sign-ins are recorded for logged-in users. The activity feed is retained for ~180 days (configurable); the access-control audit log is kept indefinitely.