Teammately Docs
Docs menu

reference

Workspace Administration

Administer workspace and project boundaries so correctness work has clear ownership and scope.

Workspace Administration

Definition

Workspace Administration covers two code-backed layers:

  • Organization administration in the Admin Console, including members, groups, roles, domain control, IP address control, audit log, usage statistics, profile, support settings, integrations, and API keys.
  • Project administration in the main product, including project members, groups, and project permission assignments.

Keep these layers separate when writing or operating from the docs. A workspace-level admin control is not the same as a project-specific correctness workflow.

Admin Console Groups screen showing organization groups, role names, and member counts.

Organization groups belong to the admin layer. Project membership and correctness artifact ownership remain separate concepts.

Fields, states, or lifecycle rules

  • Project permissions in the main product are code-backed for user and group subjects with ADMIN or MEMBER project roles.
  • The Admin Console exposes additional organization-level controls such as roles, domain control, IP address control, integrations, and API keys.
  • Do not infer compliance status, retention rules, SSO behavior, billing behavior, rate limits, or deployment options from the existence of an admin screen.
  • Approval actions in correctness workflows require accountable ownership; AI suggestions do not approve themselves.

Related objects may include workspace members, groups, workspace roles, permission keys, project permission assignments, domain controls, IP controls, API keys, notification integrations, and the project artifacts those people can access.

Worked example

Human approval boundary

A Workspace administrator manages an organization group in the Admin Console. A Project owner then grants that group access under Project Settings. The group can inspect the Project according to the current Project membership surface, but this does not change organization security controls or create authority over every governed correctness artifact.

Source confidence

Code-backed: this page is grounded in the Admin Console navigation and the main product project settings routes listed in source_refs.

Related task pages

Task / Expert ContributionsRequest an Expert ContributionCreate a focused benchmark contribution with an accountable expert, clear objectives, selected cases, attachments, and appropriate task components.Reference / Project SettingsProject MembersGrant or remove user and group access to a project while keeping task assignment and artifact governance separate.Task / Operating ManualImport and prepare casesBring cases into the project, conform them to Project Input Schema, inspect materials, and prepare benchmark selection.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

Admin Console Admin Console Understand the organization-level administration surfaces available at admin.teammately.ai. Object Model Workspaces, projects, and target systems Model organizational boundaries, product boundaries, and the AI system being governed. Governance and Reproducibility Roles and Permissions Use roles and permissions to route ownership, review, and approval work clearly. Reference Library User roles Understand the responsibilities of project operators, domain experts, AI engineers, accountable owners, and organization administrators.
AI context