Admin Console
The current Teammately product exposes the Admin Console as a workspace-administration mode under /admin. Use this page to distinguish organization-level administration from project-level correctness work in the project workspace. The shared product shell switches between project navigation and workspace administration while preserving the organization-level boundary.
Definition
The Admin Console groups organization administration into Directory, Security, Insights, and Organization Settings. The code-backed navigation includes Members, Groups, Roles & Permissions, Domain Control, IP Address Control, Audit Log, Usage Statistics, Profile, Support Settings, Integrations, and API Keys.
This page documents that those surfaces exist. It does not claim detailed compliance, billing, deployment, rate-limit, or security behavior unless a linked source file exposes that behavior directly.
The Admin Console is the organization administration surface. Group management is separate from project-level correctness work.
The Integrations screen shows notification and partner connection surfaces that belong to organization administration. Visible contact-support states should not be documented as self-serve integrations.
API Keys are managed in the Admin Console and should be documented as an organization administration surface, separate from project correctness artifacts.
Fields, states, or lifecycle rules
- Members and Groups are organization directory surfaces. Project-level membership and project permissions remain separate surfaces in the main product.
- Roles & Permissions in the Admin Console manage workspace roles and permission keys exposed by the admin application. Do not treat role names in orientation pages as exact permission contracts.
- Domain Control stores whether domain enforcement is enabled and which email domains are allowed for invitation.
- IP Address Control stores whether IP limiting is enabled and the configured allowlist.
- API Keys can be listed, created, copied at creation time, scoped, and deleted from the admin app surface. Treat the full value as a secret and create separate keys for separate integration boundaries.
- Slack is the currently clickable self-serve notification integration in the Admin Console. Microsoft Teams and the other listed partners are visible as contact-support or coming-soon surfaces in the current integrations index, so these docs should not describe them as self-serve integrations.
- Audit Log and Usage Statistics appear as admin console surfaces, but this page does not promise exact event schemas, retention periods, analytics definitions, or export behavior.
Domain Control and IP Address Control are organization-level security settings. They should not be described as project review or benchmark approval mechanisms.
IP Address Control exposes enforcement settings and should be documented only as an admin access-control surface.
Product boundary
Use the Admin Console when the question is about organization access, security controls, API keys, notification integrations, or organization-level activity. Use project settings and product-area docs when the question is about cases, reviews, policies, rubrics, benchmarks, and project-specific permissions.
A reviewer persona, a Project member, a Workspace role, and an organization administrator are related but not identical. Read each access or authority claim from its owning surface.
Likewise, an API key, its Project access, and an endpoint's action scope are related but not identical. Key administration belongs here; the external service contract must define what a caller can actually do.
Source confidence
Code-backed: this page is grounded in the current /admin workspace route, shared navigation mode, admin directory, integrations index, and representative admin route implementations listed in the frontmatter source_refs.