Platform Administration, Permissions, and Authentication

This guide maps out MOI’s four access-control layers, unified authentication (SSO) and registration admission rules, current platform administrator API capabilities, and known self-service UI boundaries.

Four access-control layers

MOI isolates workspace collaboration, database tenancy, account identity, and cross-workspace platform governance into four separate layers:

Layer

Scope

Managed capabilities

Entry point & docs

1. Unified account & security

Cross-product account level

Profile, password/email/phone/third-party sign-in links, real-name verification, personal access tokens (PAT), and service-account credentials

Top-right user avatar → Account Management, Real-name verification, Access credentials

2. AI Studio workspace permissions

Single workspace

Member invitations (existing accounts), custom roles, global and object-level rules, tags, and member operation audit logs

AI Studio sidebar → User Permissions, Member management

3. MatrixOne database permissions

Single database instance tenant

Database users, ACCOUNTADMIN / MOADMIN role hierarchies, SQL GRANT / REVOKE, IP allowlists, TLS, and private network links

MatrixOne Console → Permissions: MatrixOne, SQL privilege categories

4. Platform administrator governance

Cross-workspace platform level

Cross-workspace compute operations, managed sandboxes and workspace sandbox quotas, global service-slot bindings, and feedback tickets/rewards

Platform administration API reference

Important boundaries: A workspace administrator role does not grant platform super-admin access or MatrixOne ACCOUNTADMIN database privileges. Likewise, the account-level registration invitation limit (10 per user) is completely separate from adding existing MOI accounts to a workspace.

Platform administrator governance scope (API vs UI)

In the current codebase, the MOI web frontend provides the AI Studio workspace console and the unified Account Center, with no separate MOI Platform Admin web UI. Cross-workspace platform administration operations are exposed via authenticated Platform Administration HTTP APIs requiring a configured platform administrator identity:

Governance domain

Administrator actions available

API reference

Compute resource governance

List compute instances across workspaces (filter by workspace, status, keyword), inspect worker types and replica state, update configuration and custom Python requirements.txt validation, suspend/resume/retry error instances, run delete preflight and force async deletion

Administration · Compute resources

Managed sandboxes & quotas

List, inspect, or delete managed sandboxes across workspaces; replace network-enabled tools and domain:port egress allowlists; override workspace managed/ephemeral sandbox quotas and auto-ephemeral policy

Administration · Sandboxes

Service slots & model bindings

Query candidate models, bind or clear platform service slots and recovery environments, and audit configuration change history logs

Administration · Service slots

Feedback tickets & rewards

List and inspect feedback tickets across accounts, update ticket status and admin replies, approve non-monetary reward records, draft and submit GitHub issues

Administration · Feedback tickets

Unified authentication, SSO, and registration admission

1. Sign-in modes and OAuth2 / OIDC federation

  • Unified SSO mode (default): Standard deployments redirect MOI console logins to the unified Account Center using OAuth2 / OIDC session issuance.

  • Built-in mode: Selected private or embedded deployments can set deployment configuration (AUTH_MODE=builtin) to use the built-in login entry while still backing identities in Unified Account (UC).

  • Third-party sign-in providers: Depending on deployment configuration, users can link or unlink GitHub, Google, and WeCom accounts under Account Management. Only providers configured in the current environment appear.

2. Registration invite limits and waitlist admission

  • Invite quota & waitlist policy: Account registration supports configurable per-inviter limits (default 10 invitations for standard accounts), global invitation limits, and a waitlist mode when invite capacity is exceeded or before public beta opens. Waitlisted accounts are activated automatically once approved or when admission opens.

  • Account invites vs workspace invitations: The 10-invite limit applies only to inviting unregistered users to sign up for MOI. It does not restrict how many existing MOI users you add to a workspace in User management.

3. Enterprise SSO (SAML / Okta / LDAP) configuration boundary

The enterprise identity / subscription switches visible on the Billing Center → Settings preview layout are not active self-service toggles—you cannot enable SAML, Okta, or LDAP federation from Billing Center today.

For enterprise deployments requiring corporate IdP federation (OIDC, SAML, LDAP, or WeCom), contact your deployment administrator to configure identity federation at the Unified Account (Keycloak) layer, or reach out to Support.

4. Security and credential isolation

  • Password changes & step-up confirmation: Changing a sign-in password requires a verified email address; administrative operations enforce step-up checks and CSRF protection where applicable.

  • API credential separation: AI Studio REST calls require X-API-Key (and X-Workspace-ID), whereas Genesis calls require Authorization: Bearer with a PAT (sk-uca-v1), service-account API key (sk-sa-v1), or enabled local key (sk-mo). Never mix browser session cookies and API keys in the same request (ErrMultipleAuthCredentials). See Access credentials and Prepare to call an API.

Last updated on