Skip to content

Native Product Authorization

Native ID product authorization

Cbox ID's native workspace is an app of the platform root identity authority. Shared organization membership establishes identity and tenancy; its Admin tier does not grant native product access. The current active organization Owner has all native capabilities. Other members receive explicit, manually assigned native app roles: Reader (viewer), Billing (billing), Editor (developer), and Admin (admin). Roles combine. Reader grants operational reads and team reads; Billing grants financial reads and management; Editor grants operational reads and writes; Admin grants all native permissions. Billing-only access does not expose operational project records.

id:native-product:sync creates the real first-party confidential catalog client once, records its generated identity in native_product_clients, and synchronizes the six permission definitions and four role definitions. The client has no browser redirects or OAuth scopes and uses only the client-credentials grant type. Neither synchronization nor installation assigns roles or commercial entitlements. Installation invokes the same synchronization after creating the platform root. The production migration sequence invokes it before Billing definition synchronization and before serving the new release; failure aborts the release.

NativeProductAccess resolves the exact subject, organization and native client through core permission decisions on each authorization decision. It has no worker cache or shared-role fallback. Product admission is a separate required check. Human permissions, machine credential roles/scopes, and environment row restrictions remain separate. A machine credential does not impersonate a human's app roles.

NativeEnvironmentAccess intersects stored selections with current project ownership. Every non-Owner uses explicit all or selected scope, including shared organization Admins. An empty selected set denies every environment. Current Owners reach all environments they currently own; the stored selection is preserved if ownership later changes. Environment reads and writes additionally require the corresponding native app permission. Reader cannot gain write authority from a local environment selection.

workspace.get returns only the bound workspace ID, name and status, allowing Billing-only clients to verify their explicit organization selection. Project and environment lists require id:read and filter both rows and counts to the current environment selection. Reader environment pages retain readable records while disabling write controls; unsafe requests still fail independently on the server.

The workspace Team page and workspace API manage only native app roles. Role replacement and removal lock the membership and use roles_version; removal clears only native app assignments and retains shared membership and other apps. The current Owner is protected again under the lock. Environment selection has an independent environment_access_version covering the all flag and sorted grants, checked under the same membership lock. A stale request returns 409 to JSON clients and an actionable field error to Inertia forms. React editors refresh their displayed selection after a conflict.

Invitations carry the native client and multiple app role grants. New organization members receive the neutral shared Member tier; inviting an existing member preserves that member's shared tier. Pending invitation lists, resend and revoke are fenced by both organization and native client. Acceptance reuses the central invitation lifecycle and validates parked role grants. The native team does not expose a way to invite or assign Owner. Shared identity-directory administration remains a distinct surface; native app Admin does not rename the shared organization or transfer ownership.

Focused verification lives in NativeProductAuthorizationTest, NativeProductMembersTest, TeamInvitationsTest, WorkspaceActionsTest and PlatformInstallCommandTest. The full application suite remains the release gate; source SDK overlays are development verification tools and are not a substitute for publishing and installing the required dependency releases.