REMOTE ARC
Administration
Learn about account roles, operational monitoring and the Admin service boundary.
Administrator access
Admin requires a signed-in account with the current administrator role. The platform checks that role for each operation rather than trusting the browser's claimed identity. Administrative writes require the configured Admin origin and appropriate request format. Ordinary users cannot use Admin endpoints to read another user's data.
Platform operations
Admin provides account and device monitoring, plan and credit administration, service signals and website submissions. Existing Connect entitlements and hosted model budgets are separate. Model keys alone do not authorize paid inference. Administrative grants change only their defined scope; they do not silently expand device permissions.
Separate service rollout
The independent Admin repository has a dedicated service boundary and release workflow. The initial main-platform release retains the existing Admin experience. A later verified configuration switch can route it through the separate service without moving account data or the device registry. Publishing the code does not itself perform that cutover.